This process has worked for others. I WISH the OP would try this approach and report back. But, it appears this thread is more of a rant than a true issue resolution thread. At this point, if we don't hear back from the OP on attempts to use the process workflow, we as a community should petition the CW moderator to close this thread as "Resolved - use the suggested workflow until improvements come out in the next release(s)."

 
I really think you people are weird. You accuse me of ranting but you are the ones that keep filling this thread with comments that are not related to the problem - I am merely answering your silly posts. I think you are enjoying stoking the fire.
 
If you'd take the time to actually read my posts you will see that I agreed that your approach works. But that does not change the fact that v-vocal has a serious bug that you found a work-around for.
 
To suggest the thread gets closed just because I am not 'one of you'  and don't have the same opinions as you is just ridicoulos. If this thread is so annoying why don't you not look at it?
 
As I suggested before - how about nobody posts anything unless it can help to resolve the problem.
www.v-vocal.com
 

how about nobody posts anything unless it can help to resolve the problem.

 
Based on that logic, the thread should probably be closed unless someone here can make a code change and test it.   Otherwise it seems a little unlikely that any SONAR user here can actually resolve the problem.   
 
And even if someone from Cakewalk or Roland chose to chime in, it also seems unlikely that a response to a forum post would result in a VVocal fix any time in the near future...  at least not before the next SONAR release, or more realistically sometime afterwards knowing how development schedules typically work.   In the interim, the workarounds are available to those that need them. 
 
I do think, however, that your idea to test vertically aligned VVocal instances is a very good one.  Now *that* is something that CW/Roland should find highly useful should the tests pan out...  
 

bitflipper

it seems a little unlikely that any SONAR user here can actually resolve the problem

It took 6 pages of nonsense before somebody stated the obvious.

This thread was never anything more than a rant, a way to blow off steam. That's perfectly OK - up until you start insulting people whose replies you don't like.

I don't like the tone of your post BitFlipper or should I say ByteChanger??? It sounds a little off pitch, a little atonal, a bit dissonant.  Perhaps you need to slightly change your frequency here.  But hey what do I know?  Tritone, Triad, it's all the same to me.  Perhaps what I need is to autotune my perceptions, no?

bitflipper

it seems a little unlikely that any SONAR user here can actually resolve the problem

It took 6 pages of nonsense before somebody stated the obvious.

This thread was never anything more than a rant, a way to blow off steam. That's perfectly OK - up until you start insulting people whose replies you don't like.

Maybe you should at the man in the mirror! What have you provided in this discussion? You started out with an insult in your very first post in the thread - but maybe your high standards doesn't apply to platinum members? Not one single one of your posts here are helping towards a solution or info that might help.
 
I started this to get some attention on a problem that I and some others have. Not to waste my time on silly discussions - but I am not gonna just sit back and take the insults, sarcasm and snide & arrogant replies that are spewed here. If you have so much time to spend here you should go back see how this thread became what it is. I am definitely not a diplomat but every single one of my 'less diplomatic' replies have been to stupid forum crud that should not have been here in the first place. Eye for an eye.
 
Does ANYBODY want to help getting more information on the problem as suggested in my previous post.
 
www.v-vocal.com
 

Sijel


Thanks Jamie.
This process has worked for others.  I WISH the OP would try this approach and report back.
But, it appears this thread is more of a rant than a true issue resolution thread.
 
At this point, if we don't hear back from the OP on attempts to use the process workflow, we as a community should petition the CW moderator to close this thread as "Resolved - use the suggested workflow until improvements come out in the next release(s)."
 
Thoughts?
 

until improvements come out in the next release(s)."

 
What makse you think that a fix will come out in the next releases? It has been there since the beginning of V-vocal. Apart from all the noise - this thread was intended to get some attention on the problem so maybe there actually would be a fix. If we all just learn to live with the problems by changing our way of using the SW - the bugs will never be fixed. And no, that is not intended to be an insult. Only by stressing the problem and mapping how and when it happens will the developers be able to get closer....if they are working on it at all that is.
 
Can we just agree that we have two different angles? You like and accept your workaround and I don't (although I am forced to do it to make progress on my projects).
 
www.v-vocal.com
 

v-vocal has a serious bug that you found a work-around for.

No bug here. No workaround required.

I know that's not what you want to hear, but it's the truth, and always has been.

(My latest project runs smoothly and without glitches or errors with over 40 LIVE V-Vocal clips. No bouncing necessary.)

No bug here. No workaround required. I know that's not what you want to hear, but it's the truth, and always has been. (My latest project runs smoothly and without glitches or errors with over 40 LIVE V-Vocal clips. No bouncing necessary.)

Bristol_Jonesey

v-vocal has a serious bug that you found a work-around for.

No bug here. No workaround required.

I know that's not what you want to hear, but it's the truth, and always has been.

(My latest project runs smoothly and without glitches or errors with over 40 LIVE V-Vocal clips. No bouncing necessary.)

Good for you - does not really help the people who sees the problem though.

spanky

glrecordings

Shane_B.


OH MY GOD! I had my first V-vocal crash today with that damn cronus.dll thingy showing up.

