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 SPlat Jamaica Plain and Sonar X3 Producer.
Crashes in both.

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.

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.

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.

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

never mind . . .

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

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.

noynekker

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.

I could actually test this as I never updated to Melodyne 4.1 - I still have 2.0 Editor.  I will try to test this later this week.