Innocent, if stupid, question re .veg's

Film_Digital wrote on 11/8/2018, 6:12 PM

Why can't new versions of Vegas be allowed to open previous version files? Or, why must the format be constantly changing? Adobe does that with AE and have made a major mess; for example, grab an old but useful project, especially one fairly complicated, and, if you have a newer version of AE, you may find yourself having to download and install x versions to get to the version you need.

Comments

Musicvid wrote on 11/8/2018, 6:20 PM

Is this a problem with Vegas or a shill for Adobe?

If your .veg files are not forward compatible, why didn't you post even the names of both Vegas versions?

Troubleshooting steps can be found here: full steps to reproduce in both your Vegas versions would be the very least first steps toward getting any support.

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

EricLNZ wrote on 11/8/2018, 6:51 PM

Why can't new versions of Vegas be allowed to open previous version files?

My understanding is they should, but I don't know to how many versions back it applies. So I'm surprised you are experiencing problems.

As Musicvid has said more info is needed in order to help you. I'd like to know what the versions are, what steps you are taking to open them, and precisely what happens.

Musicvid wrote on 11/8/2018, 7:12 PM

but I don't know to how many versions back it applies. 

At least to Vegas 2, Eric.

OldSmoke wrote on 11/8/2018, 7:15 PM

If the old project includes a plugin that is not in the new version, not installed or not compatible with, than the old veg will either throw an error on opening or just wont open. If the above doesn't apply, than there is no reason why it shouldn't open. I have opened SVP8 file in VP15 without issues. However, you ant open newer versions in older ones unless you a tool like "Version Faker" but even that has it's limitations.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Film_Digital wrote on 11/9/2018, 1:09 PM

Never post late at night; otherwise, you might, in fact, appear stupid! @OldSmoke called it; I got it backwards and really want to know why you can't open newer versions in older ones. @MusicVid Shill for Adobe? Please note the criticism leveled at them for making it so hard to take advantage of old but useful assets. Left them for Vegas and haven't looked back.

EricLNZ wrote on 11/9/2018, 5:05 PM

I wondered if you had it back to front!

The reason is I guess that older versions don't understand parts of a newer versions file because additions/improvements have been created subsequent to the older versions existence. It makes sense to me. Are you saying that Adobe can do this? I thought the problem was common to any software that improves from one version to the next.

Former user wrote on 11/9/2018, 5:10 PM

I don't know of any software that is totally backwards compatible, for the reasons others have stated. New features require additional data that earlier versions are not designed to read or understand. There is some softwware that allows you to create backward compatible files (Photoshop is one that comes to mind).