Is Melodyne buggy for anyone else? I’m on Mac Tahoe with an M4 and when you try to adjust blobs, they sound weird and distorted, or just don’t make noise. Sometimes it’s clear, sometimes it’s not there at all. It seems to be intermittent and happen randomly. Has anyone else experienced this?
Further, does Melodyne make performance slow? I keep getting beach balls say every 5 minutes ish for a few seconds or so. Does this have anything to do with meloldyne? I tuned a vocal, but the vocal is split up into events to remove noise inbetween, not one solid file. I’d love to hear thoughts!
Bigger session, but not much processing going on at all. It seems like it started happening when/after I tuned the vocal.
I’m on Windows 11 and Cubase Pro 15, but I also used Melodyne on Windows 10 (and on a much slower computer than I have now) in the past, and I haven’t had any significant problems.
It is true that, sometimes when moving blobs they may temporarily make a distorted sound or no sound, though I think it depends on what specifically is being adjusted and “luck of the draw” on when you’re doing it.
One thing that can definitely affect responsiveness in Melodyne (or any ARA editor, and also some other areas, though there are some special considerations in the ARA world) is if you happen to be doing something when Cubase’s AutoSave function kicks in. In particular, depending on the size of your project (check the CPR file size), sometimes the interruption can take a while. I especially found this using Synchro Arts RePitch with the option that stored the cache in the Cubase project itself, thus multiplying the size of the CPR project significantly and taking orders of magnitude longer to do the AutoSave. Is it possible you have your AutoSave frequency set to every 5 minutes? If so, maybe that explains the “beach balls”.
I would strongly suggest not doing a whole bunch of small fragments – .e.g. after doing my fade edits for vocal comps, I tend to bounce the results into song sections (i.e. verse, chorus, etc.), rather just phrase lengths where there is no silence included. Then I’ll work on the entire lead vocal (so maybe 6-10 clips in a typical song) in one pass, then do all the background vocals (just the song sections that have them, so typically a smaller number than in the lead vocal, but also a minimum of 4 tracks for doubled two-part BGVs, and possibly a fair number more for more harmony parts) in a second pass.
I also bounce the results once I’m finished, rather than leaving Melodyne active. I don’t think Melodyne stores its cache in the CPR project – certainly not by default but I don’t know if there may be a settings option – so it really shouldn’t affect the CPR file size significantly having it live. But perhaps more instances (due to lots more clips) might add somewhat?
Got ya! I’ll check the session size and see what’s happening. I know the session is quite large, but it just had me wondering why a brand new Macbook Pro M4 is reminding me of my 2013 intel Mac Trashcan. Perhaps (I pray) there’s a reason for that which can be easily remedied.
EDIT: So, I just checked, and the session folder is 14.75GB. Not all that large. I’ll check the save intervals, but I don’t remember it behaving this way with the same save intervals. Any ideas?
EDIT: Also, it looks like my autosave intervals are every 5 minutes and a maximum of 100 autosaves. Is this a lot/excessive and would be causing these beach balls?
Got ya! How big is your session? Does Melodyne save all of the files in the Cubase project folder with your song? I feel like that’s the best idea since it keeps everything contained. My session is large, but barely any processing on it and my new Macbook Pro M4 is reminding me of my 2013 Intel Mac Trashcan, which is not ideal.
You said “session folder” on the 14.75 GB. It is CPR file size that might be relevant here on the autosave. If you meant the CPR file by that 14.75 GB, that would seem to me to be pretty darn big. For example, my current project’s CPR file is about 35 MB. The last three I finished were 15 MB, 11 MB, and 28 MB. The current one will likely be smaller by the time I archive it (the other project sizes are after archival) as I tend to keep a lot of backup stuff in my active projects, only cleaning it in the archival process once the project is finished and I’m confident the old stuff (e.g. raw, pre-comping takes) will not be needed.
The 100 autosaves seems a bit excessive to me (mine is set at 10), but that may depend on your likelihood of having problems and needing to recover from those files. I’ve only used them a few times over the years I’ve used Cubase. However, the number of files isn’t likely to be terribly relevant – it is the size of those files that is relevant to the time taken to do the autosave. FWIW, my current project folder, which includes all the audio files, frozen audio, permanent extension audio, etc., plus loads of backup CPR files for various milestones of the project) is 11.4 GB (I work at 96 kHz, so that may make it bigger than some would have for a similar number of audio files and backups).
As for the frequency, mine seems to be set to 15 minutes, though the actual autosaves are quite a bit less frequent, probably because I save frequently, especially any time I have a milestone, then I go out to Windows File Manager and make a backup copy of the CPR file with a meaningful name (e.g. “ProjectName, tracked LdVocs.cpr”).
its 36 tracks and plenty of plugins. How many Melodyne do you have open? I found that the best practice is to bounce all the clips into 1 on your track and then I add Melodyne from the top of the sequencer window. For me it looks like cubase opens a bunch of version of ARA plugins if not - that is not good for performance and seems to put alot of strain on your hard drive. Maybe it is different operations if you add ARA from the left side in the inspector view? atleast I know what works for me and after I started to edit my vocals and bounce to 1 clip, then start to tune I never have problems with any ARA plugins. so maybe since your project takes a long time to save it could be a solution that you run a lot of Melodyne ARA versions at once ??
I think the time taken to do an autosave should be the same as for doing a manual save – it is essentially saving the same file, just in a different location and with a different extension. So it would not be surprising if you see a several seconds delay every 5 minutes is that is the frequency you have set for the autosave. The only difference is, when you manually save, you expect it to take a little while and you’re at a breaking point, whereas, when the autosave kicks in, you might be (probably will be) in the middle of something else – like working in Melodyne in this case – so there’s more likely to be a noticeable side effect.
The only other thing I can think of that might make a difference here is the type of disk the project is being saved to. For example, a hard disk will take more time to save to than a modern NVME SSD.
Thanks for the reply! The strange thing is that autosave can take 3-4 seconds and a manual save can take like 5-6 or so, but, I can manually save over and over right after each other, and it will be the same outcome; that it takes 5-6 seconds or so to save.
Bumping up