Just upgraded my Melodyne Editor 2 to Melodyne Studio 4 . . . but now when I open my Sonar Platinum projects, I get an immediate Sonar crash on any project containing instances of Melodyne VST3 region FX. If I launch these projects in safe mode without the Melodyne plugin, they open just fine. Hmmm, so what's the deal with this ?
 
I can say that my Melodyne 4 Studio install seems to load as a new VST3 insertion into Sonar, that all works, but it is not backwards compatible with any projects containing the older version of Melodyne Editor 2.
 
Anyone else have this issue that has done the upgrade, or do we need to wait for the Manchester update for this to work ?

I find leaving any instances of region FX in a project causes me issues, so I try to make sure that I leave none behind, bouncing to clips as I go. Having said that, I will watch this one with interest, because I'm about to the same and upgradge from Editor 2. I'm hoping that Studio 4 will give me the option to leave multiple instances within a project while I keep working, without causes the crash issues of Editor 2.
 
Glad you brought this up.

Yes, I've never had any issues leaving the Region FX unfrozen or unbounced in the past. I usually wait until the very end of the project phase to do this.
 
Also, the Melodyne Studio 4 installer automatically removes Melodyne Editor 2, so this may be the root of the problem. Seems they don't want the two to co-exist for some reason ?

Melodyne edits are saved in the cwp, so the backwards compatible issue is a valid one. It seems 4 does overwrite 2, but I seem to recall someone saying they had both.

I still have outstanding emails to Celemony asking specifics on several items, including this one. I almost updated Melodyne on "good faith" even though the demo install went belly up, but have seen enough comments I will not get it without running it first.

Celemony's forum went offline when 4 was released as well, so information is highly scarce and subjective.

When I opened a project with Melodyne 4 Studio and edited a region created with Melodyne 2 Editor, I got a pop-up saying that if I saved the region (with Melodyne 4) I could no longer open the region with Melodyne 2. Not really an issue since Melodyne 4 upgrade replaces Melodyne 2.

Same here - thankfully!
 

Celemony mention the incompatibility on their website. You can run the 2 versions side by side. At least that's what I understood.

AFAIK Melodyne Studio 4 does overwrite and replace editor 2 BUT Melodyne Studio 3 if you have it will run as a stand alone and coexist with Studio 4
 
Fred

microapp
When I opened a project with Melodyne 4 Studio and edited a region created with Melodyne 2 Editor, I got a pop-up saying that if I saved the region (with Melodyne 4) I could no longer open the region with Melodyne 2. Not really an issue since Melodyne 4 upgrade replaces Melodyne 2.

Well, that's promising . . . so you are saying you can open projects containing Editor 2 clips, on my system it's causing Sonar to crash right at the opening these projects.

mudgel
Celemony mention the incompatibility on their website. You can run the 2 versions side by side. At least that's what I understood.

Hi Mike, I can't locate this on the Celemony website, and if I re-install Editor 2 won't it just overwrite the Studio 4 VST3 file located in C:\Program Files\Common Files\VST3\Celemony\Melodyne\Melodyne.vst3  ?
 
What I do see on the Celemony website is a chart comparing their various Melodyne editions, and at the bottom of that chart:
"Intercompatibility – Open and edit projects created by other editions" . . . so this should work, right ?