• SONAR
  • Random Crashes Since Quick Fix and V-Vocal Crashes (SOLVED I think) (p.3)
2011/04/16 04:38:55
Freddie H
Rasure


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:-)

Still working? No problems anymore or have the problems come back?
 
 
 
 
Best Regards
Freddie
 
 
 
 
2012/04/29 11:08:55
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
2012/04/29 16:07:07
Bristol_Jonesey
Thanks for the tips Rick. 

They may well provide a workaround for the not-inconsiderable numbers of people still suffering from V-Vocal problems
2012/04/30 07:52:54
drjee
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.
2013/02/19 10:52:56
Guitarist1
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!!
2013/02/19 11:05:09
Guitarist1
  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!
2013/02/19 11:39:53
Bristol_Jonesey
Thanks - but the original post was made in April 2011.

Things have moved on a bit since then, though your solution might help other users out.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account