[issues collection] Beware of using Melodyne now

First of all, i post this here, just to warn more people before they start job. (sadly i found it after all day tuning tons of vocals…)

Here what issues you will get if we using melodyne with Cubase 11:

  • GUI of cubase will slow down - more info here, later add video https://steinberg.net/forums/viewtopic.php?f=310&t=202982

  • After opening same session again, you will lose tuning of blob’s inside melodyne (actyally melodyne will warn you whe you open already tuned event in past session), I’m not sure why, i use Copy tuned event to other tracks & also track Versions, not sure what cause this problem.

  • disk space - (this is not Cubase issue, but better you guys know) i found melodyne temp/cache folder, and weigh was 20gb!

  • Melodyne hotkeys depends of keyboard layout - if you switch to other layout, you can hit a key (q for example) even if Focus is on Melodyne, after pressing Q Cubase will react (this happened only if not english keyboard layout activated. Russian ex.)

I’m not sure where should i post this issues.
I don’t have accont on Celemony forum, so if someone registered there, post this issues to quickly solve this issues

1 Like

Hi,

I’ve answered there …

Do you have some reproducible steps for us?

Nothing we can do … sorry.

Windows, Mac?

See you
Michael.

I can confirm that there is an issue related to copying parts with the melodyne extension on it - possibly related to removing the extension on copies of clips already containing melodyne data! And possibly also involving copies on multiple tracks. I tried combinations of the above, and made a brand new project corrupt in a matter of minutes, so it really shouldn’t be hard to find.

I’d love to give you an exact repro of the issue, but i’m currently i’m too busy re-tuning vocals :frowning:

… aaaand - it happend again!

I’ve been using nothing but ordinary operations on this project, and twice i’ve lost the entire tuning of a lead vocal due to “project corruption”. Melodyne and C11 is NOT ready for production work! As soon as i am done tuning vocals for the 3rd time, i’ll provide you with a repro of the issue!

I’m not sure what the qualifications for being a Cubase beta-tester might be, but it’s certainly not being an audio professional - and by that i mean someone who relies on Cubase and its (new) features for a living! Throughout my ~20 year experience with Cubase, i’ve found multiple unacceptable bugs in each and every single major release within 5 minutes of testing. And C11 seems to be business as usual …

For the love of god, please consider getting more qualified beta-testers, or better yet: implement a public beta program! Your current QA approach is costing me real money …

1 Like

What version of Windows or OSX are you using?

Melodyne 5.02
Windows 1909

I know this is not a real solution for the actual problem, but I just wanted to point out that with VariAudio, Cubase has a quite competent alternative to Melodyne built in. I’m not suggesting that the Melodyne problem should be overlooked, but it may be a workaround for you to get things done in the meantime.

Me too. Project with Melodyne extension. One day, won’t open. Cubase hangs “Loading MixConsole” on that track. Hours of work lost. The workaround is to uninstall Melodyne. :frowning:

Shouldn’t ARA2 temp files be stored with the project? At least as an option?

I think that’s a short sited downfall of ARA2 protocol at the moment. And also, there should be protocol connection to ‘remove unused media’ and Backup Project>‘remove unused media’ which would clean out ARA2 temp files from the project folder.

I just found this post but wanted to add my own experience with this to the conversation. Loss of data here too quite randomly but possibly either from a change of project name (save as) or track versions.

Here is my post elsewhere on the forum