Export for Premiere

Peter-V wrote on 7/8/2023, 5:21 PM

Just wondering about the possibilities of exporting projects from VEGAS Pro to other video editing softwares like Premiere. Right now it seems a little unstable or neglected? I've rarely gotten this to work, even with less complicated projects. One of the main barriers to using VEGAS in a professional environment is that you can't collaborate with other team members or clients commonly using the Adobe suite. Does anyone know if this is ever to be improved/changed in VEGAS or is it a lost cause?

Comments

lan-mLMC wrote on 7/8/2023, 9:17 PM

Since Premiere and Vegas are competitors, and Premiere is the market leader. So there is a possibility that Adobe Premiere is constantly reinforcing their policy with each update to reject .prpro files generated by Vegas.

Robert Johnston wrote on 7/8/2023, 9:41 PM

@Peter-V

@lan-mLMC

The only way I know of to export from Vegas Pro 20 and import to the latest version of Adobe Premiere Pro (Cloud) is to export using the Final Cut Pro 7/DaVinci Resolve XML option. Then in Premiere Pro, open the XML file. Practically no effects will translate, just your trimming, opacity, cross-fades, volume, panning. Works just about as well in Premiere as it does in Resolve.

Can't comment on the collaboration aspect.

Peter-V wrote on 7/9/2023, 6:16 AM

@lan-mLMC doesn't that seem a bit conspiratorial? Having been a user of Premiere (and working with many Premiere users) there seems to be other issues and goals the community and developers are focusing on. Spesifically spending valuable developer time to stifle VEGAS created .prpro files seem like a very odd prioritization to me, even in the name of compitition.

@Robert Johnston Yes, this is the only method I've had any luck with as well. It seems to be the consensus around this issue. But this does beg the question; why even have the feature there? It doesn't work at all and hasn't worked for a long time. Maybe it's time to just remove this Premiere spesific export feature and replace it with a .xml "Export for use in other video editors" feature instead?

Anyways, thanks for commenting on my issue. I guess I was just looking for other potential insights or tips to see if there's anything I hadn't tried yet.

Former user wrote on 7/9/2023, 7:59 AM

@Peter-V Hi, do Vegas projects open in other software besides premiere using the XML etc..?

In my novice view I see Windows as the Android version to an Apple, as with a lot of phone apps they'll open in an android phone but won't in a iPhone or you have to choose the correct option when installing, Just like My Boris plugins, OFX will work in pretty much all software except Adobe, I had to pay extra for an Adobe Licence & download to use them in After Effects,

There's a chance the prpoj link might get updated, but because Adobe is a differently based software it might not be that easy to change, It might not be quite a conspiratorial type thing but maybe just a bit of 'neglect' by the Vegas developers, Vegas has limited staff so prob it's not high on their list of things to do & that 'neglect' might be more of subsequence of not having the money or personnel to think about it, , The prpoj might also be a redundant appendage that would cause more harm to remove then it would be to just leave it be.

Peter-V wrote on 7/9/2023, 8:15 AM

I appreciate your insights on the cross-platform issues we encounter in the realm of video editing. The analogy of Windows to Android and Apple to iPhone illuminates some interesting parallels.

However, I would like to gently disagree with your point on the .prproj export feature. If indeed it is a neglected feature that doesn't function as users might expect, it might be better to remove it. Newcomers to the software might be misled, thinking it works as they would naturally assume, and they could end up wasting precious time.

Resource constraints are a real issue for any development team, including VEGAS'. In light of this, I believe that refining or removing features that don't work as expected would serve the user community better in the long run. If the .prproj export is problematic, it may be more prudent to focus on those features that add tangible value to users' workflows, like the XML export, which operates smoothly and is useful.

Please understand that this is just a perspective. I value your contribution to the discussion, and it's great to exchange ideas on these matters.

@Former user

Dexcon wrote on 7/9/2023, 8:18 AM

Have you tried an EDL export?

As mentioned before, the export/import options in Vegas Pro will only read the basic edit. It's been highlighted before on the forum that Vegas Pro doesn't read other NLE FX (and vice versa).

Peter-V wrote on 7/9/2023, 9:03 AM

@Dexcon Thank you for your suggestion. I have indeed used the EDL export feature and found it to be as functional as the XML export. This feature certainly does a good job in enabling basic edits to be transferred from VEGAS to other editing platforms.

That being said, I agree with your point about the limited feature set transferability across NLEs. But this brings me back to the .prproj export specifically, which has consistently generated errors in Premiere for me, regardless of how simple or complex the project is.

Given that the XML and EDL exports work for transferring simple edits, it's puzzling why the .prproj export feature is present when it doesn't seem to function at all. If its implementation is currently beyond the means of the VEGAS team, it might be more user-friendly to omit this option rather than having it create confusion and waste time when it doesn't work as expected.

Anyways, your insights are appreciated, and these discussions are certainly beneficial for the entire community (even though similar discussions can be found throughout time).