Hi,
Is there any way to convert Magix MS/VPX projects to Vegas Pro 22/23? The development team could at least consider some basic feature! A separate plugin! In my case, I have more than 200 projects!
Thanks!
Vegas Pro has long been able to import EDL text files (EDL = Edit Decision List), so if MAGIX Movie Studio and VPX16 are able to export EDL text files then Vegas Pro should be able to import those EDL projects. I've looked at my copy of MMS23 and user manual and, unfortunately, MMS23 doesn't seem to have an EDL export function. I also tried copy/pasting a few events from MMS23's timeline to VP22 + 23 but copy/paste didn't work.
I've never used VPX so you'll need to check it to see if it has an EDL text file export function.
In my experience, exporting an EDL project from VP and importing it into an earlier VP version imports the media only - with basic crossfades and fades - but without any FX at all whether they be native Vegas FX or 3rd party OFX plugins.
Re the availability of EDL export functions in MMS and VPX, you'll need to raise that issue in MAGIX's video forum at https://www.magix.info/us/video-forum/
Hi,
As has been pointed out, there is currently no way to import Magix MS/VDL/VPX projects into Vegas. (VDL - Magix has changed the name to the commonly used international name, Video Deluxe, with version 2026).
Vegas Movie Studio projects can be imported into MS/VDL/VPX, but not the other way round. And, only the events are imported, no titles, no effects. Importing a Project would be unlikely as VPX has multiple timelines (Movies) whereas as Vegas does not. Thus, a project with more than 1 Movie could not be imported into Vegas as it only has a single timeline. However, making a way to import a specific Movie into Vegas should be possible (see below). Titling and effects are completely different, so I doubt that they could ever be imported.
@Dexcon VPX can export to EDL, but the format is specifically made for exchanging between VPX and Samplitude/Sequoia. Trying to import an EDL file into Vegas, created using VPX, results in an error. The format of VPX and Vegas EDL files are completely different. On that point, rhetorical question, why does Vegas import EDL use .txt extension and not .edl? How would one know that it's an EDL file? No need to reply.
The Vegas team should be able to create a separate Import EDL for VPX that just reads the information and puts it on tracks at the locations indicated. Or, perhaps someone can create a script to do this.
Here is a link to an EDL file exported from VPX. You can open it with Notepad. Note that the EDL is for a specific Movie (timeline) within a project that contains several Movies. The name of the Movie is "Nathalie - Reste avec moi.MVD" where .MVD is the extension for a Movie. The extension for the Project itself is .MVP.
OT - I have created a database application of projects/movies and multimedia. It contains filenames, some EXIF information and other information, like categories (tagging), my comments, etc. Using the EDL file, I can read the Source Table Entries into the application and link the multimedia files to the movie which is linked to a project. I can then see if a source multimedia file has been used in a project. Projects can be video projects, audio projects, image projects, Word, etc., and they can be linked together. So, I can link a video project to the text for narration created using Word, along with a scoring project created using a DAW. Etc. I haven't tried importing from a Vegas EDL file, but it looks simple as the EDL file is well-structured for opening and importing into a database table.
John CB
Hi
Thanks!
➡ VPX exports a Samplitude-style “EDL” — complex, full of metadata.
➡ Vegas expects an “internal Vegas CSV,” called EDL, and in my understanding it should have a different name.
➡ The two are completely incompatible.
➡ and for the following reasons has no incentive to resolve this on the Vegas side.