Comments

NormanPCN wrote on 5/7/2014, 10:20 AM
Vegas 13 added no new features that required and change to the project file format, so it makes sense to not change the file version number.
cold ones wrote on 5/7/2014, 10:40 AM
Suppose so, but regardless it's nice that they're allowing this. It means that I can work in v13 and if there's any problem I can resume in v12. I'm beginning a new project and it's a perfect time to upgrade.
videoITguy wrote on 5/7/2014, 12:46 PM
SCS has already explained this behavior as an oversight in programming - it was NOT supposed to work this way and it will be changed in upcoming version release.
Of course, the reason being that there are some deployments where this reversion to an earlier form of project is not likely to work and then you will be having fun wondering what happened.
wwjd wrote on 5/7/2014, 1:25 PM
:O

"NOT supposed to work this way"

gah! Compatibility would be one killer feature to keep! Sad.
MTuggy wrote on 5/7/2014, 2:28 PM
It would be nice to have a "Save as v12" or other previous version option. That would be customer oriented.

Mike
NormanPCN wrote on 5/7/2014, 3:02 PM
SCS has already explained this behavior as an oversight in programming

I believe the oversight was that Pro 13 will not import Movie Studio 13 VF files.

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=893287
videoITguy wrote on 5/7/2014, 3:16 PM
You are right NormanPCN to point out what was carefully explained in the previous thread...however, these issues are exactly interrelated. The "flag" in the .veg was not updated by the forthcoming programming to be worked as has always previously been maintained.

To put it another way, there was no intention by recent code pushed into VegasPro13 to put in a save as option as many of us have pleaded for in the past over many years. It just so happens that leaving the .veg flag at version 12 is a happenstance under the regular save project menu.

I am certain that you understand that as most people have come to realize the release of Version 13 was a re-working of the last version 12 build 770 in beta. We already were aware of that and thus it is easy to understand what the code writer overlooked in buttoning up the last build.