I went through this once before with Platinum and ended up having to uninstall and re-install Melodyne to get it to work again.  I'm sure that's what I'll end up having to do again....BUT...was just going to check here to see if this was a common problem with the new foxboro release.
 

I have t had a problem. It's become one of the first things I do when I update. Is check the region fx and other plugins as that's the most common issues I read about. While I've had a few inexplicable plugin issues Melodyne hasn't been one of them.

Is it the VST3 version that you guys use?

You tried this VST reset/rescan thingy beforehand I assume?
Can you validate please all the file paths in CCC settings and Sonar Preferences to make sure no changes have been put in. Sonar has changed these values in the past during upgrades at least for me and a few other people, and we've needed to correct them.
 
Failing that what is the actual behaviour? You try to create a RegionFX then what happens?
 
Cheers...

I have not had this problem.  melodyne worked fine for me after Foxboro.
 
are you using it as an FX in the FX bin or are you using it as a region FX?  have you tried both ways?

Thanks for that Beagle! I've been creating Region FX and will try it in the FX bin. I've not had any trouble since installing Foxboro. I did just before that with older projects, though they had open,  ie not rendered clips.
 
I didn't reinstall Melodyne or anything, but I closed the open Region FX, and started going at it, by creating the Region, editing and then rendering with no issues or problems.
Michael

Must've been something...though I can't say what...specific to the audio file in that particular project. I uninstalled and reinstalled melodyne and had the same behavior but tried some other older projects which worked fine. Sigh.

Well Ol' Pal, you've encountered the mysterious Sonar corruption bug. I've seen many posts and experienced the same sort of problem. It worked one day and then not so much. Some corruption of the files' essence happens and then the project is junk.
 
If you find a way to fix it other than recreating the file, let us know.

pentimentosound
Thanks for that Beagle! I've been creating Region FX and will try it in the FX bin. I've not had any trouble since installing Foxboro. I did just before that with older projects, though they had open,  ie not rendered clips.
 
I didn't reinstall Melodyne or anything, but I closed the open Region FX, and started going at it, by creating the Region, editing and then rendering with no issues or problems.
Michael

I don't ever use the region FX myself (for Melodyne), I always use it in the FX bin.  I've been using Melodyne long before region FX ever existed in sonar, so it's just 2nd nature to me to insert it in the FX bin - I don't even think about region.
 
I'm sure the region FX are good for some people, but it's just not good for my workflow. 

yorolpal
Must've been something...though I can't say what...specific to the audio file in that particular project. I uninstalled and reinstalled melodyne and had the same behavior but tried some other older projects which worked fine. Sigh.

did you also use Audio Snap on that audio track?  I've seen anomalies using AS and Melodyne before, so I always use AS first, then bounce it to clips so that AS is no longer "active" and then I'll use melodyne on the track.