thanks Jerry, i will try re-downloading.  i have already gone through uninstalling & registry cleaning & reinstalling Melodyne, but i haven't tried this process w/re-downloading my personalized Melodyne file

wetdentist
thanks Jerry, i will try re-downloading.  i have already gone through uninstalling & registry cleaning & reinstalling Melodyne, but i haven't tried this process w/re-downloading my personalized Melodyne file

Any updates? Did this work for you?

not yet, i will probably try this tomorrow morning

no this did not work for me.  i was hoping Celemony would be more of a help, but they punted on vital customer service for me.  i mean, really, how can they not help someone who paid for their update & is having anomaly installation problems to get it installed?  not the mark of a company i would recommend to anyone.

Did you try Cake tech support as well?

not yet. i will probably wait until after the June 1st announcement, since Melodyne works fine on my main rig.  but really, i don't see this as something Cakewalk should be responsible for.  this is a failure of Melodyne installing on a Windows 7 x64 PC that has no problems with any of my other audio software.

When doing a VST scan in Sonar Platinum, I get an error with Melodyne. It says: "Error: [Melodyne] Call initProc" Then it gives me the option to either "Disable Plug-in" or "Enable Plug-in (Risky). 

I sent Cakewalk customer support a message about this a week ago but I haven't heard back yet. This error occurred on both my old laptop as well as my newly built desktop. No idea why it started happening as I used to not have any problems with Melodyne. 

I know this post is 9 months old but I was having the same problem.  This post did not help me but I figured out my particular problem.  So this is for those where my solution to my problem may help.  
 
For me, I had owned a full version of Melodyne Essentials taht was on my old computer.  But then I bought a new computer and also Melodyne Studio. My VST files are on a separate drive from my system drive.  That drive got reconnected to the new computer.  The VST scan kept failing because there was an old Melodyne Essentials DLL file in a folder named Melodyne.  The Melodyne Studio DLL installed in a folder named Celemony Melodyne.  The new one succeeded.  The old one failed because it was not registered nor installed but the error message did not help me find this folder with the bad DLL.  I just got so frustrated that I finally said "What if....?"  I deleted the Melodyne folder with the old DLL and all was well.  Hope this helps someone else in my position.

wetdentist
this past weekend i tried to update Melodyne 4 Studio to 4.0.4 and it was a mess, 

Not sure it helps, but I believe newest Melodyne version is 4.1.0.001, also do you mean Sonar 2017.02 (pre release), or 2017.01, but Im not having any issues with 2017.01 and Melodyne Studio.
 
cheers Submit Post

Dohhh!, just realized its an old post, LOL