Error, please help.

Downunder wrote on 9/29/2013, 2:39 AM

Hello
All of a sudden I am unable to open a couple of .veg files one hangs a 23% and another at 8% and that is where they stay. I have tried opening different back up .veg of the same but still the same issues. Here is the error info
Problem Description
Application Name: Vegas Pro
Application Version: Version 12.0 (Build 714) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Windows\SYSTEM32\ntdll.dll
Fault Address: 0x0000000077372FC6
Fault Offset: 0x0000000000052FC6

Extra Information
File: C:\Users\VIDEO_1\AppData\Local\Sony\Vegas Pro\12.0\dx_video_grovel_x64.log
File: C:\Users\VIDEO_1\AppData\Local\Sony\Vegas Pro\12.0\svfx_video_grovel_x64.log
File: C:\Users\VIDEO_1\AppData\Local\Sony\Vegas Pro\12.0\ocio_x64.log
File: C:\Users\VIDEO_1\AppData\Local\Sony\Vegas Pro\12.0\dx_grovel_x64.log
File: C:\Users\VIDEO_1\AppData\Local\Sony\Vegas Pro\12.0\gpu_video_x64.log
File: V:\Frontier Presentation Video 2012\Frontier Presentation Multimedia Video March 2013NEW VERSION.veg

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 12.0\vegas120.exe
Process Version: Version 12.0 (Build 714) 64-bit
Process Description: Vegas Pro
Process Image Date: 2013-09-10 (Tue Sep 10) 02:12:10

Further to this in Task Manager it says that Vegas is running (23%), and I can only close Vegas via the Task Manager too

Thanks
Lee

Comments

Grazie wrote on 9/29/2013, 3:12 AM

I notice that this is a new version of an existing VEG? Yes? Maybe you've got a plugin in the older veg that is corrupting this attempt by Build714 to open. Are you able to reopen that older one, in the previous build?

Without a doubt there has been some interesting revelations by SCS that there were some M$ tips/corrections pointing at VSTs - would yah know it!

"I fixed several 64-bit crash bugs in 670 and 714 so if your bad experience comes from an earlier build, you might consider trying again.

Chris Dolan (SCS)

I'm sure there will be a way out of this.

Cheers

Grazie

Downunder wrote on 9/29/2013, 5:21 AM

Thanks G (do you ever sleep?) I gonna have to go back to an earlier version of 12 and see what happens. I have a feeling it is something to do with audio...

Downunder wrote on 9/29/2013, 7:14 AM

Now I think that 714 will not open earlier VP12 build vegies. Anyone have this issue?

dxdy wrote on 9/29/2013, 7:21 AM

Opening earlier veg's here just fine

Grazie wrote on 9/29/2013, 7:28 AM

Me too. It's the comment about VSTs, potentially what plugs, that could be at issue.

G

Dexcon wrote on 9/29/2013, 8:56 AM

I've had this problem occasionally for some time with VP12. What I have found to often be successful is to delete all the .sfk files from the folders on the hard drive and then reselect the veg file after reopening VP12. Mostly, this has proven successful though it then takes quite a while for VP12 to rebuild the .sfk files given that there can be around 2,500 of them on a 1.5 hours project.
Recently, this hasn't always worked on one particular project. However, what I found did work was to first open a veg file created on a current/recent version of VP12, and then to load the problematic veg file. The problem project then loaded successfully - strange but true,
The cause of the problem does seem to be plug-in problem. In my case, I seemed to have caused a clash by using NB ColorFast on a specific shot or shots when Color Corrector and/or Color Corrector (Secondary) was set as a global setting for that timeline track. Somewhat confirming this is that those shots also failed to render properly (horizontal lines throughout the shot).
Early this year, I even resorted to opening Windows 7 in safety mode and then opening VP12 in order to copy the timeline from VP12 to another VP12 page. Basically, it was a case of trying anything to get the project to open.
I hope that this may help you.

Downunder wrote on 9/29/2013, 4:08 PM

Thank you Dexcon for your very useful help, most appreciated.
L