Confirmed.
New project, one audio track, record 20 seconds of silence.
Region fx the middle 10 seconds as melodyne.
Freeze.
Save.
Crash.
 
Win7 64, Cakewalk/Edirol UA-25ex.
SPlat 2017/1, Melodyn 4.1

Tried in Studio One.
Didn't crash, but when I opened the project I couldn't get back to the unbounced version - could be I'm not smart enough, but the manual says double-click on the audio track brings it back. It didn't.

dwardzala
If I had to guess, it probably has to do with the undo tree in Melodyne not being resolved before saving.  When you save in Sonar you lose the ability to undo.  If you don't actually render the region you have the ability to undo, but when Sonar tries to save it probably crashes.
 
I'm going to guess that Studio One forces Melodyne to close the undo tree which is why you can't go back to the bounced clip.
 
I know people don't want to hear this, but you should render you region before saving.

Dave, you raise an interesting point, and that could well be the cause of the crashing.
I don't use Studio One, so can't test the theory, but it makes sense.
 
I have many Sonar projects where freezing Melodyne tracks worked just fine, but after the recent update to Melodyne 4.1, Sonar's freezing no longer works. Celemony has no rollback feature to find out if the last version has broken something, or not . . . so it seems we're waiting on Sonar + Celemony developer repairs, never knowing how important this issue is . . . in the queue ?
 
The workaround of simply rendering the Melodyne clips, well, it's just a workaround . . . and I want my freezing feature back working the way it was originally designed to work.

dwardzala
 
 I'm going to guess that Studio One forces Melodyne to close the undo tree which is why you can't go back to the bounced clip.
 

 
never mind . . .

ah what the hell (not that i'm here for studio one lessons . . . but . . . )
 
you can, and it is
 
transform to rendered audio, will do what freeze does, and removes the original and any vst/vsti's, then to get back you can either undo, (if you haven't made other changes you don't want to loose etc), or you can use 'transform to real time audio' to bring you back regardless of other changes or closing project or whatever, today tomorrow or next week, and you will be back to your original state, with melodyne available via the little black 'fx' box at the bottom of the track/wave form, simple really, and works perfectly, without the issue described here.

I've sent so many crash reports to Cakewalk without getting a single response. Maddening.

I've contacted Melodyne directly and they express a sad resignation that the problem is Cakewalk's and that unless Cakewalk steps in and fixes the integration problem, it's not going to get fixed.

Melodyne is aware of the problem. Their hands appear to be tied.

Here's what we know;
1.Creating a Region FX of Melodyne on even the smallest of clips will crash the project more often than not.
2.When it doesn't crash, the blob monitoring does not work at all.

What is the point of sending these crash reports to Cakewalk if there is not a response? Even if they have no clue about how to fix it yet; at least acknowledge that they SEE the problem and that, yes, it needs to be fixed.

Over the last few years, I feel Cakewalk has taken a defensive stance on support and has made users feel like the problems experienced are annoying, when reported, and not the fault of Cakewalk.

How about a workaround? Anyone have suggestions?

Interesting because I am still on v2 of Melodyne and I have not ever had a crash.  I render each clip when I am done with it though.
 
Just because Melodyne says it Cake's issue, doesn't really mean it is.

Can you provide a recipe to reproduce? I'm not sure if you're saying that freezing a Melodyne track causes a problem, or whether you're saying that if Melodyne tracks are frozen, then when you later save the project, it crashes.
 
I ask because I don't have any problems with Melodyne so I'm curious what the workflow differences are. If there is a problem and it can be isolated/repeatable, it can probably be fixed.

OK, I tried something different with Melodyne, Keep in mind I only have Melodyne Essentials 4.1.1.011 at the moment, but I am planning on upgrading to Melodyne Editor before July ends so I can take advantage of the great Melodyne upgrade sale at Everyplugin.com
 
When I used Melodyne as everyone else, Sonar Crashed.
 
Create new project,
Added an audio track of Vocals,.
Select Region FX > Melodyne> Created Region Fx
Selected the freeze button.
Attempted to Save
Sonar Platinum Crashed.
 
===========
 
I then tried using Melodyne a different way..
 
Create new project,
Added an audio track of Vocals.
Highlighted the vocals track
Inserted Melodyne from the FX bin as a plugin
Clicked the Transfer button in Melodyne  and began playing of the Vocals track
The vocals began rendering in Melodyne, this is done in real time so you may want to use a clip only.
Once vocals rendered in Melodyne, I froze the vocal track and then clicked save
Nothing happened, the Project was saved.
 
I was able to re-open the project and unfreeze the vocal track
 
It is by no means the fastest way, but you don't have to worry about crashing Sonar 

My posts are disappearing again!   I tried submitting it three times, after editing the original post, now it's gone.
If they should suddenly reappear, sorry for the duplicate posts.   These seems to be happening quite a lot lately for me.
(It was a post about Melodyne crashing for me under the same circumstances as the OP)

My workaround is to clone the track. Then archive one and bounce the other to clips.

Then I can go back to the archive track if I want to tweak melodyne.

Problem with this is clone track doesn't Clone track gain settings (another issue) so beware

IanPritchett
"I ask because I don't have any problems with Melodyne"

I find this very surprising. No problems with melodyne? It's always been flakey for me, but fairly usable until now.

Freeze a melodyne track and save =crash

I guess I don't have problems because I don't freeze. I work on a copy and render. If I need to redo something, I can either make additional changes to the copy, or if I want to start over from scratch, go back to the original. 

msorrels
Given how trivial this is to make happen they should be able to fix this.
 
Blank project.  Load wave file, make Melodyne region, freeze track, save. 
SONAR crashes, a few calls into Melodyne.
 
Call stack on the crash looks just like it did way back earlier in this thread.

Except that if it is an issue inside Melodyne, then Cake can't fix it.  Celemony has to.

Anderton

IanPritchett
"I ask because I don't have any problems with Melodyne"

I find this very surprising. No problems with melodyne? It's always been flakey for me, but fairly usable until now.

Freeze a melodyne track and save =crash

I guess I don't have problems because I don't freeze. I work on a copy and render. If I need to redo something, I can either make additional changes to the copy, or if I want to start over from scratch, go back to the original. 

I only tried to freeze out of necessity to make it work. I have a convoluted workaround but it is another aspect that calls to question the professionalism of splat... Is it pro for pros? Or....?
A question I face every other day in the studio when clients see stuff not working like it should