Random Crashes Since Quick Fix and V-Vocal Crashes (SOLVED I think)

Rasure


As tittle suggests, since the quick fix been having lots of random crashes and V-Vocal now crashes every time I use it:-( n

I get this and have done since X1 (original).
I find that if I freeze my synths V-Vocal will work.
Please log a problem report and send CW a minidump file, the more people that log this the better our chances of getting something done about it.

Report your crashes with a Dump File and your system info file.. I find calling and reporting to a tech is alot better than just sending the file over. And then call back to find out if they figured away around the crashing your having.  Im sure they will do everything they can when you actually speak to someone. 
 Good Luck ...

Rasure


SOLVED: (I think) Just an update on this, I was working in X1 for a good 12 hours ( with a couple of PC reboots throughout the day) yesterday and not one crash, why? well I think the problem may have been Internet Explorer 9. I have since rolled back to 8 and all seems stable again, even v-vocal running as it should, not sure why IE 9 would cause this, main thing is it seems to have solve the problem for me anyway:-)

I doubt it - I am getting the same V-vocal crashes and IE9 is not on my computer.

I think it is something to do with large RAM hungry projects and 32bit VSTis - the project I suffer most in is taking around 6Gb of RAM.
In a smaller project using around 2 Gb RAM V-Vocal works even with the 32bit plugs that in the larger project need to be frozen to get V-Vocal working.....perhaps it's V-Vocal's handling of higher memory addresses that's the issue?

Rasure


Got this back from Cakewalk RE V-Vocal crashing:

"We believe that the problem you are experiencing is most likely a system specific problem or a configuration issue that can be resolved with assistance from Cakewalk Technical Support"

But since removing IE9 it doesn't happen any more, was fine in X1b too before quick fix.  So its fixed for me this time by unistalling IE9, although I only unistalled IE9 because I couldn't turn off the Clear type function like in IE. At the end of the day though users shouldn't have to be removing programs to get X1 to work correctly, never had these issues in 8.5.3

 
HOW CAN Internet Explorer have any kind of impact or influences over SONAR X1?????
Internet Explorer is a program...webreader...should have nothing to do with SONAR...
By the way, IE9 have recently been update last week to a total new version...
 
 
Best Regards
Freddie

Well - it is not that strange. I can remember Protools 8 was hanging at startup and even crashing when IE 8 was installed. The "fix" was to roll-back to IE 7 to get everything working again. In short - Protools was completely unusable when the auto-update to IE 8 took place. Don't ask me why. I only know the "engine" of IE is tightly integrated into Windows (you cannot remove it - uninstalling does only a "surface" removing) and has a lot of undocumented side effects and dependencies.

Glad you found the answer however.

JClosed


Well - it is not that strange. I can remember Protools 8 was hanging at startup and even crashing when IE 8 was installed. The "fix" was to roll-back to IE 7 to get everything working again. In short - Protools was completely unusable when the auto-update to IE 8 took place. Don't ask me why. I only know the "engine" of IE is tightly integrated into Windows (you cannot remove it - uninstalling does only a "surface" removing) and has a lot of undocumented side effects and dependencies.

Glad you found the answer however.

I'm not surprise we talking Pro Tools..stoneage program. It doesn't even work correctly on Windows 7- Its made for Windows 98...

I'm just happy that Sonar isn't crashing randomly now, spent two days at about 12 hours a time working in X1 with no glitches or crashes:-)

Just a side note regrading v-vocal crashes and what twigmans said, v-vocal is crashing because of memory issues, I noted a few days ago that when you have lots of soft synths loaded up then v-vocal crashes, but freeze a few to free up memory and it works fine:-)

Mod Bod

Rasure


Just a side note regrading v-vocal crashes and what twigmans said, v-vocal is crashing because of memory issues, I noted a few days ago that when you have lots of soft synths loaded up then v-vocal crashes, but freeze a few to free up memory and it works fine:-)

SONAR has always crashed for me if memory runs low.  I used to run into it loading very large sample sets in Superior Drummer 2.  I've since gone 64 bit with more memory and that particular problem is a thing of the past.

I have 8Gb RAm in my 64bit machine and start needing to freeze synths to operate V-Vocal when the project reaches around 4Gb RAM.......I have a project right now where task manager reports RAM used @ 6.97Gb and I have no chance of running V-Vocal...now I wouldn't call that running low on memory as there's still a whole Gb available but I suggest that there is a problem with V-Vocal and higher addresses like those fixes for all the synths that CW claimed had similar problems.

soundtweaker


I'm on IE9 and no Sonar X1b crashes here. Just sayin.

+1

I have issues with V-vocal crashing occasionally when I am using X1 64 bit. It only occurs when initially creating the V-vocal piece. It seems rock solid in 32 bit. It doesn't happen all the time. One tip: I found out, quite by accident, that there is a relationship between the crashes I observe and use of track folders. When the track is in a track folder, there is much greater chance of a crash. So what i do is move any v-vocal tracks out of a track folder, create the v-vocal, and if desired, move it back into the folder. The other work around is to pull teh project into X1 32, create the v-vocal click, save and exit out. Then load it n sonar x1 64. Oh yes, frequent saves are a must and setting X1 to allow version saving. I have tested this enough times to be absolutely sure of the relationship between having the track in a track folder when I create the v-vocal and the crash. I am on Win 7 Ultimate 16 Gig Ram. I wish they would fix these annoyances in v-vocal (64 bit). When I get the "white screen", and especially when I loose work, its a huge downer. Rick

flameout


I have issues with V-vocal crashing occasionally when I am using X1 64 bit. It only occurs when initially creating the V-vocal piece. It seems rock solid in 32 bit. It doesn't happen all the time. One tip: I found out, quite by accident, that there is a relationship between the crashes I observe and use of track folders. When the track is in a track folder, there is much greater chance of a crash. So what i do is move any v-vocal tracks out of a track folder, create the v-vocal, and if desired, move it back into the folder. The other work around is to pull teh project into X1 32, create the v-vocal click, save and exit out. Then load it n sonar x1 64. Oh yes, frequent saves are a must and setting X1 to allow version saving. I have tested this enough times to be absolutely sure of the relationship between having the track in a track folder when I create the v-vocal and the crash. I am on Win 7 Ultimate 16 Gig Ram. I wish they would fix these annoyances in v-vocal (64 bit). When I get the "white screen", and especially when I loose work, its a huge downer. Rick

Have you reported this? could help fixing it.

  Try finding your AUD.ini file which is usually in your 'User/cakewalk' file... Change its name to MUD.ini. Sonar will no longer recognise the file and will create a new AUD file when you start Sonar the next time. Dont ask me why this works but I have had problems with VV crashing forever and I was at the point of changing my DAW because of it.. I discovered a thread on a forum (may have been this site!) advising the above solution... It worked.. I have tested VV by using multiple instances in one project and doing everything that would normally cause it to crash but it seems to be fine now... Frustrating as it only took 5 mins to fix it in the end!! Hope this helps Jonesey!