Sylvan I did discover that if I start a new project in Platinum, the glitch does not occur. If I open a project that was produced in X3, it does occur.

Thats what I'm seeing too

I'm running platinum as well, but haven't noticed this issue... 
I remember having some initial issues with x3 that turned out to be audio driver mode was reset to wdm for some reason when i first used it.  when i switched to asio i still had a few issues, so i did the rename aud.ini file and restart sonar to rebuild audio preferences trick.  
have any of you guys checked driver modes / rebuilt your aud.ini files yet?

Sylvan
I will do that Noel. I did discover that if I start a new project in Platinum, the glitch does not occur. If I open a project that was produced in X3, it does occur. I will follow your steps shortly. I must do a few things first (family errands).

That's interesting. One thing we saw with your video is that your disk meter shows that you are close to full with your audio hard disk. I wonder if you are getting into a state where the disk cannot keep up or is fragmented and therefore slow. Some things to try. Hover your mouse over the disk icon in the disk meter area and see how much it is using when the glitch occurs. If you see spiking that could be a sign of overload. Have you tried copying your project to another drive that has more disk space?
 
Also Melodyne has a disk cache that is stored here in my docs: \Documents\Celemony\Separations
This cache can grow to be huge if you have never cleaned it. It could also be corrupted.
Try clearing out that cache by deleting the files in that folder and let Melodyne build it again. See if that resolves the issue. I have had some weird things happen when that gets big. You can also configure the cache size in Melodynes preferences or make it smaller.
 
Let me know if this resolves it.

Noel Borthwick [Cakewalk]

Sylvan
Also Melodyne has a disk cache that is stored here in my docs: \Documents\Celemony\Separations
This cache can grow to be huge if you have never cleaned it. It could also be corrupted.
Try clearing out that cache by deleting the files in that folder and let Melodyne build it again. See if that resolves the issue. I have had some weird things happen when that gets big. You can also configure the cache size in Melodynes preferences or make it smaller.
 
Let me know if this resolves it.

Noel,
 
Cleaned the cache and tried Melodyne again. Sonar crashed 3 times in a row trying to add Melodyne. Finally got it working - clip played correctly couple times but after 3 plays or more, the glitches did happen.
Added the performance monitor but now the glitch disappeared.
 
Erik.

Last thing to try. Increase your playback IO buffer size in Preferences and report back if it changes anything.

Noel,
 
I looked in the Separations folder but it was completely empty. I played the project with Melodyne in that region while hovering over the disk icon in the control bar, but no spikes.
 
I copied the project to another hard drive with more space and ran it from there, and the glitch disappeared. So then I went back to that project on the full hard drive and it started working correctly there too. 
 
I tried some other random project and Melodyne worked as expected. I am now unable to reproduce the problem consistently. I will keep an eye on this and if I can come up with something repeatable, I will let you know.
 
In the meantime, I can only imagine how you are going through possibilities and scenarios in your head even during your time off. It just shows the pride and dedication you have to this excellent DAW and company. I just want to recognize your efforts and say thank you for your care and hard work. I and many others really appreciate what you do. I could not do what I do without SONAR, and SONAR is what it is today thanks to you and the whole crew at Cakewalk headquarters. I am so thankful for Boston (because of Cakewalk) that I even stopped hating the Patriots for knocking the Chargers out of the playoffs a few years ago. I will even watch and cheer for them during the AFC Championship game against the Colts.

I can also reproduce this problem with an old X3 project using Melodyne Editor. I did not install Melodyne Essential from Command Center and had no problems with SONARPLT recognizing my previously installed Melodyne Editor. My C: drive disk space usage is also fairly high (82%) but not showing red in the Disk Meter. I have 12GB of RAM and my System Memory Usage meter was at 19%. I haven't tried it with a new project yet.
 
I find that I can reproduce the problem a little easier if I have two different clips set up as unrendered Melodyne Region FXs at the same time. I can open the Melodyne editor in the Multidock or just open Track View and start and restart audio playback by double-clicking in the Timeline quite a bit. Eventually the audio playback will start to stutter or skip. I tried many combinations of playback IO buffer and ASIO buffer sizes (including playback buffer maximum of 2048 and my ASIO max buffer size of 1024) to no effect. I also cleared the Melodyne cache folder to no effect.
 
I can also reproduce the problem with only one Region FX, but it seems to take a lot more effort to make it happen. 
 
I could never reproduce the issue again once I rendered the regions. The rendered audio played perfectly even when the clip would stutter while being auditioned. Tomorrow I'll try to reproduce the issue with a new project.
 
Regards,
Don
 

This may be a clue, or it just may mean I haven't run enough tests because it's an intermittent issue. But, I've never had this behavior occur if the RFX region was not inside a loop, and I've only had it occur if the RFX region was inside a loop.

Hi Sylvan,
 
You are welcome, no thanks necessary its job to investigate this stuff and make it work smoothly for you guys. We spent a lot of time on melodyne/ARA support even in this cycle for some new stuff as well as improvements and bug fixes. The intermittent nature of this is probably why it was not seen and some of our testers were trying it on pretty large projects. Even Celemony who have been in the loop with us throughout did not notice this issue.
Don I will try following up on your suggestion of having multiple regions. There could be something to that scenario that makes it more likely to happen. I think its unlikely that its related to old projects vs new. I suspect newer projects write audio data in an area of the drive that is less congested and therefore disk latency is lower.
 
I'm sure we'll find it soon. I'm waiting on Celemony for some pointers on the symptoms and should have some more leads then. The glitching is not related to latency - if you notice it sounds like a little snippet of audio is repeated. To me that sounds like an ARA disk read within melodyne failed or took too long to complete and therefore resulted in the previous chunk being repeated or something. ARA is a complex concert of operations between the DAW and plugin so it can be tricky locating where the problem is sometimes. In this case the actual glitch is occurring within Melodynes engine but it could be caused by a delayed host read or something. Once I can get a repro it will be easier to investigate.
 

I finally installed the update today, and everything is great. No weirdness with Melodyne, no other issues that I have noticed so far.
 
Thanks a lot Noel for the speedy update, you guys rock!
 
John