Comments

Kimberly wrote on 10/24/2012, 10:08 AM
Grasping at straws, but did you get any Windows or nVidia updates during this time? Any chance you can create a Restore Point today, then roll back to a Restore Point from a few days ago?

If you have nVidia and an update sneaked in, you can to tweak your Program Settings tab in the nVidia Control Panel screen to instruct Vegas 12 to use the High Performance nVidia Processor . . . again just a guess.

: (
john_dennis wrote on 10/24/2012, 10:26 AM
If Windows is still sound, at least you still get a desktop, you might try installing Vegas 12 again.
Gary James wrote on 10/24/2012, 10:31 AM
Two things to try.

(1) Open Windows Task Manager - right click on the menu bar and select "Start Task Manager". Look in the list of running Processes. If you see FileIOSurrogate running, right click on that process and select "End Process" from the popup menu. When it disappears from the list, restart Vegas. It should now start properly.

(2) If the above step didn't work, the next step is drastic but it does fix most problems. Hold down the Shift key when you click on your shortcut to start Vegas. You should see a message asking if you want to reset all Vegas Pro preferences to default. Say YES! This will clear all your startup add-ins and other user preference settings, but it usually works as a last resort for fixing startup issues.
vicmilt wrote on 10/24/2012, 10:55 AM
Neither worked:
1 - did not see FileIOSurrogate running
2 - never got to "reset Vegas preferences"

It starts to run the setup but crashes when it gets to my Nvidia 620 2gb board.
"Initializing GPU-accelerated video processing"
and goes to "VEGAS PRO has stopped working"

Am now going to try and restore computer to earlier date.
Will be back.
_Lenny_ wrote on 10/24/2012, 11:06 AM
Try a complete unistall - try using something like iobit-uninstaller which will scan your hard drive and the registry for program references and give you the choice of whether to delete them or not.

Then try a reinstall.
vicmilt wrote on 10/24/2012, 11:36 AM
Restoring the system to two days ago worked.

Kimberly wrote on 10/24/2012, 12:07 PM
In the Windows Restore it should have given you a list of items affected by the Restore. One of those items is most likely the root cause of your VP 12 not wanting to load. I say "most likely" because we cannot see behind the curtain but we can infer what is happening.

Glad to hear the restore worked : )
vicmilt wrote on 10/24/2012, 12:30 PM
The computer is only two weeks old.
The restore was only two days old.
It did not give me any references - it simply did the restore, and that seems to have worked.
I believe it has something to do with my NVidia 620 2gb card and Vegas.
That's where it was crashing on both v11 and v12.
I had it turned off, but apparently that did not work.
We'll see.
I like the new features but am currently in a state of terror, as I do this for a living - often on deadline.
Nevertheless, I still love Vegas.
Gary James wrote on 10/24/2012, 12:34 PM
Vicmilt, try holding both Shift and Ctrl keys when you start Vegas. You should have seen the dialog box before Vegas displays the splash screen.
Kimberly wrote on 10/24/2012, 12:51 PM
I have had fail on start behavior with VP 12 when my nVidia settings were not set as follows:



In my case, VP 12 dudn't load if nVidia Program Settings are not set as above. Then I can do whatever I want with GPU on/off within Vegas, but if I recall correctly, I must have this setting to load. Not sure if that will help you but it is worth a look.

Regards,

Kimberly
Laurence wrote on 10/24/2012, 1:16 PM
I had the same thing happen with V11. Even an uninstall and reinstall wouldn't fix it. I never did fix it. I just moved on to V12.
vicmilt wrote on 10/24/2012, 3:24 PM
Still WAY TOO SOON to judge, but...

I removed my NVidia GT630 board and went back to the built-in stuff in my new

Gateway DX4870-URP10 -
Intel HD Graphics -
i7 3770 -
16gig RAM -
2TB Barracuda HD (no stripe)

At least it loaded - I am 90% certain it's the NVidia board that was the source of many of my sorrows. Yes I definitely uploaded the latest driver.
Now the New Blue titler I was using will not load - and it's bitching that it needs a new video card.

Any suggestions here?

Also does anyone know how to get a HUMAN at NVidia to talk about this?
At the very least they should exchange my board for one that works, etc.

Meanwhile, my computer is Whizzing along - better than with the (wrong?) NV board.
And I'll deliver my spot on time - whew.
Kimberly wrote on 10/24/2012, 3:37 PM
Here is what I found with my nVidia and VP 12.

I went into the nVidia control panel and set Program Settings as shown in the above picture that I posted. That enabled me to launch VP 12. Then in VP 12 I set the GPU to on when I wanted to use NewBlue, and I set GPU to off when I wasn't using NewBlue. For me VP 12 renders much faster with GPU off, but of course that's only if there is no NewBlue.

Some users have posted that VP 12 went from good to bad when they updated to the latest nVidia driver. So don't automatically assume you must update your driver in this case.

jetdv is a NewBlue expert so he may have some good advice for you.

Regards,

Kimberly