Transitioning to Vegas happening at the right time for me

Cliff Etzel wrote on 5/31/2017, 12:35 PM

I was finishing up the last project I had been working on in Adobe PPro CS6 the past few days. This morning I went to open the project and PPro throws an error message stating the project file is corrupt!!! Apparently this is a known issue since version CS3! After trying all of the various fixes I could find via google, I was able to import and quickly reassemble the project in the latest Vegas Pro 13 from the last auto saved PPro Project file.

The 800lb Gorilla strikes again... 😡

Comments

ushere wrote on 6/1/2017, 3:21 AM

unfortunately, we live in/on the planet of the apes -(

i haven't ever used an nle that hasn't at some stage or other given me a minor heart attack and i have a bald head to prove it too.

the more they try to cram in the more risk there is of something going awol.

good luck...

set wrote on 6/1/2017, 7:04 AM

Do save and save as. I always do this in Vegas Pro, but I guess you can also do it in PPro CS6.

Cliff Etzel wrote on 6/5/2017, 8:10 PM

I had to revise an edit for the client that was originally done in PPro CS6 - it crashed and corrupted the project file - after 3 hours of editing. And the auto save files were corrupt as well. ARGH! I was able to semi import the corrupt project file into VP13 and rebuild what wasn't there and finish the edit. Needless to say, I'm not happy at all given how many of my projects are edited in PPro CS6.

Vegas Pro is now more than ever my primary NLE...