Recently, I updated Melodyne Studio 4.0 to Melodyne Studio 4.1
Apparently, the Melodyne Studio 4.1 update and Sonar Platinum are not getting along . . . at least on my system.
 
Here's the problem I'm having:
Freeze a Melodyne vocal track (created in Melodyne Studio 4.0) . . . the freeze works as expected, but when I try to save the project it throws a melodyne related error, and crashes Sonar Platinum. (Same result in multiple projects, so ruling out a corrupted project)
 
Here's what I've tried so far:
Rollback to Sonar 2016-10 . . . same problem exists
Re-install Melodyne Studio 4.1 . . . same problem exists
 
Guess I can try reverting back to Melodyne 4.0 . . . but Celemony sure don't make that easy !
Anyways, I like the new features and Sonar ARA improvements they've added.
 
Freezing Melodyne tracks in Sonar Platinum used to work for me, but I usually don't do this until I'm near completing a project and the editing is done. Curious that the project opens, and plays perfectly well . . . but I can no longer freeze Melodyne tracks ?
 
Anyone else here seen this happening ?

What do you mean by "freeze"?  Are you bouncing the region to clip after working with it in Melodyne (also known as rendering)?

Because melodyne has always been buggy in sonar for me anyway, I always bounce to clip after correcting.  In the past if I leave two many melodyne clips "unrendered" I would get crashes.  Now that you bring this up, that really is not acceptable in this day and age, and many of the melodyne tutorials have you leaving the melodyne track, "melodyne enabled".
 
I got one crash after melodyne update when enabling it as a region effect which is how I use it. I learned long ago to just split a small portion and never enable melodyne on a long clip.  It shouldn't be that way but I guess I have come to accept the work arounds. I also did the update on melodyne a few weeks ago and it did crash one a a very long clip and once when I was enabling it on many clips wiithout rendering (bouncing to clip).   
 
If it is re-producible on your system certainly make a bug report to cakewalk and also to melodyne.  I know there are LIVE and trackton crashes reported from melodyne so there is probably plenty of blame to go around.
 
Also I was freeze crazy for a while and I thought that was a great way to save system resources on these complex projects. I got away from it, as my workflow is too dynamic, I was unfreezing too often and nothing is ever "done" with me.
 
 

I've been able to reproduce this crash bug consistently on a completely new Platinum project.
1) start new blank project
2) add audio track
3) drag any wav file from browser to the track
4) create a melodyne region fx
5) save the project
6) freeze the melodyne region fx clip (it renders to audio clip correctly)
7) save the project - - - > instant crash, every time

dwardzala
What do you mean by "freeze"?  Are you bouncing the region to clip after working with it in Melodyne (also known as rendering)?

by freeze,  I mean I am clicking the freeze button which renders the clip to "flattened" audio
I like this because when you unfreeze the track you can begin editing in melodyne right away

papacucku
Because melodyne has always been buggy in sonar for me anyway, I always bounce to clip after correcting.  In the past if I leave two many melodyne clips "unrendered" I would get crashes.  Now that you bring this up, that really is not acceptable in this day and age, and many of the melodyne tutorials have you leaving the melodyne track, "melodyne enabled".
 
I got one crash after melodyne update when enabling it as a region effect which is how I use it. I learned long ago to just split a small portion and never enable melodyne on a long clip.  It shouldn't be that way but I guess I have come to accept the work arounds. I also did the update on melodyne a few weeks ago and it did crash one a a very long clip and once when I was enabling it on many clips wiithout rendering (bouncing to clip).   
 
If it is re-producible on your system certainly make a bug report to cakewalk and also to melodyne.  I know there are LIVE and trackton crashes reported from melodyne so there is probably plenty of blame to go around.
 
Also I was freeze crazy for a while and I thought that was a great way to save system resources on these complex projects. I got away from it, as my workflow is too dynamic, I was unfreezing too often and nothing is ever "done" with me.
 
 

I've also had occasional melodyne related crashing, hard to pin down the causes, but the good thing is I haven't lost much work or wasted editing time . . . but this is different. I simply can no longer freeze any tracks with melodyne content, something I have been able to do for years.
 
I have reported this through the automated Cakewalk problem report system, so we'll see if anything develops, I'm not holding my breath, since my past problem reports have gone into space and evaporated.

I would try to avoid freezing and bounce to clip as a work around.  How big is the clip that you are working with in Melodyne?

I use Melodyne very, very carefully.  Small clips, work on the clips one at a time and then render often.
 
There is no exact, repeatable set of steps that causes Sonar to crash (and hard crash...loses asio drivers and I have to restart computer, no crash log to Sonar and no attempted save of project) when using Melodyne.  I would describe the relationship on my DAW between melodyne and Sonar as very, very delicate and touchy.  
 
At least once a session it will crash.  Did not used to bother me much, but I an now working with others in my little home studio and it is super annoying.
 
JR

dwardzala
I would try to avoid freezing and bounce to clip as a work around.  How big is the clip that you are working with in Melodyne?

Hi Dave . . . bounce to clips is destructive. You lose the ability to easily re-think and tweak or even undo your melodyne edits . . . unless of course you pre clone all your melodyne tracks and archive / hide them . . . hence the creation of "freezing" tracks to avoid all that fuss. Freeze has always worked, now it doesn't, there must be a fix.
 
Yes, my practice has also been to use smaller clips. In a 4 minute song, I may split a clip to 4 or 5 clips before creating Region FX.

auto_da_fe
I use Melodyne very, very carefully.  Small clips, work on the clips one at a time and then render often.
 
There is no exact, repeatable set of steps that causes Sonar to crash (and hard crash...loses asio drivers and I have to restart computer, no crash log to Sonar and no attempted save of project) when using Melodyne.  I would describe the relationship on my DAW between melodyne and Sonar as very, very delicate and touchy.  
 
At least once a session it will crash.  Did not used to bother me much, but I an now working with others in my little home studio and it is super annoying.
 
JR

Both Melodyne and Sonar are some of my most amazing software . . . and nothing I have seen can do pitch / intonation correction nearly as efficiently as Melodyne . . . but it's true that Melodyne and Sonar don't always get along. By far, most of my Sonar crashes seem to mention Melodyne as the source, maybe I'm just pushing it too hard, or maybe it hasn't been perfected yet ?