EDL from Vegas to Premiere Pro cs6

avp

avp

Well-known member
Is there a reliable and accurate method whereby I can
export an edl (edit decision list) into Adobe PP CS 6 from Sony Vegas 10. I have done the "save as" avid legacy AAF file as well as th Edit protocol compliant AAF File. I was able to import those into PP and get media onto the timeline (with a lot of directing PP to the correct file locations) but a lot of the media was incorrect, did not bring audio along with it, or simply would not play.

i might add that I am working cross platform with Vegas on a pc and PP on a Mac...for what that,s worth. i am working from completed Vegas projects with music, gfx, titles and so forth.

thanks, jeff
 
Vegas 10 doesn't export a proper EDL, but that doesn't matter, because no EDL would do what you've described here. EDLs contain basic information only, and usually with a maximum of two video and audio tracks, and will contain simple cuts only -- no fades, etc. No titles, no FX, no color-correcting, etc.

Later versions of Vegas will export a project in Premiere Pro format (and others, like FCP, FCPX, Avid, Pro Tools), but that's of varying usefulness, and less so as the project gets more complicated, FX are added, and the like.
 
Thanks for your response, David.

We have about 15 - 1/2 hour shows that have been edited solely in Vegas. Now the client wants to move over to Premiere however most if not all of the shows have 20 or more video/audio tracks with varying amounts of fx, titles, and so forth. As I suspected, having multiple tracks/fx as I described could/will cause issues with exporting an EDL into Premiere even with the latest iteration of Vegas.

My ultimate aim is not to duplicate these projects but simply get the camera cuts on a Premiere timeline for locating raw footage and clips.

In your opinion, do you think Vegas 12 or 13 would at least give me an EDL that would transpose into Premiere (even despite the multiple tracks, etc.) well enough to have the cuts on the timeline while omitting fades, fx, titles and such or would I be tossing a few hundred $$ out the window. Vegas 10 generated an EDL that was readable by Premiere but what wound up on the timeline (in Premiere) was inconsistent (to say the least) with the Vegas timeline.

Certainly it is not an option and too time intensive to go into each and every Vegas project and omit the fades, titles...in hopes of a more usable EDL.

Best, Jeff
 
You won't be able to do an "effective" EDL unless you can get the whole project down to two tracks of video and two tracks of audio.

As for being able to transfer whole projects between NLE platforms, that's just something which can't really be done with complex projects if you want to keep everything intact. There's enough trouble getting it all to play nicely with Premiere projects between Windows and OS X.

Like I said, later versions of Vegas have the ability to export a .pproj file for opening the project in Premiere, which may be your best bet, but it probably won't be 100%. It will most likely be better than an EDL, though.
 
Thank you David.

To mix down to two tracks of audio and two tracks of video for our existing projects likely would not be workable.

As we are moving forward with a second season to be edited on Premiere and given that I am really fast with Vegas, would you say it is reasonable to do the initial camera sync (4 to 6 cameras) on a Vegas timeline (Vegas 13, that is) then export a .pproj and have an expectation that more than 4 total tracks could accurately be brought into Premiere Pro CS6?

Basically, I'd like to do all the camera sync, rough edit, and dialogue audio cuts in Vegas and then export to Premiere for CC, FX, music, titles, and so on. Would that juice be worth the squeeze (and the money for upgrading to Vegas 13). BTW, my first NLE was Premiere over a decade ago and I jumped that ship almost 9 years ago in favor of a (at the time) much more stable Vegas so I am relatively new to Premiere's GUI, controls, and workflow hence my wanting to work as much in Vegas as possible to save time in post.

Jeff
 
To resurrect this thread, I went ahead and bought Vegas 13, installed, and have been trying to export to Premiere Pro. Following advice from other sites/posts and working from a simple 3 track audio/3 track video project, I first tried the export as .prproj format, copying media with the export. Tried to open that project and got the message "A serious error has occurred that will require premiere to shut down. We will attempt to save your project".

I then tried the AAF format and did manage to populate the timeline with the media but only on two tracks. I'd love to see a timeline duplicate from Vegas with the understanding that I will not expect transitions/ fx, and the like.

Anyone have an idea as to what I may be doing wrong.

Thanks...

Edit: BTW, I am working cross-platform with Vegas on a pc and Premiere on a Mac Pro.
 
Last edited:
Perhaps the issue is moving the .prproj file from Windows to Mac? I still get the message:

"A serious error has occurred that will require premiere to shut down. We will attempt to save your project".
 
I've never tried moving a Vegas-generated .pproj file to a Mac, so that's pretty much uncharted territory for me. I do know that Premiere projects are not 100% compatible cross-platform, as I mentioned.
 
avp said:
As we are moving forward with a second season to be edited on Premiere and given that I am really fast with Vegas, would you say it is reasonable to do the initial camera sync (4 to 6 cameras) on a Vegas timeline (Vegas 13, that is) then export a .pproj and have an expectation that more than 4 total tracks could accurately be brought into Premiere Pro CS6?
Click to expand...

I think the best long-term solution is to drop both Vegas and the rather dated CS6 and do everything in the newest Premiere CC. You will never become proficient with it until you use it regularly. Take the small hit for learning new software and gain that proficiency.
 
Thank you Jim and I have to agree. I also must apologize for an error in my posting. We have installed the latest Premiere CC and erroneously posted that we are using CS6.

So I am in the throes of shifting from nearly a decade of editing on Vegas back to Premiere which I used in the early 2000s for a few years back then (and buggy as hell then, I might add).

Best, Jeff
 
You must log in or register to reply here.
Back
Top