Gregkonji
Having to render the regions before closing the project to avoid issues is a bug if I've ever heard of one. Melodyne adds artifacts to my tracks that I sometimes don't hear till I listen a day later with fresh ears. Fresh ears also allows me to judge if the correction is acceptable or not. Sometimes the original sounds better than the corrected version. Having to render before closing kills this going back option.

Was this an issue with previous versions of Melodyne? I don't recall having issues with open fx regions with Melodyne editor 2. I never rendered my regions before.

I certainly do now that I've upgraded to studio 4. My old projects with open regions have bizarre things going on.

Just clone the track first. 

it does seem that melodyne is super-sensitive to, well, everything else

Celemony really needs pressure from customers to let them use any version they have purchased. That whole M4 thing came across as a way to shoe horn customers into the same bin for potential piracy issues than dedication to product for me. They also did not make that one-way decision clear to many (even offering a "free" M4 Essential upgrade on behalf of Cakewalk), and then promptly went dark.

Still a sore spot for me as I am reminded of this "free upgrade" each time I launch Editor 2, sorry.

it's prolly so they only have to support 1 version (4.x) not so uncommon these days

Just to be clear, I didn't say support previous versions, I said use them.

Support for M4 compared to M2 is significantly less from my brief experience with M4 as it is, but the issue is to allow users to have a "fallback to steady state" option.

At least Cakewalk realized the need for a rollback option. Folks who make their bread and butter from their DAW have no recourse when software updates shut them down otherwise.

Succeded with the apply audio effects, except for some minor artifacts that I can take out with the volume envelope. Thanks again!

It's good practice with any clip manipulation to finalize it before moving on. This reduces cpu load which can result in strange behaviors and unexplained anomalies.

HI, I'm having trouble getting sonar to find Melodyne 4 as a plug in. I re-scan and point directly to the folder where it was installed and it still can't find it. 
 
Can anyone help me straighten this out?
 
 

32 or 64 bit or both? Make sure you're pointing to the right directory.

Gregkonji
Having to render the regions before closing the project to avoid issues is a bug if I've ever heard of one. Melodyne adds artifacts to my tracks that I sometimes don't hear till I listen a day later with fresh ears. Fresh ears also allows me to judge if the correction is acceptable or not. Sometimes the original sounds better than the corrected version. Having to render before closing kills this going back option.

Was this an issue with previous versions of Melodyne? I don't recall having issues with open fx regions with Melodyne editor 2. I never rendered my regions before.

I certainly do now that I've upgraded to studio 4. My old projects with open regions have bizarre things going on.

this is something I've never understood. if your using Melodyne, its because your trying to fix something.
so what do you have to lose by rendering really ? the fresh ears thing is also subjective.
your either fixing something that needed fixing to begin with, so there is no loss.
 
only once or twice since using Melodyne in my projects (which is well over 200) have I thought, I better make a back up/clone just in case I want to revert to this track that was messed up to begin with.
see the logic ?
I also never use Melodyne on a whole track. only portions that need fixing. so to each his own, we use this FX in different ways. I find when you use Melodyne on a whole track, your some what defeating the purpose of a natural sound, unless your using on something other than vocals. (like an out of tune guitar track) which even then, I rather redo/re record the whole track then try to fix a whole track.