You are welcome, it is a good workaround 'til the fix.
 
The issue number is CWBRN-24814

thanks for the workaround. hope this gets fixed in X3

Transcending Music
You are welcome, it is a good workaround 'til the fix.
 
The issue number is CWBRN-24814

Thanks :)

neirbod

Seth Kellogg [Cakewalk
No, I understand the actual issue. You're pointing out that some users don't read the Melodyne installer prompt. If a user can't read an installer prompt, which in Celemony's defense is quite informative, what says they'll read documentation we present?

I found the Melodyne installer prompt confusing as well.  I read it, just didn't quite understand what button to push in the context of a patch.  Any way to make it clearer would be appreciated.  

I found the Melodyne installer prompt confusing as well.  I purchased Melodyne Editor but didn't hit cancel as I figured the update may have something to improve compatibility.  I think the quality assurance engineers should consider things that seem obvious to them may not be for the new or even average user.  

Yes, I originally thought that because there was a fix for the Melodyne issue, then I should press the "modify" button in the installer, as this would apply the fix.
In the moderator's defence Alex, the melodyne installer is the last option in the installer and pops up after Sonar has installed, it is also a cumulative update and would need to be installed if you didn't have the latest version. But I do agree it is confusing and should be documented. The update does not need to be applied if you already have the latest version installed.

The Melodyne installer was confusing here too... I also hit modify. I have the full editor too.

Sorry to rake up an old thread, but I was thinking about this Melodyne "blobs not lining up" issue tonight. Could it possibly be (and bear with me here ) that this is -at least in some cases - two adjacent slip-edited clips each with their own region FX? Because the first Melodyne region is going to show the blobs not only from the visible part of the clip but also the rest of the clip that's been slip edited out of sight. So when you play back the audio, the Melodyne cursor is going to continue on past the point of the slip edit to the "hidden" part of the clip. But on Sonar's timeline, of course, playback goes on to the 2nd clip. In other words, the Melodyne window is not a direct mirror of what's going on in the track, it's showing what's going on in the clip, part of which may have been slip-edited away. I hope I'm making sense here. Probably not.