Vegas Pro 9 freezes on startup

karmacomposer wrote on 6/21/2009, 8:57 AM
I JUST installed Vegas Pro 9 last night, followed all the directions, and when it starts up, it gets stuck on "initializing ui" - I let it go overnight and it still hung there.

I have read some of the potential fixes and tried most of them (like renameing or removing sony shared folders and rename or remove vstplugins folder, pressing the shift key when starting Vegas up and pressing ENTER without clicking anything - nothing worked).

I REFUSE to uninstall my other sony software (Vegas 8 Pro works great and I DEPEND on it to make a living, so there is no way I am leaving myself for one moment without my NLE) and do not think this would be a cause, since every other sony software I own works without problems.

It should be noted that I have a 64 bit windows - and I installed both the 64 bit and 32 bit - both hang there. I have a multibridge pro and went so far as to turn that off to see if that was causing it, NOPE.

Does anyone have any possible fixes - I really want to use my $185 upgrade and cannot.

Thanks in advance.

Mike

Comments

hoteldelta wrote on 6/21/2009, 1:08 PM
Mike; No idea if this will help or not. My Vegas pro 9 was crashing after startup, I found out this was due to a file - Au_.exe leftover from an install of some other software. Hunted it down, deleted it and Vegas 9 works normally now.
Cheers,
Hal
karmacomposer wrote on 6/21/2009, 1:28 PM
I looked for a file named Au_exe and found one - a prefetch file (.pf) and I deleted it. Vegas 9 Pro still did not startup. Freezes right at the "initializing UI" part.

I have a ATI Radeon HD 3200 on this computer - and it's a quad core, 10ghz, 8GB ram, 3 1TB sata drives and a multibridge pro interface with a pci-express 16 card. Windows Vista Ultimate 64 bit OS. I installed both the 32 bit and 64 bit versions of Vegas 9 Pro.

Vegas Pro 8.0c and 8.1 work perfectly. Only Vegas 9 Pro 32 and 64 bit won't open - all other software I use works 100% on this box.

Mike
karmacomposer wrote on 6/21/2009, 2:25 PM
OK, I installed it on my 32 bit HP Touchsmart (2GB ram, 5TB total hard drive space, dual core AMD, Nvidia GeForce Go 7000 series).

I moved all of my vst instruments to another location (have too many virtual instruments on this computer - I compose on this one) and started up Vegas Pro 9.

It worked! So, on this computer it works. On the other computer, I think it is getting stuck on the XDCAM initializer - because that is what comes up after "initializing ui".

Hmmm, so why would that happen? I don't have an XDCAM compatible camera or deck. I have a Canon XH A1 (plus I have a Panasonic HS100 - and my business partner has two Sony FX1s - all of which get dumped down to the NLE) and a BetaCamSP deck and I always edit via HDV (and now AVCHD).

Anyone have any suggestions or answers? I need to get Vegas Pro 9 working on the NLE. Like I said before, 8.0c and 8.1 work 100%.

Mike
karmacomposer wrote on 6/22/2009, 6:15 AM
Anyone? I really need this to work. I will call Sony Tech Support in a few hours, but till then, does ANYONE have any suggestions as to why this is freezing on me?

Mike
ushere wrote on 6/22/2009, 4:06 PM
i really think you have a vst that's hanging vegas. i had a similar experience. short method change vst folder name so vegas can't see it, long method, add vst's one by one till vegas freezes...

sorry, but that's how i dd it....

leslie
karmacomposer wrote on 6/22/2009, 8:30 PM
Unfortunately, I thought of that right away.

I moved my VstPlugins folder to the desktop and uninstalled all third party DirectX effects and instruments. The result, only the stuff that came with Sony Vegas 9 Pro loaded in - but it did not matter - still froze. I disabled my Multibridge Pro drivers and shut it off - essentially uninstalling it. Did not matter. No USB or Firewire devices are attached. It just freezes reliably - every time, 32 bit or 64 bit.

Tech support gave up on me today and sent me some utility to log what's happening. They just cannot explain what's happening - they just run through their "uninstall everything" playbook - but that did not work.

I am 100% frustrated over this.

Mike