noynekker

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.

It did not crash. I could open and edit in Melodyne 4. IIRC, the pop-up warning occurred once I made a change in the Melodyne region.
 
Can you create a new project or edit a project not containing a Melodyne 2 region then edit that with Melodyne 4?
 

noynekker
Hi Mike, I can't locate this on the Celemony website

I tried to go on their forum just now and they've taken it down. Permanently, apparently. They suggest Facebook or one of their other social feeds for questions, etc.

Okay, I think I solved my Sonar crashing issue ! . . . thank you to "microapp" who reported that there was a pop up message appearing when editing the Region FX of Melodyne Editor 2 clips using Melodyne Studio 4. This made me realize it is possible, so I had a closer look at my own system and discovered that my Novation Impulse control surface software interface was to blame for this crashing.
 
Novation uses the Automap software as a VST wrapper, so when the plugin scan happens at Sonar start up it renames the VST3 file. In this case it renamed "Melodyne.vst3" to "!Melodyne (Automap).vst3"
Apparently Melodyne Studio 4 is not compatible with Automap, or at least it doesn't like the renaming of its plugin file name . . . as soon as I removed "!Melodyne (Automap).vst3" from the VST plugin scan path . . . it all works as expected, and I get the pop up message when trying to edit Melodyne Editor 2 clips, saying "warning - - there's no turning back" (basically saying once saved, you can no longer open the Region FX with Melodyne 2)
 
Thanks to everyone for your inputs. Case dismissed.

Open Sonar in safe mode and it won't crash.

FWIW -
When clicking through the upgrade pages at Celemony, on the download
page was a rather convoluted statement suggesting that it's best to do
a clean install...
 
Which would do away with any conflicts with earlier versions, is my guess.

Same problem here - opening a project containing Melodyne Editor 2 RFX regions reliably crashes on open. Running on an iLok I had to relinquish my Melodyne Editor 2 key to upgrade to Melodyne 4 - which was a mistake.  Downgrading back to Melodyne 2 lets me render at least, but not edit (no key.)

I'm getting crashes with a project that contains a Melodyne Studio 4 (not 2)region effect, that wasn't bounced. So seems an eliment of it just being a region effect not a mix of creating in version 2 and opening with 4. 
 
It's no biggie, I was experimenting, so nothing I wanted to keep

Since I solved the issue with Melodyne on my system, I've been using Melodyne Studio 4 a lot inside Sonar Platinum, and it's been pretty solid. Though, one issue I've found is with one older project, where I had many V-Vocal and Melodyne Editor 2 clips . . . when trying to edit further with Melodyne Studio 4 . . . bit of a crashfest . . . until I found that overlapping clips seem to be a problem. As long as I "clean up" the clips, so they are not touching, everything seems to work well. Just thought I would mention this, since apparently there are many having problems.

jassbass
Open Sonar in safe mode and it won't crash.

Yes, if I launched in safe mode, and don't load the Melodyne plugins, there is no crashing . . . except, then I won't have Melodyne actually working, which is kinda' the whole point of this thread.

I agree with everyone and everything :)  How can you put out an  "upgrade", charge me $99 (for upgrading to Editor 4) and not thoroughly test it to confirm backwards compatibility let alone the fact that it doesn't work as a region F/X even on a fresh project???  Lesson learned about "upgrading", or in this case, "downgrading" too early in the rev.