V453 crashes on opening project

Mindmatter wrote on 6/16/2015, 1:34 AM

Hi all,

in a slight panic mode.
The project I've been preparing and working on for weeeks crashed Vegas upon loading today. I have saved 3 identical versions before exiting yesterday, closing vegas while all was totally fine. All 3 crash , one on about 50% , one on 55% and one on 95% loaded.
I uninstalled V 453 and reverted to build 444, same problem! all 3 versions crash.

The project has 7 hours of preedited footage, ready for the final editing. I tried rebooting etc etc, no chance.Uninstalled newblue titler 4 ukltimate. uninstalled vegasaur. Restarted, reinstalled vegas 444, then 453. No improvement. ALL the saved versions, even the .bak files saved minutes before the final save, crash Vegas at 50 %, where it stops responding.
I did a search here and followed the advice on this thread:
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=912878
As i had a couple of clips using new blue colorfast on them, I thought that might be a possible issue, or that the install of titler pro 4 had messed with some newblue plugins., Installed v12, loaded the same project, same thing: stops responding at exactly 50%. So I uninstalled and reinstalled new blue colorfast and tried v13 again - same problem.
This is seriously annoying, to put it mildly.
I had updated to 453 a couple of days ago, but continued to work on the project without a glitch. MaybeI should not have updated in the middle of a project... but something is very wrong here. The prospect of having lost like 20 hours of work is not appealing. I'm pretty clueless as to what to do next. What could possibly be the issue?

Thanks for any help!

Comments

ushere wrote on 6/16/2015, 3:05 AM

do you have an image you can restore and try opening the veg's in that?

MarcinB wrote on 6/16/2015, 3:25 AM

"crash Vegas at 50 %, where it stops responding."

Is it a crash (Vegas exists) or projects loading stops at 50% and the Vegas is not responding to any action?

If it stops loading and not responding, you might be affected by the Nvidia driver issue (if you use Nvidia card), reported already on Movie Studio forum.
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=925640

Marcin

Mindmatter wrote on 6/16/2015, 3:46 AM

Hi and thanks for the suggestions so far. Here's an update to the situation:

The non working .veg fiile had more or less 7 and a half hours on the timeline before I last saved it. It is obviously too much for V13 to handle.
I tried several things, one of which was to rename the folder with the footage to force v13 to ask for a location and to try and load the project without any files at all.
After asking for a file location and "ignore missing files" command, it jump- loaded to 100% and crashed.
I now found a .bak file that had saved with 6 hours on the timeline - and guess what - it opened fine, but only after about 3 breath-holding seconds of " not responding".
My guess is that v13 just cannot handle a larger number of files once they exceed a certain limit.. I will now try letting V13 "not respond" on the original project to see if maybe it will eventually come back from the dead after 30 or so minutes.
At least the whole project isn't lost.

LATEST UPDATE ( SOLVED..well kinda ):

Project loaded after about 10 minutes of waiting out the " not responding" V13.
Happy, relieved...but wondering what is going on here...?

set wrote on 6/16/2015, 5:45 AM

Under Project Media Tab, look for 'Lightning' icon (that's the first icon) to remove any unused media from project, just in case you have imported media but decided not to used. That can help.

While opening project but seems 'not responding', try wait a bit longer.

What media format (or from which camera) do you work in this project? 'Not Vegas friendly'-type source media is one possibility too.

If possible, render any finished part of your project to any intermediate working format. (in case anything goes wrong, you can keep continue from here)

Hope everything goes well until finished.

Set

Mindmatter wrote on 6/16/2015, 6:08 AM

Thanks Set!
The project is made with Sony mp4 files from a Sony PMW 320, so it should not be much of a problem for Vegas.
Actually, all has ended well. After a 3 hour odyssey, I finally got the project loaded by waiting the " not responding" period out. I then split it in 2 parts, deleting the respective unused media bins, ending up with two 3-hour timelines. Both "half" projects now load well and fast.
I had exported each separate shooting day already preedited in a low Q render to give it to the producer, but it would still have been a mess to have to crawl through the unedited rushes again.
I don't know if this behaviour of V13 in context with its problems handling large amounts of video qualifies as a bug, but there sure is something wrong here.
Has anyone else been dealing with this issue before? Is there a recommendation from Sony as to a file limit that V13 can handle?

ushere wrote on 6/16/2015, 7:23 AM

from an old issue - try turning thumbnail view off in project media.

OldSmoke wrote on 6/16/2015, 7:50 AM

Did you see if Vegas was rebuilding the peaks? That can take a long time and make it look like it is not responding and even Windows will say the program is not responding. I have that issue if I move a large project without bring the peak files along.

Mindmatter wrote on 6/16/2015, 8:03 AM

Oldsmoke - no this was different. I've had the peak problem before, but in this case, V13 just stopped responding at 50% load. It takes 10 minutes in that state to finish loading. Problem solved by reducing file load in the project, limiting it to 3 hours on the timeline.
That being said, V13 still rebuilds peaks for no reason from time to time.

Ushere - thanks I'll give that a try!