Comments

dimipapa wrote on 12/3/2014, 1:15 PM
Usually .veg files are designated to one version of vegas on your computer. When you open 12 does it have a message like "do you want these files associated with this program blah blah blah" if it doesn't then does 13 have that message?
Geoff_Wood wrote on 12/3/2014, 2:18 PM
Um, that's a FEATURE that has long been requested - backwards file compatibility !

Are you sure something is being lost or is out of whack (apart from things just generally being out of whack) ?

geoff
Chienworks wrote on 12/3/2014, 5:35 PM
In short, this isn't Vegas, it's your Windows install. Windows doesn't know about Vegas versions. It just knows that a .veg file should be opened by Vegas. When you installed V13 it didn't inform Windows that it was now Vegas.

Right-mouse-button click on a .veg file and choose Open With. Browse to (probably)
C:\Program Files \ Sony \ Vegas Pro 13.0
(this will vary depending on your Windows install on your particular computer), find vegas130.exe (i assume this is the name, i don't have version 13 installed), and select it. Now find the checkbox that says "always open this file type with this program" and check it.

Windows now knows to open .veg files with Vegas 13 instead of 12.
NickHope wrote on 12/4/2014, 2:24 AM
+1 Chienworks.

But MikeyDH, in what way is Vegas Pro 12 throwing things way out of whack?

VP12 and VP13 are the first 2 versions I remember that feature backwards compatibility, I suppose because the lack of new features in VP13. I'm really pleased SCS have allowed it. I have many times opened VP13-created projects in VP12 to access the Peachrock Veggie Toolkit (which doesn't support VP13), to get functional closed captioning, to avoid crashes when renaming files, or simply to test things. I have never noticed anything go "wrong" by doing this.
MikeyDH wrote on 12/4/2014, 5:30 AM
Thanks Chienworks, I'll put that to use.

Nick, I have noticed that images that were pan cropped reverted back to original as well as some 3rd party FX.
NickHope wrote on 12/4/2014, 7:15 AM
Ah OK Mikey, I'll look out for those.