Not trying to hijack this thread but I feel this is related as to how Celemony treats its customers.

I've already gone round the block with them on the "libguide" crashing issue, which they fixed in 2.0 but refuse to do the same for 1.x. Now Cakewalk finds another problem (which celemony should have found) and I seriously doubt they will fix this for 1.x users either. They seem intent on forcing us to a paid upgrade in order to get functional software.

This is customer service at its worse:

A. customer buys software.
B. software is unusable because of bugs.
C. Customer asks vendor for help.
D. vendor denies it's their fault.
E. ANOTHER COMPANY confirms vendor bug and tells them about it.
F. vendor announces a fix is coming, but only for their latest upgrade.
G. vendor requires us to PAY for the fix by purchasing the upgrade.
H - CUSTOMER GOES ELSEWHERE FOR FUTURE PURCHASES.

Any news on a fix of this crashing issue with sonar x1?

Can I please get an answer on the progress of fixing incompatibility with sonar?

From crash dumps I sent to Cakewalk they found that there was a memory leak issue in Melodyne. They passed this information to Melodyne who are working on a fix. The update cycle isn't all that frequent with Melodyne so I'm assuming they'll roll the fix into an update along with any other issues/changes. I don't know when that might be but soon would be nice!

Hello guys,

Please understand that we won’t pin down any bug fix confirmations or release dates before the next version is ready to be released. But be sure that we are constantly working on updates and improvements.


Don’t know what you are used to, but last year, for example, we’ve had a few updates for Melodyne editor 1.x. Free updates, that is! Plus the 2.0 and 2.0.1 ones.

Claudio, the problem with SONAR was identified to Celemony over SEVEN months ago. In the meantime, Celemony has released a new version with the same major bug. I don't know if you guys fully realize this but right now Melodyne is pretty much unusable with SONAR. I have spent several hundred dollars on a product that I simply can not use with my primary DAW. So far I have not been able to use it successfully on a single project. I know many companies that have released quick, hotfix releases when their products have been identified as having serious showstopping bugs. In the above message you seem to imply that people are not being patient when I feel that we have been more than patient.

So far this experience with your product has been extremely disappointing. Quite frankly, I am starting to regret having bought Melodyne.

-e.B

In addition, the issue was there years ago, and it took another company which takes issues seriously and dig into it and find the reason and a solution suggestion to fix this bug, while celemony, reliable for faults, tries to negate that their product is faulty.

PLEASE do something about this - I'm getting the same problem here. I only work with small clips. I save my project after every edit. I close Melodyne and reopen it. I have tried every workaround - I am a patient person but this is the only plug-in that crashes my DAW. Surely, you can come up with a fix for Sonar owners - I love your product but it is fast becoming unusable.
PLEASE

I feel your pain but rest assured they will come up with a fix - 2 or 3 years from now - which will only be available in a PAID upgrade.

As a fellow sufferer, can I just say all will be well sooner than that I'm sure.
Patience mes braves!

I also want to re-state (being the OP) that I am still having these issues. I'm anxiously awaiting the promised bug fix.

Thank goodness I can't sing or I might be here more often but do I understand this correctly that X1 and Melodyne Editor is a total kill? I've been reluctant to upgrade to X1 but just did so last week and I'm getting the hang of it. The Screensets are what saved me!

Anyway, so I'm working my first project and to test something out, I added voice. But after the Transfer and when I go to Save, I get the Sonar "won't respond" error and it crashes too. Eventually, everything opened (plug-ins in display) the project does the same.

I only experimented with this a little but i did see where a smaller clip of a few seconds did behave. The worrisome thing for me is I thought this was just a glitch and it was my intention to do the $99 upgrade, but it sounds like because of this Melodyne and Sonar are no longer compatible?

Worse, reading this thread in its entirety, it sounds like Melodyne has a tin ear to Sonar X1 users. I do hope this situation can be resolved quickly and I'm withholding upgrading til this is acknowledged.

*edit: Using V-vocal til Melodyne addresses this issue.

...and another six weeks ticks by with no fix.

Maybe the person that updates the Twitter feed should start fixing bugs, since they appear to be the only person actually working at Melodyne from my perspective.

-e.B

Cmon guys! I need this fix ASAP. I've got projects waiting to be finished that need the Melodyne pass!

Hello.

The update is out now. Please see here.