(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.

If your using more than one instance of V-Vocal, stop.. Use one instance, then bounce to clips or tracks. Then use another instance and bounce to clips or tracks. Maybe that will help with your predicament.
Cj

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.. 

I had some crashes when I first started using VVocal too, and Cj's advice on the subject is spot on.  The other thing you may want to look at is the length of the clips you're applying it to.  In my case, that seemed to be the culprit.  Once I split the clips down to a workable size, and did them one at a time like Cj said, I stopped having crashes.

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.

Good luck nailing down the issue, many are plagued with v-vocal instability.  I have some projects I can use a bunch of instances before it crashes and I have to start mixing/bouncing down..other projects for whatever reason it will crash upon opening the first instance

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

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.

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
 

I never bothered to contact them.

from what I gathered, from various posted experiences.. a full un-install & re-install of sonar and all it's components was CW's solution. and even that didn't help most people with this issue.