I add melodyne extension and do what i need to. Usually bounce once i’m done (make extension permanent havent never worked for me, unstable).
In case i missclick inside of melodyne ctrl + z OR forget to bounce and move the event which have’s melodyne on following happens: Melodyne shows no data and event doesnt play audio even it shows data. I can remove extension, but once i’m trying to add melodyne to same event, same problem.
Sometimes when things get really messy, i hear melodyne playing audio even without event.
Only fix for above have been by going to back up project and start over. Very time consuming which grown man doesn’t have.
Guys who coming to scream ‘‘use variaudio’’, don’t bother. I have been using melodyne since 2015 with multiple daws without issue. It’s so bread and butter for me so i’m not willing to walk back on hours what i have been into just if poughkeepsie doesn’t work. Cubase is only place we’re it feels risky to use specially on later state on mixing/production specially on projects we’re i get paid for.
So have anyone been facing this issue or simply feel like melodyne inside cubase can be risky to use?
You don’t mention your platform (i.e. Windows/Mac), but I use Melodyne Studio quite a bit, currently in Windows 11 with Cubase 15.0.10 on an Intel Core Ultra 9 285k PC with 64 GB of RAM (but previously, at Cubase 14 and earlier, on an i7 5280K PC with Windows 10 and 16 GB RAM), and I have not had any significant issues.
One thing I’ll note on your Ctrl-Z comment, is Cubase does sometimes make it challenging to be sure your focus is on the Window you think it is on. In that context, I have seen some issues where I’ve hit Ctrl-Z in an ARA extension (I don’t recall if it was Melodyne – I also use other ARA extensions, including having used Synchro Arts RePitch for tuning a little bit in the past), where the Undo ended up being for having added the ARA extension, probably because I’d clicked in the Cubase project window at the wrong time. I don’t recall if a Redo got back to the context I’d had before the Undo or just put me at the starting point of adding the extension. That context issue has also affected me in other areas that don’t involve ARA editor windows, with the most frequent one being hitting “G” or “H”, thinking I’m zooming out or in on the project window but having it narrow or widen the MixConsole strips (after having pressed a button on that screen, which is always up on my second monitor).
I’ve mostly bounced Melodyne results, typically after tuning a section of a song in a vocal. However, a couple days ago I was doing polyphonic tuning on three guitar parts in parallel for a long time, using Melodyne at the track level (I usually use it at the clip level), and I did just use the make extension permanent at the same track level, with no issues in the results.
no big problems for me on win or mac. I do not understand how “make extension” could be unstable. either. it prints the melodyne or it don´t? works everytime for me. when I work with ARA I like to bounce the track into 1 part and not apply it to a bunch of edits, I find that is easier to keep track of. I could see the ctrl-z not always work they way you think, I just stopped using that shortcut when editing. Sometimes using that shortcut melodyne would just be removed so I think I have the same issues as the other poster that your focus would be shifted sometimes when you think it is not.
2 and 3 I have all the time. I have found that fiddling around with moving the events on track around on the time line kind of forces Melodyne or cubase(whichever gets confused) to refresh the state of the audio and get it back in sync.
Another related issues…If you start playing right before a track has any event on a multi track view, sometimes that track will just stop playing. move the playback head forward to where there is an event, then flip it back to where you want to start actual playback.
Also, use smaller chunks of audio events, because melodyne gui slows waaaay down if they get too long and try to zoom in and out.
Make sure musical mode is off on any tracks/event and not using elasetique(use cubase algos) before you slap melodyne on.