• SONAR
  • V-Vocal broken in latest Plat 2016.08
2016/09/08 20:21:37
gmp
On 2 different projects I've tried opening V-Vocal on a small 2 bar clip and it froze into an hourglass for a long tie until I finally tried to close Plat by hitting exit. Then I got a Window saying Plat has stopped working and must close.
 
The 1st time it happened Plat would not open again, so I rebooted and opened a different very lean project and tired the same thing with a 2 bar clip - same freeze. Can anyone else please verify this? I have all the Win updates and the latest Plat 2016.08
2016/09/08 21:59:18
noynekker
Hi Gerry . . . I'm running the latest Sonar Platinum as well, I opened a project from 2013 that had many V-Vocal clips and they open and play as expected, then I opened an older project from 2007, it also works properly, region editor opens the V-Vocal editor window and it all seems to work.
 
HOWEVER, If I try to create a new V-Vocal clip it does throw an application error message (taskhostw.exe - Application Error) the error references that is a memory related error. It also says to click OK to close the program, but when I click OK . . . the V-Vocal clip is created, and Sonar does not close or restart, and appears to work normally. The new V-Vocal clip appears to work fine. Granted, my system is different than yours (especially you're still 32 bit), so I can't confirm they've actually broken V-Vocal in 2016.08 version . . . but it is breaking down, perhaps suffering from old age, it's just a matter of time.
 
Also, I should add that I never noticed a problem since I don't use V-Vocal anymore, and haven't for a few years, since I've been using Melodyne, so not sure if it's just the most recent Sonar version that does this or not ?
2016/09/08 22:19:21
gmp
Actually I'm using 64-bit now. I rarely have to go back to a 32 bit project. I'm certainly not anyway near low memory and I've not had this problem with any other version of Plat.
2016/09/08 22:48:37
noynekker
Gerry, (please update your system specs) I do recall a problem I used to have with V-Vocal when there were slightly overlapping clips, and also if ever tried to cut and paste V-Vocal clips there was eventually some problem until I just froze or bounced the track . . . not saying this is your problem, but I hope it can be helpful as something to quickly check ?
A while back I noticed that V-Vocal automatically started to open in my multi-dock for editing . . . It used to open in it's own separate floating editing window, have you noticed that in your set up as well ? Perhaps there something there.
While I don't think we can expect V-Vocal to just keep working as Windows OS keeps updating with preference towards the latest hardware available . . . I've always found Cakewalk's backwards compatibility to be amazing, probably best in the DAW worlds, so there may just be a configuration setting (or soundcard) to adjust somewhere to remedy this.
2016/09/08 23:57:52
gmp
noynekker
Gerry, (please update your system specs) I do recall a problem I used to have with V-Vocal when there were slightly overlapping clips, and also if ever tried to cut and paste V-Vocal clips there was eventually some problem until I just froze or bounced the track . . . not saying this is your problem, but I hope it can be helpful as something to quickly check ?
A while back I noticed that V-Vocal automatically started to open in my multi-dock for editing . . . It used to open in it's own separate floating editing window, have you noticed that in your set up as well ? Perhaps there something there.
While I don't think we can expect V-Vocal to just keep working as Windows OS keeps updating with preference towards the latest hardware available . . . I've always found Cakewalk's backwards compatibility to be amazing, probably best in the DAW worlds, so there may just be a configuration setting (or soundcard) to adjust somewhere to remedy this.





I've updated my specs in my signature to reflect 64 bit Platinum, although it still shows 32 bit. Maybe I need to log out and back in. I assume that's what you meant about updating my system specs. In my 2nd test today with V-vocal as I freshly rebooted. I opened a project with 3 audio tracks. The lead vocal is one long clip, so I split it, into a 2 bar clip and opened V-vocal, the fact that it froze in this situation indicates a pretty serious problem on such a basic song file.
 
 This is a year old Jim Roseberry fast computer, Win 10, all updates current. I've used V-vocal for more than 10 years and have always tuned only small 1 or 2 bar clips and immediately choose "bounce to clip". Since V-vocal sometimes can be squirrelly, like you said, This method has made V-vocal very stable and predictable until today.
 
For me, V-vocal is opening in the multi-dock for editing, not a separate window. It seems I made it that way in my template, so it never opens in a free window anymore. Although when I tried to open it today, when it froze I could see the clip with the V-vocal name in it, but it didn't appear in the multi-dock, it just froze with the hourglass. So is V-vocal working ok for you? Are you using the most current Plat 2016.08? Every other version of Plat worked fine.
2016/09/09 00:45:33
noynekker
gmp
noynekker
Gerry, (please update your system specs) I do recall a problem I used to have with V-Vocal when there were slightly overlapping clips, and also if ever tried to cut and paste V-Vocal clips there was eventually some problem until I just froze or bounced the track . . . not saying this is your problem, but I hope it can be helpful as something to quickly check ?
A while back I noticed that V-Vocal automatically started to open in my multi-dock for editing . . . It used to open in it's own separate floating editing window, have you noticed that in your set up as well ? Perhaps there something there.
While I don't think we can expect V-Vocal to just keep working as Windows OS keeps updating with preference towards the latest hardware available . . . I've always found Cakewalk's backwards compatibility to be amazing, probably best in the DAW worlds, so there may just be a configuration setting (or soundcard) to adjust somewhere to remedy this.





I've updated my specs in my signature to reflect 64 bit Platinum, although it still shows 32 bit. Maybe I need to log out and back in. I assume that's what you meant about updating my system specs. In my 2nd test today with V-vocal as I freshly rebooted. I opened a project with 3 audio tracks. The lead vocal is one long clip, so I split it, into a 2 bar clip and opened V-vocal, the fact that it froze in this situation indicates a pretty serious problem on such a basic song file.
 
 This is a year old Jim Roseberry fast computer, Win 10, all updates current. I've used V-vocal for more than 10 years and have always tuned only small 1 or 2 bar clips and immediately choose "bounce to clip". Since V-vocal sometimes can be squirrelly, like you said, This method has made V-vocal very stable and predictable until today.
 
For me, V-vocal is opening in the multi-dock for editing, not a separate window. It seems I made it that way in my template, so it never opens in a free window anymore. Although when I tried to open it today, when it froze I could see the clip with the V-vocal name in it, but it didn't appear in the multi-dock, it just froze with the hourglass. So is V-vocal working ok for you? Are you using the most current Plat 2016.08? Every other version of Plat worked fine.


Hi again Gerry . . . yes I have the most recent version Sonar Platinum 2016.08 on my system, and mostly V-Vocal seems to be working OK. I say mostly because it is a bit buggy in some instances, though I can't pin down a repeatable reason why weirdness does occur, though it's certainly not crashing my system like on yours.
"Jim Roseberry" . . . certainly sounds like your system is rock solid, As a further test, I created a brand new project, inserted some audio, made it into a V-Vocal clip, and all worked as expected.
 
 
2016/09/09 07:02:42
Bristol_Jonesey
V-Vocal has always been a bit flaky, on even the best of systems.
 
But you can mitigate a lot of problems by following a few simple rules:
 
  1. Only EVER work in short clips of a couple of bars.
  2. Before working on a single clip, bounce it to itself (bounce to clip)
  3. Make sure the signal is at a healthy level
  4. Make sure the signal is free from noise
  5. "Top & Tail" both ends of the clip
VV is of course no longer shipped with SONAR and hasn't been for several versions, so naturally there's no support for it either.
2016/09/09 13:47:24
gmp
Bristol_Jonesey
V-Vocal has always been a bit flaky, on even the best of systems.
 
But you can mitigate a lot of problems by following a few simple rules:
 
  1. Only EVER work in short clips of a couple of bars.
  2. Before working on a single clip, bounce it to itself (bounce to clip)
  3. Make sure the signal is at a healthy level
  4. Make sure the signal is free from noise
  5. "Top & Tail" both ends of the clip
VV is of course no longer shipped with SONAR and hasn't been for several versions, so naturally there's no support for it either.


 
I realize there's no support for it and I don't need that, because I know all the quirky things and know all the workarounds and use your methods above also. Yet I do expect Cakewalk to make sure it works with all the newest versions as it has until this version.
 
I just reverted back to an old image file that has been the most stable Plat of all so far, which is 2016.03  I've had problems with all the versions after that. Mostly just little things. I've opened the same project and found that V-Vocal works perfectly with 2016.03  So this is clearly a bug in 2016.08
 
I did a little more testing last night and found that it appears that when I import too many audio files it triggers the problem. For instance I opened my template and dragged in the 6 stereo vocal files that I originally had trouble with. V-vocal worked fine. Then I dragged in a stereo file into the song and when I tried to use V-vocal on one of the vocal tracks it crashed. I then tried the same experiment dragging in instead 2 mono wav files and got the same result  - V-Vocal crashed trying to tune a vocal.
 
So the cause is dragging in more than 6 stereo tracks or maybe it’s different bits. The 6 vocal files were originally imported by Plat from a CD, so they’re 16 bit, 44.1 and the additional files I dragged in were 8 bit and the mono files were 16 bit. Whatever the reason this is clearly a bug that’s not present in earlier Plat versions.
 
I hope someone else can verify this problem
2016/09/09 16:44:04
orangesporanges
Sounds like a good time to explore Melodyne. That being said, I recently ran into an issue with Pentagon I not opening on the latest version of SPLAT. Remedy? Run as Administrator. I think some of these "long in the tooth" plugs, tools and instruments like DXi's are finicky on Windows 8 and above, and even in Sonar itself. That would be the first thing I'd try.
 
2016/09/09 18:49:25
Anderton
I thought V-Vocal was brilliant, but as Windows and SONAR progressed, and Roland stopped maintaining it, it became increasingly flaky. When I started using Melodyne, I kicked myself for not having done it sooner. If nothing else the sound quality was much more natural. Remember, V-Vocal was released over 10 years ago, so it was in design before that.
 
However, the bad news is that to do everything V-Vocal did you really need the Editor version of Melodyne. That means a paid upgrade. The good news is Melodyne does it so much better. The Pitch Modulation tool alone is invaluable, and the percussion algorithm is fantastic for leveling out vocals without using dynamics processing.
 
And the polyphonic pitch correction! What really sold me on Melodyne was when I did a slide guitar part and the slide landed on the right note but at an angle, so half the notes were sharp and half the notes were flat. Melodyne fixed it without altering the slide itself. Messed with my mind...
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account