Melodyne is constantly crashing. Sometimes Editor crashes all of Sonar, other times the GUI interface in Editor just goes all crazy, and becomes unusable. I have to constantly reload my sonar project from scratch to fix this.

It doesn't matter whether its a new project with just one wav file, or a whole project full of tracks and other plugins. It happens the same way in both Sonar 8.5 and X1. (both fully updated and running 64bit) Editor is version 1.2 running in 64bit.

Melodyne Editor crashes at least every 5 minutes, but sometimes in as little as 1-2 minutes. This makes using the program just a giant waste of time.

With all the bugs and issues, and original lack of 64 bit, you guys really need to find a new programmer that actually knows what the heck he's doing.

Seriously... fix this shit.


(Edit: The crashes seem to be related to the audio engine. If a disable the audio engine when editing, Melodyne doesn't seem to crash. It also only crashes WHEN I'm actually editing. ie. Physically moving a notes pitch or timing, etc, within Editor.)

Just noticed some more problems.

When mixing down, I'm getting these spots where all of a sudden the tracks volume jumps up really quick for a fraction of a second, then jumps back down. They are spread throughout the edited piece. I did not do this myself, I never edited any volumes at all. I only moved the timing and pitch.

When I play the track just inside Sonar, there aren't any of these, but if I 'bounce it to a track' or mixdown the whole project these strange blips appear.

If I delete the Melodyne editor from the project, (obviously my track is reverted to the previous state) and there are no longer any problems.

I have verified this with other tracks in other projects too.

Hello Plink,

is your audio buffer size set to 1,024 samples? If not, please try if this makes a difference.

My audio buffer is set to 32. I do this to run with an ultra-fast latency of 0.7 ms.

Why would the buffer need to be 1024? Is Melodyne not able to run any faster?

(I'll try this out and let you know how it goes)

Plink,

this is a basic misunderstanding. You only need a low latency when you are recording tracks and all your monitoring goes through your system as opposed to some outboard equipment, for example. But once all tracking is done, every computer system will benefit from a large buffer size, since it will release CPU stress. The processing of DNA in particular takes a lot of CPU load, and if your CPU can't handle it, your system might crash easily, if your audio buffer size is too low. So, it's not about speed and latency, it's about processing power.

I'm having the same issue with Assistant 1.2. I haven't been able to figure out the exact steps to replicate the issue 100% yet, but I will pay closer attention in hopes that Celemony can isolate the issue. I have my ASIO buffer at 4096 and I'm running 32-bit Sonar 8.5 Studio with 4 GB RAM and a 2.0 GHz Pentium Dual Core CPU on Vista Home SP2 32-bit. I sent an email to support.

Yes, I have the same issue in Sonar X1. I've posted on a different thread under "Working (not working?) With Melodyne":
viewtopic.php?f=10&t=7658
but still Melodyne have not offered any clues, let alone a solution. I get the impression that they regard their software as pretty well perfect and that the DAW software is always the problem. But there's enough evidence ** I feel to indicate an issue with the way Melodyne interacts with Sonar and with all due respect to Celemony I would have thought it worth their while to at least look into this a little further. I've already seen a posting on the Sonar forum where someone checked in to ask whether it was ok to buy Melodyne yet to use with Sonar X1 and after the responses to his request I think he decided not to do so.

** The OP here bears out my findings that the freezing/crashing is time-related, i.e. it doesn't matter what samples, buffers, and other variables you experiment with, crashing happens afer about five minutes of actually working with blobs and so on.

Hello Skyline,

sorry, I am not too familiar with Sonar myself, so I have no clue what the problem might be in your case, but I will gladly forward your other thread to our support team. Meanwhile, rest assured that we look into any issue that our users report. Also, we are in close contact with Cakewalk and other DAW manufacturers to work on any possible incompatibility issues, so upcoming updates (theirs or ours) might bring a solution.

Hello Skyline,

I just confirmed that shorter transfers under X1/64 work right through here (Win 7/i7 Quad CPU).
A 3:30 min polyphonic transfer passed testing, while a 13 minute transfer with two instances didn't. I agree that there might be a time or (RAM) related issue we or Cakewalk need to get into.
For now, I strongly recommend to:
a. transfer only sections that need correction, transfer section by section, save inbetween
b. avoid long transfer like whole tracks
c. do not transfer to multiple instances

Best, Ulf

Thanks Ulf.
I've been doing (a) for the time being.
I look forward to any progress you can make with the CW team.

John

Gentlemen,

FYI, I have the same problem with ProTools LE 8.0.5 on a similar Windows 7 computer.

Kevin Stratton

Hello Kevin,

welcome to the forum. This thread is about Sonar, not Pro Tools. Your issue might or might not be the same. May I therefore ask you to open a new thread and give us more details? See also this thread first.

Is there any progress on finding why Editor freezes, and Sonar with it, after two or three minutes as a Plugin? Sonar X1c patch has made no difference so I don't think it's an issue with Sonar. I've also upgraded my Sandy Bridge high-power DAW to 14GB of memory and that made no difference either.

Has Melodyne Editor got a problem with its Intel AVX implementations by any chance? Sonar had a problem with this after they were introduced in Windows 7 SP1 - they caused problems only if you had a Sandy Bridge processor - like me! Cakewalk fixed this major issue in X1c, but I was wondering if Melodyne Editor has also somehow fallen foul of the AVX protocols (whatever they are) in its own programming.

At the moment Editor has been a complete waste of money for me and it is simply not fit for purpose. The Plugin version that I had before gave sterling service for years - but now I'm jiggered. If there is no solution soon, then sorry I will be wanting my money back please.

John

PS: There's a highly-detailed paper here on Intel's site detailing Sonar's use of AVX. I don't know if it could be of use to the Editor programmers in case it provides any clues:
http://software.intel.com/en-us/articles/utilizing-intel-avx-with-cakewalk-sonar-x1/

Are the Celemony folks on holiday?

Hello Skyline,
there will be no immediate fix but we need to take a look at the issue certainly. As a workaround please use shorter transfers only for the sections that need correction or the stand-alone version with export from Sonar - see above. I can't say anything about the AVX protocol.