Comments

PeterDuke wrote on 8/12/2014, 2:19 AM
Yes, that is the general rule: forward but not backward compatibility.
John_Cline wrote on 8/12/2014, 3:45 AM
Yes, once you save them in Vegas 13, you can no longer open them in Vegas 10.
TheHappyFriar wrote on 8/12/2014, 5:34 AM
So open them and then "save as" with a "_13" at the end (or something). Autosave will overwrite your "old" veg file.
PeterWright wrote on 8/12/2014, 7:06 AM
Yes, this has always been the way, forward compatibility, but not backward ..... until this years release of V13.

Files saved in V13 can be opened in V12 - presumably because the same basic structure was used for both versions.
Chienworks wrote on 8/12/2014, 7:39 AM
"Files saved in V13 can be opened in V12 - presumably because the same basic structure was used for both versions."

Or because no new internal features were added in version 13, which would have required new data structures. *THE* reason for no backward compatibility is because new versions contain new features that didn't have any place to stored in the previous versions' .veg files' data structure.
Grazie wrote on 8/12/2014, 8:18 AM
Yup. 'cept the Windows Layout Keystrokes. They don't appear to have been cross-version compliant. I just got the: "You are using and older . . Layout . . blah blah".

Grazie

TheHappyFriar wrote on 8/12/2014, 5:52 PM
Kind of related, over the weekend I found that if you use a Vegas with cinescore data in it, the 64-bit version reads that as a plain wav file. The 32-bit version of Vegas reads the cinescore data. So you can still edit the cinescore files after you modify the veg in 64-bit vegas.

pretty cool!