Melodyne disappeared in region fx with X3e when a Waves tech deleted extra waveshells on my machine. I was hoping that Platinum would fix it.
 
Rocky

If you already have melodyne installed in X3 there is no reason to reinstall it in Platinum.
If its not showing up in region fx then you possibly don't have the vst3 version installed. You can also try resetting and rescanning to see if it picks it up again.

I didn't even install Melodyne...I already had Editor Installed...
Somehow it got "deactivate" and I had to reactivate...but it's
still not showing up in either VST or Region FX, even after re-scan...

Also, I have 8 cores...and am getting intermittent dropouts...but nothing showing
up wrong in the Performance meter.

I also brought in ONE project from X3e that has 2 tracks with Kontakt
Choirs on them...they sound like Cats being stepped on...all my other instruments
are fine...just the Kontakt Choirs....strange stuff Maynard....

I had a problem in X3 a few weeks ago with Melodyne and this fixed it. I removed the dll files from my vst2 and vst3 folder, then opened Sonar and did a scan. I closed Sonar and put the dll files back to where they were and opened Sonar and did a scan...fixed.

I have Melodyne Editor 2.1.2 and the VST3 is at C-> program files -> common files -> Celemony -> Melodyne. This folder is listed in the plug-in manager scan path. After scanning, Melodyne shows up in the VST list but not VST3 list. Fwiw VVocal doesn't show up in the VST3 list but shows under region fx. I get a VPA plugin rejected VPA host compatibility error. I also got a registry read error.
 
Rocky

Got the same errors with melody in platinum.
I've deinstalled all my Melodyne software and installed melodyne essentials with command center. After that I got back my melodyne editor in sonar.
_Markus

You should try what I posted...it couldn't hurt, and it fixed my problems.

I had the same problem as well with UltraVerb and UltraChannel due to DLL hell. If the VST being scanned brings in an older version of a dependency and then later another VST is scanned which needs a newer version the same dependency, the later one will fail to load. If by chance the VST scanner reverses the scan order of these libraries, the issue doesn't happen.
 
Remove the VST that failed, start sonar up and let it scan, shut it down, put the dlls back, and then start sonar again will get around the issue.

Thanks guys, worked perfectly!

I have been getting the same error: Error: [Melodyne] Call initProc for some time now on Sonar x3E. I am waiting for my authorization code from JRR for Platinum.
I have tried the solutions from other threads with no success and I usually pick the ignore option. (I’m not at home now so I don’t know the exact wording).  One solution that did not work for me was moving the dll’s up a folder.
Since it seems this solution works I am going to give it a try when I get home but I have some questions.
Clint said (post 14)“I removed the dll files from my vst2 and vst3 folder, then opened Sonar and did a scan. I closed Sonar and put the dll files back to where they were and opened Sonar and did a scan...fixed.”
How do I remove the dll’s? Does it mean delete them? If I delete them how do I get them back?
JS516 said (post 18) “Remove the VST that failed, start sonar up and let it scan, shut it down, put the dlls back, and then start sonar again will get around the issue.”
I guess it’s the same question, how do I Remove the vst that failed? Does this mean delete the vst and reinstall?
I really need step by step instructions.