Premiere CC 2019 won't read .prproj created by Vegas Pro 16.

Norbert wrote on 5/5/2019, 2:34 PM

I wanted to export a project from Vegas Pro to Premiere CC 2019 but Premiere crashes when I try to open the file. I found out that an .aaf file can make the magic trick but messes up the soundtracks, every stereo is read as mono and Premire creates lots of new soundtracks for no reason. I have to change the sequence' resolution, too because it's read incorrectly.

Comments

Norbert wrote on 5/5/2019, 2:52 PM

Okay, I've found that aaf doesn't support stereo tracks

"Any track that has mono and stereo audio will be ignored; the AAF format does not allow mono and stereo audio on a single track."

wjauch wrote on 5/6/2019, 7:20 PM

FWIW last year I tried loading a Premier Pro project into Vegas15, that didn't work either.

 

Norbert wrote on 5/9/2019, 11:48 AM

At least with AAF it works...

tdfilmstudio wrote on 12/17/2019, 9:21 AM

I have been waiting for this problem to be solved for a long time. Exporting Vegas projects in .prproj format does not work in new Adobe Premiere or After effects. No explanation given by Vegas pro Team, and no assurance regarding possibilities of a solution in future versions.

joost-berk wrote on 12/18/2019, 2:07 PM

The best way (for me) to import or export between Vegas and Premiere is to use .XML files (Final Cut 7/DaVinci Resolve). You won't get your effects with this methode. But at least you get Premiere to work with Vegas Pro and vice versa.

Vegas Pro user since version 1.2

OS: Windows 10 Pro (Latest version)

CPU: AMD Ryzen 7 3800X

RAM: 32GB DDR4 3200MHz

GPU: Nvidia GeForce RTX 2080 Super 8GB GDDR (Latest Studio Driver)

Monitoring: Black Magic Design DeckLink SDI 4K (or Nvidia HDMI for 4K HDR)

Audio: M-Audio M-Track Eight ASIO

Controller: Behringer X-Touch

Silverglove wrote on 4/16/2020, 11:15 AM

Bump. I just tried this with V17 and Premiere CC 2019. This is a no go and has never worked in the past. Very frustrating.

Deata wrote on 4/18/2020, 12:16 PM

I dont get why there has been the option to export to premiere in every release of vegas pro for the past 10 years when its never actually worked.

Why do they keep adding it the new releases when its broken and there is absolutely no way to get it working as a user.

 

Its literally like they just added an export function just to say that hey have the ability to export to premiere but never bothered to actually code the damn thing

Musicvid wrote on 4/18/2020, 12:30 PM

The simple answer is that Vegas and Premiere are competitors, and don't share a common protocol. It is what It is.

Deata wrote on 4/18/2020, 1:45 PM

The simple answer is that Vegas and Premiere are competitors, and don't share a common protocol. It is what It is.

Huh, then why include the ability to export to premiere at all?

And weirdly these type of issues seem to only affect vegas and not any of the other competitors that premiere has like resolve.

They export just fine.

 

Kinvermark wrote on 4/18/2020, 3:28 PM

It did work for super simple timelines many years ago. My assumption is that it is kept in the program for the "one guy" who still uses it.

IMO, there is absolutely no point in wasting resources fixing it. Contrary to your experience, there are many, many limitations and problems from all sort of NLE's in project interchange. It would, as @Musicvid has intimated, require some level of cooperation between competitors. (I think Pixar or Disney is working on the latest attempt at an open standard.)

Try using a FCP7 xml export. That is the closest to an industry standard we have for interchange. If you stick to a simple timeline and use clips with timecode, then it should work (does with Vegas to Resolve.)