how to use Pro 13 file in Platinum 11?

joe-winko wrote on 4/20/2016, 8:30 AM

I've been having a lot of problems with sony vegas pro 13 and i dont want to use it. I just finished working on a big project in Sony Vegas Pro 13 but i can't render it

I wanted to try rendering it in sony vegas platinum 11 instead. but i can't open the file in sony Vegas platinum 11.

is there any other way i can get it to work in sony vegas platinum 11? isn't there a way i could just import all of the media files i used for the project into sony vegas 11 then use some trick to have them all on the timeline in the exact way i arranged them in the sonyvegas 13 file without me having to do it manually?

Please help <3

Comments

D7K wrote on 4/20/2016, 9:37 AM

You haven't told us about your system and what specific issues you are having. Why don't you just render segments in PRO and then re-render all of the rendered segments to see if that works.More information is needed for anyone to help. Did you post a "help me" in the PRO forum?

vkmast wrote on 4/20/2016, 9:50 AM

I don't know any way to make it work in VMSP 11.
You could try to install the trial of MSP 12 or 13 (64-bit). Try to "Select Events to End" and Copy / Paste (Ctrl+C / Ctrl+V) on timeline tracks from VPro 13 to MSP 12/13.
Don't remember if it gets a watermark when rendering in MSP 12/13 trials as it does in VPro 12/13.
You could try if MSVPVF works with VPro 13- - -MSP 13. Haven't tried.

You should actually find out why you get crashes when rendering.
Overheating?
Troubleshooting crashing

Tim L wrote on 4/20/2016, 11:55 AM

There is a privately developed program "Vegas Pro Faker" that changes certain flags within the project file -- .veg or .vf (or whatever file extension Movie Studio uses) -- to let it be opened by an older version. I've never tried it, but it might be worth a try. Of course, it would not be able to bring "newer" features (filters, transitions, etc.) into an older version of Vegas, or Pro features into Movie Studio.

http://www.ipadtouches.com/movie-studio-vegas-pro-version-faker-msvpvf/

Here is an old thread in the Vegas Pro forum that discusses it. There may be others.
http://www.sonycreativesoftware.com/forums/showmessage.asp?messageid=887072

joe-winko wrote on 4/20/2016, 12:19 PM

@Tim L

I tried that, but whenever i try to open the new file with the changed flags, it then gives me the error message: "an error occurred reading the file. make sure you have read access to the file/folder and that it is not corrupted"

@vkmast
the trial version does leave a watermark on rendered videos so i dont want to use it

@D7K
what information is needed?
and i tried rendering pieces of it in the file on vegas pro 13 but they still wont render and it still crashes. and yes i did post a help thread on the vegas pro section of the forum too.

what im trying to is figure out how to get the media files in sonyvegas movie studio 11 and have them all be aligned up the exact same way they are in the vegas pro 13 file without having to drag and drop them all in manually because that would be complicated and takes for ever.

isn't there a way you can type in a number on some setting for each clip to have it be placed in a certain location on the timeline? (not sure if that made sense but i hope it did)

vkmast wrote on 4/20/2016, 1:53 PM

>>>the trial version does leave a watermark on rendered videos so i dont want to use it<<<

Have you actually verified this yourself? I know the VPro 13 trial gives you the "Created with Vegas Pro" watermark, but I do not remember users reporting similar with MSP. The only mention I found (besides my own inquiry on these forums about this issue, which nobody confirmed one way or another) was the pcmag.com review of MSP 13: "A free trial download is available for all levels, and unlike most of the competitors, it doesn't put a watermark on videos you produce or limit project sizes."

Another matter is that it probably won't render anyway given the issues you're having ATM, so all of this may well be only academic.

edit: I see from your Pro thread that the GPU was the culprit.
Not for the first time, SCS KB: Troubleshooting crashing, point 2.