I finally got Vegas 13 trial to open after uninstalling Prodad Mercalli 2.0.

My computer is running Windows 8.1.

Pleased it worked for you Robert. Uninstalling Prodad Mercalli 2.0. made no difference here. Seems like it's a crap shoot as to what the solution is and so far I have found none.

and, a week later, no reply from scs...

Glad to know it helped somebody.

Watching Vegas startup 'progress bar' gives a clue as to where the problem might be.
My app was crashing at the very first stage when importing file format I/O modules.

After noting that it was a simple process of elimination - first removing all file format I/O modules and adding them back until I found the offender on my system.

While not a proper fix, it did allow me to start up and get to work.

On a positive note :

Once actually able to do the work I am pleased to say I've had not a single crash working all day (11 hours) doing extensive editing of two different multicamera projects involving 4 streams of mixed-format Full HD .MTS and .MOV files with a few video plugins.

That was almost never the case with VP12.
I'm happy, even if it means I can't work with .AVI files for a bit.
I will use VP12 for those until a proper fix is here.

My system is i7 SandyBridge, 16g RAM, GTX 580, Samsung 840 Pro SSDs, Win 8.1

John,

I had the same startup issue on Vegas 13 without renaming the Cineform dll. While leaving the Cineform dll disabled, I tried GoPro Studio Premium and HDLink. Both applications still worked. I was able to transcode videos to Cineform. I then tried Cineform playback and rendering in Vegas 13 and it worked. While this may not work on all computers, it is worth a try.

My system is running Windows 8.1

While leaving the Cineform dll disabled, I tried GoPro Studio Premium and HDLink. Both applications still worked. I was able to transcode videos to Cineform. I then tried Cineform playback and rendering in Vegas 13 and it worked.

AFAIK, as of Vegas 10 and later, Vegas uses the Cineform SDK to access Cineform. So a faulty CFHD, Video for Windows, file in SYSTEM32 may cause a problem during startup when Vegas initializes and enumerates the VfW subsystem, you should still be able to decode and encode Cineform AVI files.

This could explain why having the DLL disabled still let you use Cineform in Vegas.

The reason applications would use the Cineform SDK is to bypass Video for Window limitations. VfW was depreciated in 1995. Vfw is limited to 8-bit and Cineform can support more than this.

Uninstalling NewBlue Titler 2 fixed my problem!

Same problem here....
Crashes on the "Creating windows" bit.
I've removed all Vstplugins, renamed the File I/O folder, uninstalled the included NewBlue essentials, installed the K-Lite mega pack of codecs. I don't have a go-pro, Camstudio or Titler Pro. Followed all the helpful advice on this thread to no avail.

I am perplexed. Vegas 12 runs fine.
Windows 8.1
Nvidia GTX660TI - latest drivers

Just to add that I've now tried the 310 build and I get the same issue in the same place.

installed the K-Lite mega pack of codecs.

robinv, get rid of that codec pack. Browse these forums and you'll find several posts strongly recommending that you never install it as it is known to severely mess up Vegas.

Mike

Hi robinv,
If you get the crash again, could you please send us an error report with my name "Chris Dolan" and your handle "robinv" in the message? Then I can search for it in the database and maybe figure out what's causing it. I've been working with other users on the JRiver Media Center crash since yesterday morning, and that seems to be crashing in the same place as yours, circumstantially.

@ChrisDolan(SCS)...

Chris, since you are very visible here (totally appreciated) and are discussing crashes at startup, I would really appreciate you taking a look at a now-closed ticket - 130217-000019 - and read from 02/26/2013.

That reported issue has never been resolved and with the VP13/301 trial installed behaves exactly the same way.

I'd love to take this on again, off-line preferably.

Thanks for your attention.
Tom

Still can't get SVP13 to start...initialises ok and runs through all the plugins, but crashes at 'GPU acceleration...' which is the last to load.

I guess I just wasted $300 - but having the GTX 780 might be the problem?

Great to know if anyone got round this...like can the GPU acceleration tests be stopped on startup and not use, or try to initialise the CUDA from the Nvidea GTX 780?

Big thanks if anyone can help...

Matt

Matt,
We got Tom Pauncz's system working (he had leftover files from Production Assistant 1.0 still installed), so maybe we can solve yours too. The next time Vegas crashes, can you send a crash report with my name "Chris Dolan" and your userID "Maffin159" in the message field?

Crashing at "GPU acceleration" doesn't always mean it's the GPU that's the problem. If Vegas crashes in the 32-bit helper apps (VST or file read/write) then GPU is usually the first place we notice because that's where Vegas syncs it's GPU log file with the ErrorReportLauncher.exe.

Well slap my thigh and call me Shirley - that did it!
I have a demo of JRiver Media Center installed - uninstalled it and now she works. So thank you for that indirect prompt :)

I then went back to my Vstplugins which were crashing Vegas when it scanned them before I renamed the folder. This time it skipped on through all of them and only crashed on one - Spark from Arturia. It doesn't do a "send crash report" type crash it just says that it's stopped responding and gives me a "Close" button. So if I rename the spark.dll extension so Vegas ignores it then it's fine, but obviously not ideal. I'm sure there used to be a "do not scan vstplugins on startup" check box in previous versions but I can't find it so i'm stuck with having to rename that plug-in when I want to use it in music software. Does that option still exist?

So other than that i'm up and running.
Many thanks for the help.
Robin

Robin,
Vegas is configurable about which VST folders it scans. Maybe if you put Spark in a VST folder that your other app scans but Vegas will not scan? Just an idea...

I've been emailing back and forth with JRiver for several days, so hopefully we can come up with a solution that will let our software coexist with their ASIO driver.
Chris

Hi Chris,
Turns out the spark plugin was an older version and I was able to update it and now it no longer crashes on the scan.

So i'm all good now - thanks for the help. It's a shame that sending a direct support request in doesn't get a response (i'm still waiting after week) but your forum interaction is very welcome indeed.

All the best
Robin

Mine crashes at "Initializing GPU-accelerated video processing". The thing is, it worked before, and I haven't installed anything since! It's annoying since I spent $300 on this thing

I am almost certain Windows updated your video card driver without you knowing it. Try and see if that is the case and revert back to the driver that worked. Keep in mind that for video drivers the latest is not always the best. You can also use CTRL+SHIFT to reset Vegas to its default settings.

Thanks for the reply. I reverted back my driver until it wouldn't let me and the reset vegas to it's default settings AND deleted all caches, but it still crashes at the same point, is there another solution?

How did you revert to an earlier driver? Don't use the Rollback function! Uninstall the driver completely, use driver sweeper or something similar and install the new driver. BTW, what kind of graphic card do you have in your system? Would you mind filling in your system specs and make them visible to the forum?

Oops! I used the rollback function! (I updated it again soon after, though). I have Intel HD graphics card in my computer, 8 gB RAM, 500 gB Hard drive space and an Intel Pentium 2.70GHz processor.