A fatal error has occurred... (v-vocal crash)

(sonar pe, 64bit, 8.5.3.282)

having some issues with v-vocal.. errors, crashing.. etc..

just when I think that I've figured out what might be causing it, and think I've fixed it.. it happens again.

it may have to do (in part) with certain effects being loaded up in the bins, causing some sort of conflict. I deleted all the older cakewalk fx (classic phaser, para-q, tempo delay.. etc..) and was able to create v-vocal clips again.. from the audio already available in the project.

though.. any new, imported audio gave me errors (direct show error) and crashes (cronus.dll) again, when I'd try to create v-vocal clips from them. the imports were the same as the previously, successfully v-vocal'd clips.

so.. then I deleted the newer cakewalk fx as well (vocal & percussion strips).. still crashed.

then I deleted every single thing in all fx bins (guitar rig 4.. etc..).. and could finally create v-vocal clips again.. no problem.

the inconsistency is really annoying.. sometimes I just delete a few fx and it works.. sometimes I have to delete them all to make it work.. wtf.

anyway.. if anyone has any insight to this problem and can offer any suggestions I'd appreciate it. it seems the fx bins are to blame.. but I'm not totally sure.

all my software is completely up to date btw.

ok. thanks for that suggestion.

I bounced them all to clips, but any attempt to create new ones results in crashes and errors again.. until I clear out a few, or all, the fx bins again (in no particular order).

not sure submitting a bug report would help much, considering I can't seem to find a consistent chain of events that makes this happen, other than just having stuff in the fx bins.

I guess in the future, I should just pre-convert all my vocal snippets to v-vocal clips.. and hope I don't have to import any new ones during the production.

kind of disrupts my creative process.. 

most of the clips are very small (3 to 10 secs). it seems, regardless of the size.. the crash can still occur.

I've also enabled the Cronus plug-in, in the dx section of the plug-in manager. no luck.. still crashes.

the only 'consistent' I can find.. is that having anything, in any of the fx bins, can cause a new v-vocal conversion to hang half way through.. and crash.

of all the 'fixes' I read about, and tried.. this particular 'fix' was never reported. 

I got the idea after reading a unrelated post.. about someone dealing with a corrupted .cwp file. he figured out there was a bad instance of an fx bin plug-in that was corrupting the entire session. after removing the effect, then reapplying it.. it fixed the problem.

so, I thought my session saves had gotten corrupted somewhere down the line.. even though I wasn't really experiencing the same issue of opening any of them like this other guy had.

concluded that wasn't actually the problem I was having.. but thought it was interesting that a similar circumstance might be causing all these v-vocal problems people are having.

if there's anyone out there that has any old sessions with this, v-vocal crashing problem, and can confirm this 'fix' of mine, by deleting all your fx bin plug-ins in that session.. it would be very helpful in trying to nail down this problem.

Me too, but I think it has somthing to do with memory and buffers.  Underneath the v-vocal clip is the original clip and it's muted.  I dont have any more soloutions apart from small clips and one clip at a time then bounce or freeze the track.

Look I have said this before and this does not help really but as human beings we are not perfect so unfortunaltly the things we build and design are not perfect.

On saying that i have used this effect to great use in the last week or two and am happt to put up with the imperfections due to the worth of the tool.

I’m not being conceited or arrogant, I just want to give away the formula for turning lead into gold.
Down with the false Gods. (Audio Schools)
Viva la Revolution
Sonar Forever, Pro Tools Never
Ben B.C.T (Bachelor of Creative Technology)
http://www.myspace.com/audiomystics

progtronic


I'm all for workarounds.. pre-converting all my vocal clips will totally work for me.

it's just that I think I may have stumbled on something that could help cakewalk further investigate what's causing all these v-vocal problems.

just a few people, reproducing these problems, in a similar way.. could help pinpoint whats causing these issues.

it's just that I think I may have stumbled on something that could help cakewalk further investigate what's causing all these v-vocal problems. just a few people, reproducing these problems, in a similar way.. could help pinpoint whats causing these issues.

 
Have you heard from CW Support? If not, you should contact them directly.
 
www.v-vocal.com
 

Well, you are right about that. However, if you don't contact them you just hand them another excuse for not fixing it. You don't see Tech Support getting involved in this particular issue on the forum.

www.v-vocal.com

messeri


I faced a similar problem today. It seems that Cronus.dll somehow causes crash of the whole application.

I decided to live without VVocal and renamed the Cronus.dll to something else, so it is not loaded now when I open the application. It is a pitty, but needed to decide not to use that. After all I can now use my active project again... I am now running low on one of the key features...

The problem became evident when I was editing manually volume levels on a track where I had VVocal used. Then the app suddenly crashed. The error message was:
"A fatal error has occured.
Module: C:\Program Files (x86)\Cakewalk\SharedDXi\VVocal\Cronus.dll
A crash dump file has been created here:
C:\Users\{MYUID}\AppData\Roaming\SONAR X1"

Booting the PC did not help at all.

Common for these cases seems to be that we both have a 64 bit OS.

I posted this as a problem to support. Let's see what happens...

My mini specs:
- Windows 7 64
- SONAR 1a update
- M-AUDIO FastTrack Pro

Any more recent wisdom on this bug?

Over the years I've learnt to use V-Vocal on as short clips as possible -- just a phrase or two at a time -- and bounce to clips say a verse at a time. In other words, I stay in V-Vocal mode for as short a time as possible.

Another technique I've used is to do the vocals processing in a separate project, with only a skeleton or premixed backing track to work against. Then bounce to clips and export the vocal track as audio before importing it back into the main project. It seems to help to keep everything as simple as possible while V-Vocal is up and running.

I really don't like V-Vocal much -- it can create some horrible artifacts if you use it for harmonising -- but I use it "because it's there."

Hi... I fixed my V-Vocal problems!! For ages V-Vocal would cause Sonar to crash although it took me a while to realise that it was VV that was causing it!! I tried everything including a complete reinstall.. Nothing worked!!.. I then came upon a thread which advised to replace the AUD.ini file! Actually, all you need to do is find the AUD file (Usually in your USER/Cakewalk file) Changed the existing AUD file to MUD! I then restarted sonar which forced it to create a brand new AUD.ini file. I have tested the system with various instances of VV now and it seems to be very stable! NO MORE CRASHES!!!

Reading this I just realized I have been using V vocal on a few songs without issue. I only pin point short snippets to correct pitch. But I'll end up with up to 20 of these in a multi harmony part.