• SONAR
  • Melodyne Essential 4 Crashing Sonar Platinum (p.15)
2016/07/29 21:54:27
bitman

They are not responding to us. I think we deserve more backing from Cakewalk on this than what you wrote above. Assuming they'll address it in their next update isn't very proactive considering you guys used Melodyn as a huge incentive for your customers/prospects to upgrade or move to Sonar.
 

Easy up just a little on Cake here. When they integrated ARA Melodyne was ver 2, and worked.
So we were wooed to something that worked at least.
Celemony "broke" it if you will, with their version 4.
 
 
 
2016/07/29 22:11:03
Blades
But it has been several months with an update that renders the feature completely useless.  It's not loke something about it doesn't work or whatever - the entire program crashes if you use the feature (taking your newly create material with it), so the end result is that you can't use it at all.  Unfortunately, for many of us, this was one of the reasons we spent the time and money to update our programs from X3 to Platinum and all of the things that go with it.
 
I understand that Cakewalk doesn't make this plugin/integration directly, but my clients don't really care that I don't make Joomla! - they only care that their websites don't crash.  If they do, they expect me to find a way to fix them or at least put them back to functional while I await some other developer to correct the issues they are having.  This is the function that I see that Cakewalk at least SHOULD have control of - the CCC should be able to determine that an integration is on a version that is known to cause issues and offer to fix the problem by back-leveling the integrated application and keeping that installation up to date as long as there is a problem - again, it's not that this isn't a known situation for several months.
 
I think Cakewalk should be more on top of this.  I mean, the last update we have from Cakewalk was from Noel 6 weeks ago that Celemony has identified a fix and is releasing an update soon...and here we are.
2016/07/29 23:03:06
bitman
I don't think Cake has anymore leverage here than they did with UA when UA updated their software broke Sonar in some instances and ways one used the UAD plugs. Eventually Cake had to concede that this was the way it would be as apparently UA would not cooperate with Cake on the issues. My memory if foggy as this was years ago though.
 
Here again we are dealing with a very prideful company in Celemony who split the atom with DNA.
They have also decided a user forum is not good for business - that's very disturbing as Celemony has little reason to be paranoid.
 
Let's hope it's better this time around.
2016/07/30 08:04:15
Bajan Blue
I have Melodyne Studio latest update (4.04 I think)
Until the latest update I could not use melodyne at all inside Sonar. With the latest update I can use it as an FX via the FX bin, but cannot use it as a Region FX - soon as I try to create a FX region, Sonar crashes. Also if I do manage to get it to work via FX bin route  but forget to mix down and delete, when I go to open the project next time, Sonar will not open - I have to open in safe and not load Melodyne.
I have been waiting for the next Sonar update to see if that improves things before starting to try and deal with Melodyne, which i don't think I will enjoy much.
Nigel
2016/07/30 08:09:31
ZincTrumpet
I have now also raised a support ticket with Celemony. The response so far has not been particularly helpful always turning it back on me to provide a crash dump etc.
 
They haven't acknowledged that there is a problem with Melodyne although I have directed them to this thread and others here showing the extent of the issue.
 
If I use Melodyne either within Sonar or standalone it crashes before too long; even doing basic stuff. I have lost quite a bit of work and now always do a backup before opening Melodyne. I am on Melodyne Essential v4.04.004 btw. 
2016/07/30 09:25:38
Bajan Blue
Hi Susie_temp
Basically for me Melodyne only just works via FX bin, cannot use at all in any other way - it is so unstable I try not to use it and have considered dumping it totally and going back to something like Autotune - however the integration with Sonar is the ONLY thing keeping me with Melodyne at the moment (even though it now does not work!!), so while it seems clear this is a Melodyne issue, I do believe Cakewalk should be doing more  -ie how about threatening to drop melodyne as it does not work and causes major issues! I would imagine Cakewalk's parent Company is quite a bit larger than Melodyne and should have a BIG stcik somewhere they can shake at zee Germans...........
Nigel
 
2016/07/30 14:15:51
Bajan Blue
OK an Update - just updated Sonar to 22.7 build 41 - I had already loaded latest Melodyne update 4.04 - started a new project, insert 1 piece of audio - tried to creatRegion FX - instant crash 
I do think Cakewalk need to give us some help here as Region FX is a Sonar function - the fact that Melodyne is not working, well still a Cakewalk issue I hate to say, much as I am on Cakewaks side - the thought of trying to sort this out with Melodyne alone is not one to look forward to
Nigel
2016/07/30 15:45:31
Sheds
When I emailed Melodyne last month about t his they responded that they did not know of this as a problem.
 
" . . .it is not a known issue for version 4.0.4.004 to be crashing often." 
 
So, I am confused.
2016/07/31 11:16:05
Bajan Blue
This is a known issue and we have reported several crash dumps to Celemony. They have acknowledged that it is an issue on their end.
 
See Post 109 - emm as I said dealing with Melodyne will not be easy nor pleasant I fear!! Version 4.0.4.004 has made no difference for me. I have firstly logged it as a fault with Cakewalk as the main issue is trying to use Melodyne as a Region FX - instant crash
Nigel
 
2016/07/31 13:42:03
mettelus
Ironic (or outright sad) feedback here... Melodyne's update deal was through April 30 IIRC, and after sending several emails back and forth to them during my trial, it all ended at version 4.0.4.004 (which was less buggy but still "not right"). I am rather shocked that not a single update has occurred in the 3+ months since?
 
Ultimately I backed out of the "deal" as it fell into both the "too good to be true" category, and the company had "gone dark" (i.e. customer support vanished). I am finding that the "going dark" tends to be the best litmus test on whether to do business with a company or not these days.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account