Normally I record 96/24 with 64bit precision turned on but this project I'm working on now I have Sonar set up 44.1/24 with 64bit precision turned off just to see if I got any performance improvements. So far today I've gotten 5 cronus.dll crashes.

Who knows ... I give up trying to figure all these Sonar errors out.

I froze the track and set Sonar up to auto save every 2 minutes. Not a problem after that ... but why the heck should I have to go through all that.

Anyhoo ... hope somebody gets a chuckle out of this if they remember my previous post in this thread stating cronus is the one error I've never got in Sonar. I think I've officially experienced every error I've read about on these forums now. I feel so special. :)

Shane

Can you provide some information on how many v-vocal clips and how they are placed in your project. Also what are you doing when the crashes occur?

www.v-vocal.com

I'm pretty sure he was being facetious. His second to last sentence proves it.

Nope, it happened. And it happens repeatedly now. I'm going to reply to glrecordings request for details now.

I love v-vocal and I will remedy this. As I get older my playing is improving and my voice is failing so I need this plug to work! LOL

the price you pay for Melodyne and what you get for it, I would be much more inclined to start a Melodyne flame thread.

 
IOW, the grass always seems greener on the other side
 
For me, standalone vocal tweaking is a non-starter.  V-Vocal works fine with the workprocesses a few of us have posted in this forum.

glrecordings

Shane_B.


OH MY GOD! I had my first V-vocal crash today with that damn cronus.dll thingy showing up.

Normally I record 96/24 with 64bit precision turned on but this project I'm working on now I have Sonar set up 44.1/24 with 64bit precision turned off just to see if I got any performance improvements. So far today I've gotten 5 cronus.dll crashes.

Who knows ... I give up trying to figure all these Sonar errors out.

I froze the track and set Sonar up to auto save every 2 minutes. Not a problem after that ... but why the heck should I have to go through all that.

Anyhoo ... hope somebody gets a chuckle out of this if they remember my previous post in this thread stating cronus is the one error I've never got in Sonar. I think I've officially experienced every error I've read about on these forums now. I feel so special. :)

Shane

Can you provide some information on how many v-vocal clips and how they are placed in your project. Also what are you doing when the crashes occur?
 
www.v-vocal.com
 

Sure, I'd be glad to ...

Please see my signature for my system specs.

It's a small project I'm working with that I just started. I have my project set to 44.1/24 and I have the 64-bit engine turned off. Normally my project settings are 96/24/64bit engine=ON but decided to change to see if I got any performance increase. I didn't see any performance increase other than a smaller project size, actually my reported latency increased by more than double what it is at 96, but I really couldn't tell a difference.

Project Details:

1 Session Drummer 3 session with 3 audio outputs active, so basically 3 Session Drummer tracks.
1 True Piano track.
2 Vocal tracks. The first one is the length of the entire song and the second is two very short clips that I moved to a second track that I had kept form previous takes I had done.

I split the full length track in to 5 clips and used V-vocal on 3 of the clips and I used it on both of the clips on the second vocal track. I routed everything to busses and put the plugs there except for the Sonitus track EQ, which technically is a plug I guess. I have 4 busses, Drums, Piano, Vocals, and Master.

The error doesn't occur at any specific time, it just randomly happens out of the blue. It never happened when I was actually using V-Vocal. It happened when I was adjusting the Sonitus EQ and 64 Tube Leveler. Those are the only plugs I have in the project at this point but I imagine it would occur with whatever plug I was using.

I stopped the error by freezing the tracks with v-vocal on them.

This is the first time I've ever had a cronus.dll crash. Normally I have my project settings at 96/24 and the 64bit engine turned on during the entire recording, mixing, and mastering process so maybe it has something to do with the project settings? The last project I did totaled 24 tracks, 6 of which were vocal tracks. I used V-Vocal on all the vocal tracks (some were split and some were not), a bass, and an acoustic track without bouncing or freezing and didn't have a single problem.

I'm not running any hacked software or anything like that on my system that could be causing problems. All I have on my DAW is Sonar 8.5.3 PE and Izotope's Alloy and Ozone, but I wasn't using them at the time this happened.

Shane

Me also find same problem with V-Vocal and Sonar 8.5.3, I was tried to create a V-Vocal clip and sonar cash. I already tried to connect so many times but there are so many issues are occur and any one say that the problem is not solved yet. I am saying very confidence that this problem still occur.

< Yawn >

I can't stop farting 

Well i was using Reason then FL Studio then it was either Cu Base or Sonar - The Reason i chose Sonar was i got a better reply from the customer service desk -

The only issues i have with Sonar is my lack of understanding the program - i have dabbled in V Voacal but never had any issues as i do a clip at a time - then bounce to audio !

everyday is a school day for me the now but - thats why i got a pro DAW so it challenged me and i get good end results and compared to FL and Reason the end results are sounding better - maybe if i went back to the two - i would get better results as now i know more - but i am happy with my 400quid investment - just need a better PC for numerous plugins! Rave on!

ChefMike888      Shane's shirt is making me dizzy
 
 
I thought it was me;  and my malaria was back.