How to open newer project files in older version.

FocusOnVegas wrote on 3/8/2014, 12:42 PM
Normally it isn'’t possible to load a project file in Sony Vegas or Movie Studio if the project file was made with a newer version. That is what I experienced when I tried to open a Movie Studio 13 project file in Vegas Pro 12. So even if you don'’t use the new features of a new version you can not read your project files in older versions of Movie Studio or Vegas.

I made a free program “Movie Studio / Vegas Pro Version Faker” (MSVPVF) that can change the flags for the version number and even the file type (Movie Studio or Vegas Pro) of a project file. So when you '‘ll open the project file in the older program, the program '‘ll read the (changed) version number and '‘ll load the project file. This little “cheat” seems to work surprisingly well, at least with Movie Studio 13 and Vegas Pro 12. Of course don’'t use the new features of the newer software that don'’t exist in the software / file format you “convert” to.

More info : www.ipadtouches.com

Comments

videoITguy wrote on 3/8/2014, 12:56 PM
For VegasExtended - I would like to see some of our programmmers test your patch, as this would be quite a feat and comes closest to previous export/import XML method of working with VegasPro.
Understand that this does nothing but traverse a simple edit assembly and will lose most plugins and effects.
Key frames is a question.
Lets put your system to the test.
FocusOnVegas wrote on 3/8/2014, 1:09 PM
My program is not changing the file content, except the flags for version and, if selected, the file type.

But for basic editing with Movie Studio 13 and Vegas Pro 12 it seems to be sufficient.

Don't expect features that are not present or are different between versions or between Movie Studio and Vegas pro.

Give it a try for basic editing and let me know the results.

videoITguy wrote on 3/8/2014, 1:13 PM
Did you know?
Subject: RE: Using XML Export in Vegas Question
Reply by: Gary James
Date: 3/18/2013 7:11:03 AM

If you're using the supplied Vegas scripts to Export / Import a project to XML, the XML file reflects the internal Sony Vegas Object hierarchy, structure, and programming interfaces. This was not meant to adhere to any sort of project interchange standard.

I always looked at this as a way to get a newer Vegas project to open in an older version of Vegas. And as an example of how to write a script to access the Vegas programming API.
FocusOnVegas wrote on 3/8/2014, 5:17 PM
An interesting forum topic about using XML Export in Vegas.

I made a project file in Vegas pro 12 with several clips, a page roll transition, a NewBlue 2.0 titler title, a Sony sharpen effect with keyframes, a Sony Defocus effect with keyframes and a Volume envelope on the audio track.

An XML export in Vegas (Final Cut Pro / DaVinci Resolve XML) gave me a log with a lot of " ignored" stuff. Movie Studio was not able to import the xml file.

Then I used MSVPVF and changed with it the version flag of the veg file to 13 and the file type flag to Movie Studio (veg --> vf file).

The results after loading the vf project file in Movie Studio 13 Platinum:
- All the clips are present.
- The transitions are present.
- The NewBlue title is present (I bought sometime an upgrade to NewBlue titler 2 so I can use it with Vegas pro and Movie Studio).
- The Sony sharpen effect is present with keyframes.
- The volume envelope (with envelope points ) on the audio track is present.
- The Sony defocus effect is not present.
- An error message that the Defocus effect is not present on my system. This is correct, this effect is not a member of Movie Studio 13 Platinum.
After confirmation of the error message everything seems to be OK.

So at this moment I haven't found a better solution for close related versions (for basic editing) like Vegas Pro 12 and Movie Studio 13.

Please, let me know what your experiences are with "Movie Studio Vegas Pro Version Faker (MSVPVF" .



videoITguy wrote on 3/8/2014, 5:48 PM
so by your last comment, you have not tested Vegas12 Pro project loaded into VegasPro 10 or evenPro 11? - hence what is the validity of your forum topic title?
FocusOnVegas wrote on 3/9/2014, 6:42 AM
You are right.

Although it is working for Movie Studio 13 and Vegas Pro 12, it appears not to work with older versions.

It appears to work only with Movie Studio 13 and Vegas pro 12 project files !

