-
Crashes? Try this technique from Sony.
Sony very nicely responded to a recent ‘rant/question’ I posed to them regarding the constant crashing I was experiencing. There was nothing particular about the crashes that afforded me any clues as to why.
Their response, at the chance of stating something that most of you perhaps know anyway, might help some. I must admit my system does seem to be a lot more stable since I tried this (using the latest 64b build).
Sony’s advice –
“Lets have you install the SCS application to a newly created administrator profile. This will require uninstalling the software, creating a new user account, logging off the old user account and logging onto the newly created administrator account, then installing and activating the app on the new administrator account. This allows the software to make the necessary changes needed to the registry. Please consult the Help and Support Center in your Windows operating system for specific directions regarding creating a new user account with full administrator rights.
“Go to Control Panel > Programs and Features and uninstall the SCS software if it is currently installed.
“Now go to My Computer and browse to “C:Program FilesSony Setup” and delete the folders within.
“Next, it’s time to create a new user account with administrative privileges. Go to Control Panel > User Accounts. Select “Add New User” and type in a new name for the new user account. When asked what permissions level to assign to the account, select Administrator.
“Then go to Start menu and choose “Logoff” or just restart the computer to switch users. Be sure to log into the new user account, reinstall the program, and register the application.
“Once the application is up and running you can log back to your normal user account. Now go to Control Panel > User Accounts and remove the test account from your computer.”
-
16 Replies
-
Sorry guys. What was I thinking?! Still getting plenty of seemingly RANDOM crashes. Probably can disregard my previous post. If only it had been that simple!
-
Phil, what graphic card are you using, how much ram does your system have, how many monitors hooked up to that graphic card, and what kind of clips in the workflow? (i.e. lots of fx, multiple camera types, etc.
I have some ideas on Sony’s instability, but need more data samples before feeling my guess is correct.
Al
-
Uninstalling, deleteing folders, different Admin. and all
that stuff wont stop the random crashes….Would love to know
the result of some of that data info Al is gathering,as im trying
to piece together some solutions myself.Steve Rhoden
(Cow Leader)
Film Editor & Compositor.
Filmex Creative Media.
1-876-832-4956 -
There’s been a lot of discussion on running Vegas pro v11 in compatibility mode.
In my case it cured the problems I was having with the New Blue Titler.
I am running Win7-64bit and chose Win7 Service Pack 1 compatibility mode.
Cheers for now,
Tom Pauncz
(30WEST MEDiA GROUP) -
Hi Al
I am running on an Asus P8H67 mobo, 8 gig of Corsair DDR3 with an Asus GTX550Ti video card. And yup, I have two 24″ monitors hooked up to the card. I use Win7 64b and am running the latest build of Vegas 11 Pro.It HAS to be the video card incompatibility doesn’t it? I keep testing, even with single events on the timeline. Last night for instance; one clip, copied to another track with a mask and then a Gaussian blur added to that top track with the mask. Crash!
And again. And again. The clip I used was some stock footage from the internet which was 720×480, 30fps progressive footage. My project settings were 720×576 25fps interlaced.
Sorry for all the details, just trying to be comprehensive for you. Good luck with your theory though! Let me know if there is anything else I can provide you. Maybe others here can detail their tests, using a minimum of events and effects, in order to try and isolate wherein the issues lie. As a said in my initial post I think, when mine crashes it more often than not does so without the option of posting the issues to Sony.
-
To follow up on Tom’s post, here’s the “official” word from Sony.
Stability with third party effects.
Vegas crashes when trying to use certain third party effects.
Running Vegas in Windows compatibility mode may resolve stability issues when using certain third party effects.
Right click on the Vegas launch icon, and select properties, then click the compatibility tab.
Place a check in the box “run this program in compatibilty mode for…”
Then select the Windows version for compatibility from the drop down menu available. Click apply + OK.
We recommend trying compatibility mode for Windows 7 and Windows Vista.
-
Hi Mike… this puzzles me. Why should Vegas be started in compatibility mode for Win 7 when it is installed on a Win7 system… is it written for some weird Venutian Gostak system or something? I wonder if the programmers have been lazy and used non-documented API calls, and of course these can be twiddled with by MS in successive windows updates.
Windows 7 Pro64, 16GB RAM, SSD boot drive, GTX 570 Graphics, Vegas Pro 11 and VP10 just in case
-
Phil, I have no idea why this works but it does.
A user on the Sony Vegas forum discovered it, posted it and now Sony has adopted it as a potential fix for some users. -
Mike!!
You have saved my sanity a couple of times now and this seems to be one of them. Been throwing a few things at Vegas after this little tweak and seems as though nothing fazes it now!
My amazement can be summed up in three words – “Well I never”, ha ha.
Really, thanks. I am still holding my breath though.
-
Phil, thanks for the update. You might want to try running on one monitor as an experiment for a few days. As to the discussion on the compatability mode, it’s the first time I’ve heard about running in compatability mode, The program is sold as being compatable with the latest W7 builds. For now, I’ll take compatability mode advice from Sony with a grain of skepticism.
It’s been my experience that New Blue has seemed to me very buggy, but the crashes I’ve experienced were not just NB, to be fair to them. I’ve had these crashes come and go while using Sony’s own plug ins. Less often lately, as I have gone back to using one monitor rather than two. It happens less with one monitor, but still does. I’m pushing a lot of MXF files (meaning 50Mbps so think large) , but I really don’t use much in the way of fx. I’ve not been experiencing problems with multicamera footage, which means that the code doesn’t break in those modules (for me). The crash dumps don’t reveal much of anything except exceptions that appear to be very generic. You would have to know more about the code to know if they matter, as they aren’t usually pointing to a module, but just exceptions. I routinely check my memory useage and I never get close to running anything more than about 6 GBs of total RAM useage.
I have been seeing a lot less crashes since I cut back to one monitor, and stripped out fx. I’ve been running all fx’s in separate timelines, rendering them and then importing them in to the main timeline. That *does* seem to help. Oddly enough, when I had a laptop last fall and into this winter(Samsung, W7, 64 bit, etc. which I’ve since sold due to no longer traveling) I had *no* crashes. I did not install New Blue, nor any other fx other than Sony’s. I pushed the same footage through it, including MOV and crashes were almost, but not totally non existant. They were dramtatically less. So what’s the difference? The OS was the same (Windows 7 Ultimate), the RAM identical, the version of Sony, Vegas, the same, and the same external eSata hard drive with the footage on it. The graphics cards were different, and no NBlue. Not picking specifically here on Nblue, as I bet I would find some issues with other fx providers if I bought their products. Has anyone been experiencing lots of crashes with Boris installed, for example?
I can’t imagine that Sony’s team, if they were looking, couldn’t reproduce these kinds of crashes. Most of us can likely reproduce them by just spending 2 or more hours on our computers, it seems.
But I’ll keep trying to gather some knowledge on this. Like I said, my sample size is too small. I do not suspect Windows 7. I don’t suspect my hard drive (as I don’t buy green drives nor program them to sleep). My machine does not act up at all with anything else I throw at it, so it really seems to be just a Sony problem. The crashes *only* happen within Sony Vegas 11.
Al
Reply to this Discussion! Login or Sign Up