Yesterday while trying to open a project I've opened without issue in the past, will not now open. It tries, but at the last second, I'm getting a Melodyne error, fault reporter, etc. I tried opening in Safe Mode also, but still get the same Melodyne error and the song won't even open in Safe Mode.
 
So I then tried opening Melodyne on an audio test track in another project.  But as soon as I try to create the Region FX, I get the same crash as noted above. All projects without Melodyne open and operate fine. I even tried deleting the actual audio files I thought had Melodyne on them, to no avail.
 
I did the Windows update a couple weeks ago and the latest Platinum update. Is there a new Melodyne editor update somewhere that I'm missing? I'm at a complete loss here, and cannot open this specific song.
 
Thanks guys for any help. Maybe I need to go through Celemony to get this fixed?
 
~Jeff
 
EDIT (Solved): Melodyne was definitely the problem. I uninstalled Melodyne from within CCC. Then uninstalled again via Windows. After that I was able to finally open my project. Turns out there were 4 vocal clips that had un-rendered melodyne regions. I'm going to assume that rendering regions (bouncing) prior to closing out the project is the safest way to do things and will prevent this from happening again.
 
So I removed the regions on the clips and saved as a different project (to be safe). Reinstalled Melodyne from the Celemony site and within CCC, and all is fine now! So the moral of the story......render before you close.
 
~Jeff

Just to ask...Have you installed other DAWs onto the same system or drive with Sonar?..
 
Reason being I Find Avid PT 12.5 installing drivers of it's own, on some of my systems, causing perhaps issues with audio and midi .
 
Also some application which is always on, and running checking for updates....(and some know how I feel about that these days)..lol
 
And On my Mac Pro...Melodyne Studio 4 Crashes in standalone multi track mode, when trying to save the sessions, when trying to get tempo mapping and such, of badly performed tempo players....( I thought it might solve for, so I bought it)...well we do dream of solutions for bad timing here for some who cannot play to a click, or keep time .
 
any hoot..The tech told me back a few months now, that the mac version has a bug,(no vu metering when recording is showing up) and they are working on it.
Haven't heard of any updates yet though....and they got my data dumps, saying something is wrong with the audio drivers...Yet it is always Melodyne crashing it.
 
And I do not think PC is the same problem..in the same way...but file linking or saving might be...Management issues of data controlled via...Device managers.....But seems all things when the XY or Z is in constant flux...no one can really solve for x untill it is stablized to no change...To standards.
 
Good luck and cheers...Keep a stiff upper lip, and your hair on your head, when told..."Please stand bye for station I Dent if i cation"...could be a long wait for...if not found..But I hope You find, or they fix it.....
 
 
Best of the Day to you!
 
Cheers!

Sir Les
Just to ask...Have you installed other DAWs onto the same system or drive with Sonar?..
 
Reason being I Find Avid PT 12.5 installing drivers of it's own, on some of my systems, causing perhaps issues with audio and midi .
 
Also some application which is always on, and running checking for updates....(and some know how I feel about that these days)..lol
 
And On my Mac Pro...Melodyne Studio 4 Crashes in standalone multi track mode, when trying to save the sessions, when trying to get tempo mapping and such, of badly performed tempo players....( I thought it might solve for, so I bought it)...well we do dream of solutions for bad timing here for some who cannot play to a click, or keep time .
 
any hoot..The tech told me back a few months now, that the mac version has a bug,(no vu metering when recording is showing up) and they are working on it.
Haven't heard of any updates yet though....and they got my data dumps, saying something is wrong with the audio drivers...Yet it is always Melodyne crashing it.
 
And I do not think PC is the same problem..in the same way...but file linking or saving might be...Management issues of data controlled via...Device managers.....But seems all things when the XY or Z is in constant flux...no one can really solve for x untill it is stablized to no change...To standards.
 
Good luck and cheers...Keep a stiff upper lip, and your hair on your head, when told..."Please stand bye for station I Dent if i cation"...could be a long wait for...if not found..But I hope You find, or they fix it.....
 
 
Best of the Day to you!
 
Cheers!

 
Nope. No other DAW's. I'm faithful to my Sonar.
 
Not sure if it's related, but I also often get crashes when saving projects. Too bad, cuz my system was running very solid for while. Now this.
 
Frustrating that I can't even open the project in Safe Mode to remove the freaking Melodyne! I wonder what will happen if I uninstall Melodyne, then try to open the project???

There are various threads on Melodyne crashing SONAR and I believe I'd read that Celemony was aware of the problem and in the process of fixing it with an update, but to my knowledge they still haven't nailed it down yet. Some users have experienced no problems whatsoever with Melodyne, and others are frequently having issues. I used to get crashes all the time (especially when using Melodyne as a Region FX) but the problems decreased substantially when I just used it as an insert.
 
I did however get another Melodyne crash a few days ago when opening a project, so yeah...that's fun!

I get the same type of crash when I use Melodyne or V-Vocal, but it's Melodyne's fault? That doesn't make sense.
 
Faulting application name: SONARPLT.EXE, version: 22.10.0.19, time stamp: 0x5808dac9
Faulting module name: MelodyneCore-4.0.4.004.dll, version: 4.0.4.4, time stamp: 0x56f42e5c
Exception code: 0xc0000005
Fault offset: 0x0079f412
Faulting process id: 0x17dc
Faulting application start time: 0x01d22f9f3c01ab93
Faulting application path: C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.EXE
Faulting module path: C:\Program Files\Common Files\Celemony\Bundles\MelodyneCore-4.0.4.004.dll
Report Id: 9c60771b-9b92-11e6-b5c5-00241dd6013b 
 
Faulting application name: SONARPLT.EXE, version: 22.10.0.19, time stamp: 0x5808dac9
Faulting module name: Cronus.dll, version: 1.5.3.0, time stamp: 0x4d367513
Exception code: 0xc0000005
Fault offset: 0x00005e0d
Faulting process id: 0x1360
Faulting application start time: 0x01d22f9f01362670
Faulting application path: C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.EXE
Faulting module path: C:\Program Files\Cakewalk\Shared DXi\VVocal\Cronus.dll
Report Id: 742e43cf-9b92-11e6-b5c5-00241dd6013b

Now I am joining the melodyne crash club.
Upgraded to Sonar 2016.10 and Melodyne 4.04. often crashes creating a Region FX.
Sent a mini dump and got an email with link but the link is broken:
https://www.cakewalk.com/...atus/<ticket.no>
Whats wrong?

Sonar crashes often when an attempt is made to create a  new melodyne region fx (since the 2016.10 update) Reported error, but same as for pbandit: the link to track progress comes back as broken
 

you said you uninstalled for CCC, I don't know what CCC is ?    Did you lose any of Melodyne corrections, when you uninstalled the program?   Thanks in advance.    

Cakewalk Command Center.