Vegas 17 Can't Find Files!

Film_Digital wrote on 11/6/2019, 6:37 PM

Just got Vegas 17 and tried to load up a couple of old (14) project. Vegas 17 reported "An error occurred opening the media file" for all media files associated with the project even it called out the exact location of the media file it couldn't find. It auto radio buttoned the "Specify a replacement media file" and yes, of course that works, but what the??? BTW, Vegas 16 opens the projects just fine.

Comments

fr0sty wrote on 11/6/2019, 8:25 PM

No idea, but you should only have to tell it where the files are once, save the project (or a copy, since you won't be able to open it in 14 again after saving), and then you won't have to worry about it again.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Film_Digital wrote on 11/7/2019, 12:25 AM

Yes, older versions happily find and load files needed if they are in the same place as the "missing" one. No joy with Vegas 17 on that score either. I've not had to save the project for that to happen but I'm sure going to try it for V17 as it's a pain to point it to where it already is!

fr0sty wrote on 11/7/2019, 2:11 AM

I don't have issues loading projects from 16... if you have older versions to try, maybe open it in, say, 16, resave it in 16, then open that file in 17.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

pierre-k wrote on 11/7/2019, 7:44 AM

if you have mov files in your project, you have to enable preferences - obsolete functions, quicktime support.

fr0sty wrote on 11/7/2019, 9:37 AM

That isn't always true, it depends on the format the mov files are in. I do not have quicktime support enabled, and the mov files from my gh5 and S1's are able to be read by VP17 using so4compoundplug.dll as the decoder. However, that should result in the clip not loading at all, rather than it flagging a location error, especially when projects from other versions of Vegas don't do that.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Film_Digital wrote on 11/7/2019, 3:00 PM

Greatly appreciate the comments. It turns out that @pierre-k method seems to fix the problem (it's called Deprecated Features) which I probably should have caught if I'da been reading V17 changes as there is quite a list in that tab. Just another reason (besides plug-in mess) to keep old Vegas versions around. And guess this is a wakeup call to find a quicktime/.mov replacement codec. Had a nice arrangement with DNxHD in CS6 AE and Vegas.