.VEG file is corrupt?

jim-schuler wrote on 9/23/2024, 7:06 AM

I saved and closed down Vegas Pro 18 last night with the intention of rendering this morning.

I go to open my project and it's completely unusable. The .bak files are bad too. Nothing has been moved/deleted/changed. I merely stopped work for the night.

 

Are there any steps to fix something like this? Not looking forward to re-assembling everything.

Comments

Dexcon wrote on 9/23/2024, 7:43 AM

If you have 'Advanced Saves' (in the Tools menu) enabled in Vegas Pro 18, go to the Windows folder where those 'saves' have been saved to and use the last save to open the project. Otherwise, hopefully you regularly copy Vegas Pro project files (.veg) to something like a backup HDD/USB memory card/Cloud as a free or low cost insurance policy to avoid the worst aspects of failures such as a corrupt .veg file or an HDD/SSD failure.

Also, when saving a backup it's a good idea to rename project files so as to keep earlier saves; for example, xxxx1.veg, xxxx2.veg, xxxx3.veg and so on. Vegas Pro 22 has an incremental save option.

Last changed by Dexcon on 9/23/2024, 7:53 AM, changed a total of 1 times.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 20, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

jetdv wrote on 9/23/2024, 8:22 AM

Does it tell you anything when opening?

What if you move all the media to a different folder and then try opening it? Perhaps the issue is a piece of media instead.

You could post the VEG file here and we could see if it can be opened (without the media) to help determine if it's the VEG file having an issue or something else.

jim-schuler wrote on 9/23/2024, 9:03 AM

@jetdv: I moved the veg file to a new folder and it didn't ask for the media. just loaded the progress bar to about 30% and said "the file is either corrupt or of an unknown format"

@dexcon I will check, standby.

 

jim-schuler wrote on 9/23/2024, 9:05 AM

Yeah I tried the appdata local file and it's giving the same error. So odd, saved just fine last night. Now i'm rebuilding. It's 2.5 hours but only about 25 elements (digitized 8mm I spent about 30 hours converting). So compared to that, it's just putting my project back together--- it's suffer-able

jim-schuler wrote on 9/23/2024, 9:18 AM

Can you move the veg file rather than move all the media? I mean, will it achieve the same goal of pausing the load to look for the resources either way?

jetdv wrote on 9/23/2024, 10:30 AM

@jetdv: I moved the veg file to a new folder and it didn't ask for the media. just loaded the progress bar to about 30% and said "the file is either corrupt or of an unknown format"

You have to move the MEDIA so the VEG file can't find it.