V-Vocal still crashes X1B as soon as I invoke it.

V-Vocal still crashes X1B as soon as I invoke it.

As detailed in CWBRN3942

I have another minidump, who wants it?

This thing is unusable.

So 4263 has been closed as it is a duplicate of 3942 with a rather stroppy reply:

Closing report as duplicate. This issue is still on file with our development team and has not been reported as fixed in SONAR X1b. As stated before, if we have additional information regarding this issue we will provide you with information at that time. Unfortunately, at this time we do not have additional information. Please reference CWBRN-3942 regarding this particular issue.

Well i'm sorry - how the hell was I supposed to know it wasn't supposed to have been fixed?
It's been SUBMITTED TO DEVELOPMENT for over a month and X1b claims to have fixed 'many V-Vocal issues'
It should've been fixed
It should never have been released like this in the first place.
I'm not sure I like the dismissive attitude of the problem report feedback.
I need V-Vocal to work for me.

BEATZM1D10T


If it's fixed you get an e-mail stating it was fixed. I got a couple today....

Really?
I never have before.
I've reported stuff that has been subsequently fixed in an update and never had an e-mail to say anything has been fixed.

> Now this is a function I never use. so I opend a song ..
    to a wav track clickd on it, then went to v-vocal, make ..
    clip, clickd on that, box opend,clip popd up, super-cool
    now this is a option i can see getting a lotta use, whats
    going on there , this is not a joke post !!!

That, or DimPro...

Twigman

StarTekh


> Now this is a function I never use. so I opend a song ..
  to a wav track clickd on it, then went to v-vocal, make ..
  clip, clickd on that, box opend,clip popd up, super-cool
  now this is a option i can see getting a lotta use, whats
  going on there , this is not a joke post !!!

Now try it in X1b x64 on W7x64Pro with 9 unfrozen instances of ReFX Nexus in the project

> I am on win7-32 and xp sp3 I will let you work it out

Twigman

trimph1


That, or DimPro...

Are you seeing the same crash with unfrozen DimPro instances?

I was beginning to think it was just me that is having these V-Vocal crashes

I had one...then bugger all for crashes...weird.

StarTekh

Twigman

StarTekh


> Now this is a function I never use. so I opend a song ..
to a wav track clickd on it, then went to v-vocal, make ..
clip, clickd on that, box opend,clip popd up, super-cool
now this is a option i can see getting a lotta use, whats
going on there , this is not a joke post !!!

Now try it in X1b x64 on W7x64Pro with 9 unfrozen instances of ReFX Nexus in the project

> I am on win7-32 and xp sp3 I will let you work it out

you're using 2 operating systems? at the same time?

bitflipper


Anybody check the rev stamp for cronus.dll in X1b? Has it actually been updated?

And the SonitusFXDelay.dll That's supposed to be fixed as well.
 
 

X1b installed.

Vvocal will start, and I can manipulate notes, but when I try and play the song with the new vvocal edit, nothing moves, and there is no sound.

I dunno, maybe I'm not doing something right, but I never get the crashes that people talk about with VV. I'll tell you how I use it if it helps any...and I just did a vocal track right now as I was reading this thread to make sure I tested this out before-hand.

I zoom in tight on my vocal tracks and split the clips where problem areas are. Once I do, I right click on the split clip, click the VV option, it loads up, I adjust the pitch, close the plug, then right click on the clip it edited and I select "bounce to clip".

The only issue I have is, sometimes the muted clip VV does to your original track, sometimes ends up on top of the good one...other times, it's behind the good one. It looks like this.



The V's in yellow show where I did the V Vocal edits. See how the first clip is reading "muted"? If I delete that, there is the corrected VV file behind it. See the others that have the yellow V? If I delete them, (they are the processed VV clips) you'll see the mute thing behind which are the original vocal takes. This mute thing showing up is the only issue I have ever had with VV. I've never got the Cronus thing unless I insert VV as an effects plugin and let it run. Even then, it will hang in there a pretty long time before it crashes. But using the method I have mentioned above, not a single issue. What you see here was just done in X1b while being on the forum...so for me, it's working perfectly. This particular pc is a stock Dell, Realtek HD with asio4all drivers...no bells or whistles. It's just my net pc.

I zoom in tight on my vocal tracks and split the clips where problem areas are. Once I do, I right click on the split clip, click the VV option, it loads up, I adjust the pitch, close the plug, then right click on the clip it edited and I select "bounce to clip".

I suspect by splitting the clip so that VVocal only affects a portion of a lengthy clip is the answer.

I am not a VVocal fan, but I didn't really have many issues with it.  I think it's the same reason:  I always isolated the range that I wanted to affect into it's own clip.

Trying to VVocal long / full length project clips may simply cause memory issues.

A couple of new pieces of info.

Cakewalk customer service gave me a few pointers for stuff I was already doing:  Short VV clips, and making sure the track isnt armed when I created a VV clip.  They also said that using VV on a stereo clip can cause it to crash too.  (really???) 

They also said to make sure that cronus.dll was in the plug in manager, and not excluded.  Mine was actually excluded, so I added it back in.  Same issue.

So they then told me to export my VV clips, remove the VV clips from the project, save, and reopen X1b and the project,  and import the VV again.

For giggles, I didnt import the VV clip.  I simply tried to bounce to clip one track.  Same error... dropout, and the project refuses to play.

I tried this on several projects made with various versions of Sonar, and more than likely even Pro Audio.  All failed the vvocal and bounce to clip tests....  with 2 exceptions:  1) the project I mentioned above which was created completely with X1a, and 2) A small, 2 audio track project I am pretty sure was made with Pro Audio.

Not sure where to go with this... have 2 emails in with customer service now, but perhaps will call them tomorrow night for some phone help.  But so far, not so good on what they are telling me to try.

I can get V-Vocal to work as expected only if I freeze all instances of ReFX Nexus.
If I don't, X1 just crashes.
ReFX nexus is a 32bit VSTi that runs via BitBridge.
It has been confirmed to me by CW that it is indeed V-Vocal that 'causes' (initiates) the crash but from what they've told me I believe they still do not know why.
I suspect this may be a BitBridge related problem perhaps?


I must confess that at the moment I only have projects that have been created in X1A or prior to test with.
I have not started a new project in X1B yet.