As per the subject line, my story below:
I inherited numerous Vegas Pro 11 projects, many of which use now obsolete 32 bit plug-ins. Opening these projects in Vegas Pro 13 (or 12) produces a plug-in warning, and where the plug-in was used is stripped from the project timeline. As I want to modify and render these projects as per my requirements, and retain the plug-in usage, I choose to convert the projects from Sony Vegas Pro 11 to Movie Studio 13 Platinum using an application that was intended to enable Vegas Pro Projects to be opened in older versions of Vegas Pro.
The application is called: Movie Studio Vegas Pro Version Faker (MSVPVF) and is available free here: http://www.ipadtouches.com/movie-studio-vegas-pro-version-faker-msvpvf/
(Although the application is free, for anyone that does use it, I think the programmer does deserve to receive a donation.)
How I used MSVPVF:
1. Select the Vegas Pro project file.
2. Set the 'New File flag (version)' to 12, and 'New File format' to Movie Studio.
3. Click 'Write new file with new flags’.
Notes:
- In step 2, version 12 had to be selected and not version 13, else Movie Studio 13 claimed that the project file had been created in a newer version of Movie Studio.
- Step 3 creates a Movie Studio *.vf project file in the same directory as the source project file.
- The Vegas Pro project file is not harmed in any way by the making of this Movie Studio project file.
The new project file can now be opened in Movie Studio 13. You will see a message that the project was created in an older version of Movie Studio; saving the project fixes that problem. Job done!
I have the 32 bit and 64 bit versions of Movie Studio 13 Platinum on my PC, so when I open the converted projects in my 32 bit version, the project loads without any warnings and I can see where and how the plug-ins were used. Over time I will replace them with a close 64 bit equivalent.
In two days I converted 330 Vegas Pro 11 projects to Movie Studio 13 Platinum projects. I was very pleased with conversion results. The only problem area was where embedded projects had been used. This I got around by replacing the embedded project with an uncompressed rendered file of the embedded project. The file, which was huge, was then deleted, and will be recreated when needed.
One of the converted projects contains over 220 video clips, titling, several video and audio tracks, 35 markers, all sorts of color and sound adjustments, event pan and crop, cookie cutter effect, and cross-fades - it converted perfectly. Provided the feature used in the Vegas Pro project exists in Movie Studio, then the conversion may well go smoothly, as it did for me.
I inherited numerous Vegas Pro 11 projects, many of which use now obsolete 32 bit plug-ins. Opening these projects in Vegas Pro 13 (or 12) produces a plug-in warning, and where the plug-in was used is stripped from the project timeline. As I want to modify and render these projects as per my requirements, and retain the plug-in usage, I choose to convert the projects from Sony Vegas Pro 11 to Movie Studio 13 Platinum using an application that was intended to enable Vegas Pro Projects to be opened in older versions of Vegas Pro.
The application is called: Movie Studio Vegas Pro Version Faker (MSVPVF) and is available free here: http://www.ipadtouches.com/movie-studio-vegas-pro-version-faker-msvpvf/
(Although the application is free, for anyone that does use it, I think the programmer does deserve to receive a donation.)
How I used MSVPVF:
1. Select the Vegas Pro project file.
2. Set the 'New File flag (version)' to 12, and 'New File format' to Movie Studio.
3. Click 'Write new file with new flags’.
Notes:
- In step 2, version 12 had to be selected and not version 13, else Movie Studio 13 claimed that the project file had been created in a newer version of Movie Studio.
- Step 3 creates a Movie Studio *.vf project file in the same directory as the source project file.
- The Vegas Pro project file is not harmed in any way by the making of this Movie Studio project file.
The new project file can now be opened in Movie Studio 13. You will see a message that the project was created in an older version of Movie Studio; saving the project fixes that problem. Job done!
I have the 32 bit and 64 bit versions of Movie Studio 13 Platinum on my PC, so when I open the converted projects in my 32 bit version, the project loads without any warnings and I can see where and how the plug-ins were used. Over time I will replace them with a close 64 bit equivalent.
In two days I converted 330 Vegas Pro 11 projects to Movie Studio 13 Platinum projects. I was very pleased with conversion results. The only problem area was where embedded projects had been used. This I got around by replacing the embedded project with an uncompressed rendered file of the embedded project. The file, which was huge, was then deleted, and will be recreated when needed.
One of the converted projects contains over 220 video clips, titling, several video and audio tracks, 35 markers, all sorts of color and sound adjustments, event pan and crop, cookie cutter effect, and cross-fades - it converted perfectly. Provided the feature used in the Vegas Pro project exists in Movie Studio, then the conversion may well go smoothly, as it did for me.