I run at 128 (IIRC) and typically don't have a problem using Melodyne. I'm usually only editing small clips though, not a full score.
 
If I do get any hiccups I bump my samples.
 
Regards,
 

I've been using Melodyne for a number of years with Sonar and was a Beta tester for them when there was a problem with a memory leak between Sonar and Melodyne that took a long time to fix (me and Skyline on this forum and it turned out to be a Melodyne issue). It was around this time, this recommendation came from Melodyne. Since the fix was made over a year ago, buffer size is does not seem to be critical at all. In fact when I was using Sonar and Melodyne post fix, i felt that I had access to such a special set up. And now Sonar integrates it in Producer for all !!!.  No benefit for me but it is for nearly every other Sonar use,r so you guys now have integrated access to truly 2 great software progs. To be clear I run at whatever buffer size I want and it works now. So agree with the other posters.
 
Hope helps

Wow!
 
My humble thanks to everyone for chiming in on this... Lots of good info as well as experience/opinions.
 
You have all convinced me of what I suspected so I will ignore the warning and just remember that if I start experiencing any problems when running Melodyne, it's a good item to check/test...
 
I typically do very short bits of correction. If a track/performance needs much more than that I'd probably opt to re-sing it... But there can be times................. ;-)
 
I've had mostly very good results in the past using V-Vocal and have always dreamed of getting Melodyne.... Now I'm 2/3 of the way there. I have a working copy of essentials (single-track?) and now dream of one day upgrading it to full Editor!
 
Thanks Cakewalk!
 
...and all the Cakewalk Team!
 
......oh, and very important. To all the Forum Members who are always willing to help out other Sonarites in need!
 
Keni
 

I usually increase to 512 on larger clips. Like others here, I don't adjust for smaller clips.