This workflow is working for me (till I '‘ll experience problems) :
- Editing in Vegas 12.
- Vegas pro 12 project (veg) file to Movie Studio 13 project (vf) file (with MSVPVF).
- Editing in Movie Studio 13.
- Movie Studio 13 project file to Movie Studio 12 project file or Vegas pro 12 project file (with MSVPVF).
- Editing in Vegas pro 12

or
- Editing in Movie Studio 13.
- Movie Studio 13 project file to Movie Studio 12 project file or Vegas pro 12 project file (with MSVPVF).
- Editing in Vegas pro 12.
- Vegas pro 12 project (veg) file to Movie Studio 13 project (vf) file (with MSVPVF).
- Editing in Movie Studio 13.

Common features between Movie Studio 13 and Vegas pro 12 seems to be preserved.

So I think the file formats of the project files of Vegas pro 12 and Movie Studio 13 are more or less the same.

If other combinations are working, please let me know.

videoITguy wrote on 3/9/2014, 10:21 AM
Indeed, the project flag was to distinguish whether the test version of the veg was concurrent with the equivalent version of the movie studio project.

In other words, as we had suspected is that in many ways the older generation of the VegasPro corresponds roughly to one-up in the generation of the Movie Studio release.

Hence VegasPro 12 to Movie Studio 13
or
VegasPro 10 to Movie Studio 11.

Backward compatibility between versions of each product line has not been established.
FocusOnVegas wrote on 3/9/2014, 4:02 PM
You are right that there is no backwards compatibility between versions of the Vegas pro and - probably the Movie Studio product line.

But Movie Studio project files (.vf) made from older versions of Vegas pro project files (.veg) with MSVPVF seem to load in Movie Studio 13 as well (although I found no way back to the older Vegas pro version).

I made a (native) Vegas pro 10 test file with Vegas Pro 10. The testfile contained several clips and 5.1 audio. I muted the LFE audio channel. I named the channels. I added a clock wipe and an iris transition. I added a volume envelope on one audio channel and a surround pan on the rear audio channels. I added a composite level video envelope and at one clip a Sony Border and Sony Black and white (50 %) effect. After saving the Vegas pro project file I "flagged" the Vegas project file with MSVPVF as a Movie Studio version 10 project file. The complete project, including the attributes, loaded without problems in Movie Studio 13!

So there seems to be a way to use older Vegas pro project files with MovieStudio, at least with version 13. Maybe useful for people with an older Vegas pro version who are satisfied with the newest version(s) of Movie Studio.

rstrong wrote on 3/9/2014, 8:21 PM
So what could I gain, to open a project from a Pro version into a newer Studio version ?

R. Strong

Custom remote refrigerated water cooled system for CPU & GPU. Intel i7- 6950X, 10 Core (4.3 Turbo) 64gb DDR4, Win7 64 Bit, SP1. Nvidia RTX 2080, Studio driver 431.36, Cameras: Sony HVR-Z5U, HVR-V1U, HVR-A1U, HDR-HC3. Canon 5K MK2, SX50HS. GoPro Hero2. Nikon CoolPix P510. YouTube: rstrongvideo

FocusOnVegas wrote on 3/10/2014, 2:47 AM
You can use / add the new features of Movie Studio that are not present in older versions of Vegas pro. This with Vegas project files that were made with an older version of Vegas pro and without the obligation to buy an (another) upgrade of Vegas pro. Example : easy proxy editing, new file formats, new effects that are only present in Movie Studio (Platinum).

MSVPVF is free and anyone can try what works in his own situation (version of Vegas pro and Movie Studio) and what doesn't work.



joe-winko wrote on 4/20/2016, 6:32 AM
when i tried using it, I was trying to open up a Sony Vegas Pro 13 file in Sony Vegas Movie Studio HD platinum 11 (the reason why is because i wasn't able to render it in sony vegas pro 13 because an error would keep happening. i was trying to render it in wmv.)

I was able to convert it/change the flags with your software so it could be opened in sony vegas movie studio platinum 11, BUT when i tried opening it i got an error message that said:

"An error occurred while loading the project file. Make sure you have read access to the file/folder and that is is not corrupted."

is there any way to fix this? :(
Duke_Hamburger wrote on 12/2/2016, 1:38 PM

Well, I tried the program seems to work fine. I tried to convert a svp 12 project to a svp 11 project. After done loading, I opened the file it created and than this error showed up:

If anyone could help, thanks!

Alucard01001 wrote on 1/22/2017, 4:07 PM

Well, I tried the program seems to work fine. I tried to convert a svp 12 project to a svp 11 project. After done loading, I opened the file it created and than this error showed up:

If anyone could help, thanks!

Absolutelly the same problem. I wish to open .veg file from vegas pro 12, i use the program to "convert" the file suitable for vegas pro 11 and when i finally come to open it, i get this message. Please help

NickHope wrote on 1/22/2017, 9:22 PM

Maybe try converting to VP10 or even older format, then opening that in VP11 and saving it as VP11 format.

Alucard01001 wrote on 1/23/2017, 12:45 AM

Tryed all the way to version 6, no effect