Sonar X3 crashes with integrated Melodyne

Hello,
 
Lately, every time I use the Melodyne plug-in, it causes Sonar to crash when I try to open the session. I have used it on several sessions, and it causes this problem about 70% of the time.
 
I have the latest X3e patch installed, and I have tried re-installing Melodyne as well. I was able to open the session in "safe mode" and disable melodyne to continue working on the project, but after taking the time to transfer the audio back into melodyne and do pitch correction, it usually crashes again.
 
Has anyone else run into this? Any known ways to solve this issue?  
 
Thanks for any help in advance!

Most times these days, if Sonar crashes, it is when there is a 32-bit 3rd-party plugin in the project.
 
Is it possible this is the case here?
 
If not, please detail your system specs, audio interface, driver mode, as well as details on the characteristics of the project and the steps you are performing when the crashes occur.
 
Additionally, Sonar should produce a dump that can be sent to the support folks to help figure out what is happening.  (I think exploring the other above options may provide some quicker results, but you may also want to send in the dump),
 
Bob Bone
 

I see this is a bit of an older post, but I did a search after I experienced the exact same issue as described here. I appreciate knowing the edit and forget it advice as that's what I had to do to move forward with my (limited tracks) project.
 
My new question is, now that Sonar has moved to the subscription model, will anyone on previous versions of Sonar get any bug patches if we're not on the subscription program?
 
I just upgraded to X3 prior to the subscription model, and I would hope if and when a bug fix comes out for this Melodyne crash issue, I'll be entitled to that although I'm not on the monthly plan.
 
Thoughts?

mudgel

razor
I see this is a bit of an older post, but I did a search after I experienced the exact same issue as described here. I appreciate knowing the edit and forget it advice as that's what I had to do to move forward with my (limited tracks) project.
 
My new question is, now that Sonar has moved to the subscription model, will anyone on previous versions of Sonar get any bug patches if we're not on the subscription program?
 
I just upgraded to X3 prior to the subscription model, and I would hope if and when a bug fix comes out for this Melodyne crash issue, I'll be entitled to that although I'm not on the monthly plan.
 
Thoughts?

Whenever a new version is released there are no further fixes for the previous version. It's like that with all software I've ever owned. So the simple answer is no there won't be any more fixes for X3. They stopped with x3e. Sonar is not on a subscription model. In addition to an upfront purchase as with all software that you buy a non expiring licence for, Cakewalk have simply added the option to purchase the program on monthly payments.

I'm not aware that this Melodyne issue as you call it, is a bug. For the type of processing Melodyne does, it's just best to do the edit and bounce it. It's not really designed to keep active within a project, save in that state then reopen the project. Hope that helps.

Yeah, that makes sense bro. I guess I have to remember that I bought the upgrade to X3 right before Platinum, etc. came out and the X3 e patch was already out. Largely waiting later because CW offered a screaming deal on the price because the new versions were coming out.
 
On the main topic, when it crashed Sonar created a dmp file and asked if I wanted to submit it, which I did. Maybe if they do find a bug they can find a patch for new versions.
 
The only reason I think it may be a bug is because I have a fairly new high-end DAW and fine tune X3, which is also new. I did upgrade to Melodyne Editor v2, and I'm guessing it uses more resources then the version that was packaged with X3.
 
Anyway, I'm glad I know this about the best use of this awesome tool and I didn't lose anything at all.
 
Cheers
 
 
Stephen