I accidentally saved my vegas 13 as vegas 17 and now I'd like to stick to using vegas 13 but I cant open it. Is there any workaround that would enable me to either open it or copy its media files with same timings to a new vegas 13 project so that I can save it as Veg13 project? I hope there is a way to open my project on Vegas 13..
Thank you
Still have any .bak files of the old version?
You might have to open both versions and copy/paste between. Unfortunately you won't get every setting so you'll have to recreate some of your work
Yes, I have the .bak file. What should I do with it? I tried copy paste but it didn't work, how do I copy-paste, how can I see the bak file? Is there any way it will transfer all my settings, crops, etc?
From the .bak file you have to delete .bak en than you have the almost latest project file you are able to open.
From the .bak file you have to delete .bak en than you have the almost latest project file you are able to open.
Could you help me understand what you mean?
When the BAK.file is also rewritten as Vpro17, then you can try with this free tool from this site: https://www.focusonvegas.com
There is no garantee because development was stopped with Vpro16, but at least you can give it a try.
You can try doing a COPY ALL from the timeline in 17 and paste it into 13. You can also try exporting an XML.
From the .bak file you have to delete .bak en than you have the almost latest project file you are able to open.
Could you help me understand what you mean?
delete the extension of the file (.bak)
From the .bak file you have to delete .bak en than you have the almost latest project file you are able to open.
Could you help me understand what you mean?
delete the extension of the file (.bak)
Oh great this worked, how can I ensure this .bak is the exact replica of the final project file that I cant open on 13 anymore? Also how frequently are bak files created when I fiddle with my project?
The bak is an exact copy of the second last save. The veg is the last save. So when you save twice without making any change, bak is veg.
@ceyhun242 a bak file is created every time you save. If you open the project again in 17, save it with a new name so you can tell the difference
You cannot open a project file created in Vegas 17 with Vegas 13. They are not backwards compatible.
Forward compatibily usually works, except for some fx and filters.
The bak is an exact copy of the second last save. The veg is the last save. So when you save twice without making any change, bak is veg.
@ceyhun242 a bak file is created every time you save. If you open the project again in 17, save it with a new name so you can tell the difference
So when I saved the last time this veg as 17 folder accidentally, it created exact replica as.bak file meaning that this bak is definitely the exact copy of my veg which I lost to vegas 17? or it is the second last save and hence and older version of my most recent veg file? If so how can I use the last ve file to be opened on13?
No, when you save a project the first time only a veg is saved, no bak. When you save again (and again) the veg is renamed in bak and a new veg is saved. Means the bak is always a copy of the second last save and not a copy of the last save, which is the veg.
Is there a way to compare bak and veg and see what are the changes made? If not, still how can I get new v17.veg file to be saved as a veg13 so that I can always run it on v13?
This is now going round in circles. Despite suggested workarounds, backwards compatibility has almost never occurred in VP10-17 AFAIK.
The best solution as offered earlier on by @Former user who suggested:
You can try doing a COPY ALL from the timeline in 17 and paste it into 18. You can also try exporting an XML.
Just copy (CTRL-A then CTRL-C) the entire timeline from VP17 and copy (CTRL-V) to a new blank timeline on VP13. FX should follow as long as the same FX are available in both VP17 and 13. The only thing you then need to do is to add any audio and video FX at track or project level.
Copying from Vpro17 timeline to Vpro13 timeline works only correctly when no features are used in Vpro17 that aren't available in Vpro13. Also trackfx/trackmotion and their keyframes are not copied. As mentioned.
But what is wrong with finishing your project in Vpro17 instead of Vpro13?
Quite right .. the same as my comment other than the only thing I missed out on was keyframing.
I tried copying and pasting but it didn't work..
Also, Dexcon said fx should follow but he then said one should as fx at project and track level. but then it means fx actually doesn't follow? Also the keyframing. What are copies not what is not with copy-paste? If copy-paste is a working solution, why vegas just don't allow backward compatibility ? just marketing strategy to force purchase?
@ceyhun242 … Just to clarify: FX applied directly to the events on the timeline (both video and audio) should follow when copy/pasting from one instance of Vegas Pro (the source) to another instance of Vegas Pro as long as that other instance of Vegas Pro has the exact same FX installed as are used in the source Vegas Pro.
A thing to consider here is that Vegas Pro 17 is a MAGIX product whereas Vegas Pro 13 was a Sony product, and the native inbuilt FX have different names. Though I am not sure about this, you may find that a native VP17 FX applied to an event in VP17 won't appear when copied to VP13 because VP13 does not have the exact same FX as in VP17 because the name and coding of the FX is different. If it does appear in the copy to VP13, then that will be a big plus.
When copy/pasting, only the events on the timeline are being transferred - nothing more. Therefore, any FX applied elsewhere such as at track or project level aren't copied simply because those FX are not directly applied to the individual events themselves. Track and Project FX affect events on the timeline, but Track and Project FX are not on the timeline
I tried copying and pasting but it didn't work.
The copy/paste process is the same process as you would use elsewhere on your computer, for example, when copying files, text within a word processor, and so on. In all cases, you need to first highlight what you want to copy, which is what CTRL-A does. If the mouse pointer is on the timeline, all events on the timeline should be highlighted when hitting CTRL-A. Then hit CTRL-C (copy), and toggle over to VP13 (both VP13 and VP17 should be open at the same time), click the mouse pointer on a blank track on VP13's timeline, and then hit CTRL-V (paste). The copy/paste process may take quite a while to complete, especially if it is a large project.
Re backward compatibility, I can only recall one occasion when a project in the latest VP version could be opened in the immediately prior version because there were no major changes to the basic program coding in the new release. I can't recall if it was 12/11, 13/12 or 15/14, but other than that exception, new features in new releases usually means a program coding rewrite which has the consequence of not being recognized in earlier VP versions. Others on the forum are probably in a better position to comment on this point.
Besides, VP13 was released 6 years ago as a Sony product. MAGIX have made substantial changes and improvements with VP14, 15, 16 and 17 since Sony sold VP to MAGIX. To expect backwards compatibility to previous releases issued by a previous owner is a really big and rather unrealistic expectation.