Strange Issue with 64 Bit Vegas

bigrock wrote on 6/6/2012, 12:45 AM

I upgrade my boot drive to a Corsair SSD tonight. Every thing went and the machine boots super fast now. But I am having a very weird issue with 64 bit Vegas. It will not run. I unstalled it and reinstalled it and still the same thing. No response is produced at all. 32 bit Vegas 11.0 works just fine. Other 64 bit progams are fine as well.

Any ideas as to what would cause this problem?

Comments

bigrock wrote on 6/6/2012, 12:53 AM

Also seems to affect 64 bit Vegas ver 10 but again the 32 bit one works fine. Tried many 64 bits programs all seem to functioning just fine.

bigrock wrote on 6/6/2012, 1:22 AM

No logs in the event viewer to provide any insight into the issue.

bigrock wrote on 6/7/2012, 12:12 AM

Any ideas - not getting anywhere solving this problem.

Grazie wrote on 6/7/2012, 12:32 AM

I just read your system specs. Is that the system you're attempting to run BegasPro 64bit?

G

ushere wrote on 6/7/2012, 6:12 AM

perhaps he hasn't changed pc since 2006?

;-)

rmack350 wrote on 6/7/2012, 8:59 AM

I'm feeling foggy on this, but Vegas needs a few other things like a C++ redistributable. You've probably got all that but I wonder if some prerequisite needs to be reinstalled.

Rob

bigrock wrote on 6/8/2012, 1:01 PM

It seems odd because it was straight clone of the boot drive to the SSD. And everything else has had no issue. I suspect it was this way prior to the move to the SSD, and I didn't notice it. I do most of my work on high powered laptop.

bigrock wrote on 6/18/2012, 12:25 AM

Continuing to work on the problem not making much progress. The problem affects 64 Vegas Version 10 and 11 but not Version 9. 32 bit versions run fine as well. Process Explorer shows the process starts and then craps out. I don't see any error messages in the Windows logger. No indication in the Sony Logging of the issue. I have uninstalled and reinstalled 6 ways to Sunday - no luck.

ushere wrote on 6/18/2012, 1:37 AM

did you clean install windows to the ssd?

bigrock wrote on 6/18/2012, 2:19 AM

No, cloned over from hard disk.

bigrock wrote on 6/18/2012, 2:20 AM

Monitoring the Vegas process I can see it writes no error messages to the Sony Error Log. There is always a Process Exit .01 of a second after it starts.

videoITguy wrote on 6/18/2012, 5:26 PM

To bigrock:
Don't get me wrong- I don't work with SSD drives, never saw a need, and therefore I am not the expert. One of the things that I do actually is that I try to remain on the curve by studying the research and comments of the industry.

It has been clear from what I have heard of 'best practice" - you don't clone a windows OS boot drive to SSD without HIGH RISK that you will run into these kind of anomalies. I emphasize RISK - because some anecdotal cases get away with it.

Best Practice: Install SSD boot drives as new virgin installs...only clone data drives.

bigrock wrote on 6/23/2012, 10:40 PM

I disagree 100%, being do IT for 30+ years. It's an old wives tale. Now if change to a motherboad with a different chipset than yes it might be neccesary.

The SSD cut boot time by 95%. The SSD is not issue. I put all the Vegas Sw over on the some old hard disk - no difference.

ushere wrote on 6/23/2012, 11:26 PM

i did the same thing first, ie. simply cloned from back-up. had odd problems here and there but nothing dramatic, HOWEVER i noticed that the ssd speed though fast wasn't anywhere near advertised (if one is ever to believe advertised speeds for ANYTHING!).

cs6 came along and my 60gb was going to be too small, so went to 120gb WITH a clean install.

out of curiosity threw back the 60gb and cloned from the 120gb install. not only did the speed almost reach advertised (and greatly exceed that which i'd been getting originally), ALL my little niggles were cured.

all that i read (and i read an awful lot) said to clean install if going from hd to ssd.....

bigrock wrote on 6/24/2012, 3:56 PM

I put a high end Cosair 256GB in, the speed is amazing. Not having any other issues however. I think the issue was there before that change. The process is simply shutting down during it's initial startup for some reason. I am tracing the process trying to fiqure what it is. I might send the process trace into Support to see if they can come up with anything.