(SOLVED) Got Platinum...Melodyne no longer appears in region fx

I have the same issue...Build 254 choked on VST Scan with Melodyne Editor and LUFSMeter64...

I said Ignore...but Melodyne is gone in region effects, and doesn't show up at all in VST's...

This did not help with Melodyne not showing up in Region FX or
in the VST List...just an FYI

That was the same message I got.  I checked my Melodyne Standalone
and it said it need to be activated, so I did that, and the Standalone was
fine then....but it still doesn't show up in Platypus...in either VST or Region
FX....I'm doing a rescan of VST's now...

Hopefully someone will help us soon. Dont understand why its fine in X3 and standalone and not in Platinum. tried uninstalling platinum and reinstalling. I even tried uninstalling then installing essentials with command centre and using my editor serial number. 

I installed without issues. Everything seems to be just the way I had it in X3.

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.

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

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.

mrneil2
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.

Hi MrNeil, this is what i did. (i only have vst3 melodyne installed) You dont need to delete, they just need to be dragged somewhere that isnt a VST scan path.
 
1) opened c:\programfiles\common files\vst3 folder and located the melodyne.vst3 file
2) dragged it from folder onto desktop.
3) opened sonar and rescanned VSTs
4) closed sonar
5) dragged melodyne.vst3 file back from desktop to original folder
6) opened sonar and rescanned VST's
7) done!
 
Hope it works for you
 
Bibs

Did you do a "reset" of the VSTs before you scanned?

That solved it for me as well. Thanks for the help Clint!!!
 
Rocky

I did an uninstall and reinstall and it solved the problem...
Crazy...something is definitely wrong there with the code
for that to happen....

reginaldStjohn
Uninstall and re-install did not work for me. However, I did not rescan after uninstalling so that may be the key.

Yes...I did that...I uninstalled and then opened Platinum...then reinstalled and opened it again
and all was fine...