Project in VP14 cannot be re-opened after any alteration

Ronnie wrote on 8/1/2018, 10:03 AM

Hi,

I’m Ron, I am a video-amateur since 1990 and I’m new to this forum.

So here is some introduction first.

Software:
Vegas Pro since version 8, up to VP 14, build 270. Various plug-in’s from NewBlue, Mercalli stabilizer.

Titler: with VP14 came Vegas Pro Complete, but I removed that a short while ago and reinstalled my NewBlue Titler Pro 2.0.

Hardware:
Pc with Intel i7-2600 (3.40 GHz), 16 GB RAM, NVIDIA GeForce GTX580, software on SSD 840EVO 500 GB NTFS, data on a 2GB Western Digital NTFS. Camcorder: Sony CX900 (HD, so no 4K).

Here’s my problem (as far as I could see there is no existing post that solves my problem).

I’m in the middle of a project that started with 9 hours of (travelling-) footage. I’m narrowing it down to max 30 minutes.

At this time it is still 1 hour. The footage is .m2ts + 1 file in .mov (from Vasco da Gama). On several scenes I added effects like stabilizing, timestretching, cropping, pip’s etc. Project properties are set to match with the footage. Although it is a pretty large and sometimes complex project, no problem so far.

Then I added a larger new .mov routefile in VdG, cut it into pieces and spread them over the timeline. I saved the project with a new serial number as I always do after a few edit-sessions.

Next time the project couldn’t be opened anymore! Re-tried that a couple of times, but every time it stops at 32% of the opening-process with the message that “Vegas Pro doesn’t work anymore”.

I made a restart with the earlier serial number, prerendered scenes with timestretching and other effects, saved it and the same thing happened. I restarted that same earlier version (noticing that the opening process hesitates every time at 32% for many seconds and than opens in a split-second to 100%), removed the non-used files from the Project Media bin, removed a few tracks with spare-material completely (just to make the project “lighter”) saved the project and, again, couldn’t re-open it.

In the end I changed nothing in the project, just gave it a new serialnumber and…after saving it would not open anymore! I also tried all these things again with a re-opened auto-saved version of the project. But nothing works.

Over the last 10 years I made 6 such travelling-movies, each out of a basis of 9-11 hours of footage, all following the same procedure and I never had this problem before.

If I start a new project (which I actually did last month) everything works fine. So probably the problem is strictly project-related.

Anybody ideas???

(sorry for the long story, but I have no idea which info is relevant and wich is not, so I have mentioned everything I could think of).

Comments

Former user wrote on 8/1/2018, 10:50 AM

Normally this is a situation of a non-standard or corrupt file being accessed, or a plug-in that is not compatible or has become corrupted.

diverG wrote on 8/1/2018, 11:31 AM

You are doing the right thing saving to a new name as you progress through your project. It probably is a corrupt file or dodgy plugin. From time to time as you progress through your project I would test open earlier versions just as a precaution. An alternative is to make the project in sections. With the final project comprising a series of .veg files.

Ronnie wrote on 8/1/2018, 1:04 PM

Thanks, david-tu and diverG,

I checked the message from the moment of breakdown again. It says:

An error occured while loading the project file < name> .

The plug-in's specified are not installed on this system.

"Svfx:com.NewBlue.ESDetailEnhancer" (and this is mentioned twice).

Earlier I already checked if these plug-in's were indeed missing, but as far as I could see they are still in place.

But you may very well be right that those files are corrupted.

Tomorrow I'm going to remove and reinstall all my NewBlue plug-in's.

I'll be back with the results!

Thanks so far,

Ron

Ronnie wrote on 8/2/2018, 2:51 PM

Today I removed and reinstalled all my Newblue plug-in's.

That didn't help.

I already tried removing tracks, hoping to find the corrupted part that way, but that resulted again in a project that could not be opened after being saved.

Then I decided (while the latest functional auto.saved version was re-opened) to start an empty project in my second screen and copy track by track from one screen to the other. Doing so one track caused a crash (in the auto.saved project). In that track I finally found (by removing it piece by piece) one corrupted file. As soon as that single file was removed the problem was solved.

I don't understand what is wrong with the corrupted file but I'm glad that I can continue editing my project now.

Thanks again david-tu and diverG, you pointed the way.

Grtz, Ron.

jetdv wrote on 8/3/2018, 4:57 PM

You might try resetting Vegas by holding down CTRL-SHIFT when starting Vegas. Make sure you also check the "Clear cache" box.