Sonar Platinum and Melodyne Studio 4.1 - CRASHFEST

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.
 
 

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

BRuys

noynekker
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

Seems to me you have a bona fide bug here that you should report to Cakewalk.  Who knows, it may be the key to unlocking the intermittent bugs other people get in Melodyne.  Bottom line, this should work without a crash and as a customer, you should expect it to be fixed.  But you gotta help the bakers out by reporting it along with your recipe so they can investigate.  Reporting it here on this forum is good, but not enough to get it fixed.
 
Have a look in the Problem Reports forum.  Noel has instructions on how to capture a crash dump.  If you were to submit your recipe along with a crash dump, I'm sure we'd be well on our way to having this bug fixed.
Good luck!

chuckebaby
I would also send in a dump file.
Cant say I have ever frozen a Melodyne clip myself. I used to use the freeze track option to free up resources when I had a less than stellar CPU but just out of curiosity, why freeze it anyway ?
 
Sorry to hear about your problems.

chuckebaby
Melodyne has been very stable here. I haven't had a crash with Melodyne since last year and I use it on every project just about.
 
- I only use it as a Region FX.
- I DO bounce to clips after I make my edits (Render it) Because think about it...Why would I want to go back to the original clip ? If I am using region FX this means the original was not worth saving anyway. However if it ever got that bad, I have a back up just like everyone else in the Projects Audio folder. So bouncing to clips might be destructive, but the original is still there (unless of course you are using the "Clean audio folder tool" after saving your project).
 
- I don't over use Melodyne because I don't think that's what it was ever intended for. (but that's only my opinion).
I use it sparingly to fix guitar mistakes, Vocal errors and anything else that might need a quick fix.
if something is so bad  that I would find myself using Melodyne on more than 50% of the track, I'd rather Re-record it .
 
I also use Vocal synch and drum replacer. those 3 region FX are my best tools for house cleaning.
this is typically the first step I take in the mix down process.
 
My whole planning set up (though not really related to anyone's comment on this thread) is:
I never use Melodyne to be something I am not. So with this, I have been fortunate to have success with Melodyne.
What im trying to say is, I work in sections and render as I go. As I said earlier, if the clip is bad enough that I need to use Melodyne, then it wasn't worth saving to begin with. However like any good producer, I get ADHD and try to fix more than I should. but with being said, still been lucky and had no problems, no crashes.
 
To those who do have crashes, im sorry for your issues. Try rendering as you go though and see if that makes a difference.
Remember you still have a back up in your Projects Audio folder if you labeled your tracks correctly.

The Grim

msorrels
 
Here's the call stack on this easy to reproduce bug (just followed the steps above).  While it's possible it's a SONAR problem, the call stack makes me suspect it's more a Melodyne problem and thus the odds of it being fixed soon are very low.
 

while it may be a melodyne problem, it also may not be, in studio one if you do the same with it's 'track freeze' equivalent 'transform to rendered audio' there are no issues, i know less than nothing when it comes to programing and how this stuff works, but one could be forgiven for thinking if x plugin was inherently broken, had an issue, it would be in all hosts, perhaps not but . . . . one of the reasons i think studio ones ara and melodyne integration is superior, far less issues and quirks than you get with sonar when dealing with melodyne.