Melodyne also saves its edit data in the cwp if not bounced, I am not sure if this has any contribution though.

I can't say I've ever had any Melodyne issues either, from X3 through Foxboro (knocks on wood).  
 
But as others mentioned it does require a non-AudioSnap/looped/etc clip.   I'd make a copy of one of these clips and move it to a new audio track, bounce it in place, then try Melodyne again.  That may help narrow down whether it's a clip or project-specific thing. 
 

I've used it extensively since it was introduced to Sonar, on both old and new projects, and it has been absolutely rock solid (using region fx - I have never used it as standalone or in fx bin.)

millzy
I've used it extensively since it was introduced to Sonar, on both old and new projects, and it has been absolutely rock solid (using region fx - I have never used it as standalone or in fx bin.)

Same here, except for pilot error (e.g., bouncing while the track is muted).

Anderton

millzy
I've used it extensively since it was introduced to Sonar, on both old and new projects, and it has been absolutely rock solid (using region fx - I have never used it as standalone or in fx bin.)

Same here, except for pilot error (e.g., bouncing while the track is muted).

That made me smile - it's the kind of thing I would do.  I have had an intermittent problem with splitting clips for some time.  Eventually the penny dropped that I was highlighting a "comp" track clip, with many lanes/layers, and wondering why "S" wouldn't work..  Opened up the take lanes and voila.. 
 
I'm glad I discovered it before I came on here screaming..

jb101

Anderton

millzy
I've used it extensively since it was introduced to Sonar, on both old and new projects, and it has been absolutely rock solid (using region fx - I have never used it as standalone or in fx bin.)

Same here, except for pilot error (e.g., bouncing while the track is muted).

That made me smile - it's the kind of thing I would do...

One reason I'm not in here talking about my problems with SONAR is most of the time, I've done something dumb. The only thing I can blame SONAR for is not being smart enough to tell me when I'm dumb.
 
Computers may have invented artificial intelligence, but humans excel at artificial stupidity. 

Yep, that's how it works for me, when "it isn't working!" LOL
I'm not having any issues with Melodyne, now that I have the "render habit"
 
Michael

Anderton
 
Computers may have invented artificial intelligence, but humans excel at artificial stupidity. 

I have found Melodyne (I have the full editor version) to be rock solid in the <RegionFX> mode as well. Similarly, most of the bugs I have found using Sonar Xn relate to my impatience and thinking that I can change things on the fly (i.e. while mixing, or worse while recording). Sometimes it just forces an audio halt, but sometimes crashes the program. I can only recall one corrupted file (beyond recovery) a couple years back.

I have part of this message in another thread but I am putting it here also because of the emphasis here on pilot error causing problems, which is definitely possible in my case.
 
I just started using Melodyne Editor as a plug-in in Sonar X3 64 bit in Windows 7 and have a problem of another blob moving when I change the pitch on the one selected.
1-Snap is off.
2-It occurs 2 bars away from where I am changing the pitch, so I would not think the pitch transition would be relevant.  (It also occurred when I used the program yesterday in the same bar.)
 
Specifically, when I move a blob at A# down to A, it moves a C two bars away down to B.  When I move the B back to C, the earlier note goes back to A#.  When that happens, the Scale Editor also changes from C major to D major.  I do not want this to happen!!!
 
I am wondering if this has something to do with the way Melodyne handles scales, which I can change, or if this is just a bug in the way it works within Sonar.  Also wonder if there would be difference in using Melodyne Essentials rather than Editor, or in using Sonar 32 bit.
 
I am starting it from Region FX.  Anybody have any ideas whether it is me or the programs not working together properly?  Thanks.

I have part of this message in another thread but I am putting it here also because of the emphasis here on pilot error causing problems, which is definitely possible in my case.
 
I just started using Melodyne Editor as a plug-in in Sonar X3 64 bit in Windows 7 and have a problem of another blob moving when I change the pitch on the one selected.
1-Snap is off.
2-It occurs 2 bars away from where I am changing the pitch, so I would not think the pitch transition would be relevant.  (It also occurred when I used the program yesterday in the same bar.)
 
Specifically, when I move a blob at A# down to A, it moves a C two bars away down to B.  When I move the B back to C, the earlier note goes back to A#.  When that happens, the Scale Editor also changes from C major to D major.  I do not want this to happen!!!
 
I am wondering if this has something to do with the way Melodyne handles scales, which I can change, or if this is just a bug in the way it works within Sonar.  Also wonder if there would be difference in using Melodyne Essentials rather than Editor, or in using Sonar 32 bit.
 
I am starting it from Region FX.  Anybody have any ideas whether it is me or the programs not working together properly?  Thanks.

 
I haven't seen this behaviour but make sure that in Melodyne under Edit/Pitch Grid that No Snap is checked. Also try just selecting the one blob (click and drag with your mouse) with the selector tool (arrow.) You may need to zoom out to just grab the one blob. Now try your pitch adjustment. Not sure if this helps but its all I can think of - good luck!