I just had to uninstall Melodyne 5 assistant 5.3.1.0018 so I could record. Every time I would try to punch in to record a new version I got the audio dropout error. Melodyn 5 was shown as an extension, and was greyed out with no way to get rid of it. I checked the old track version, and melodyne was on it, not greyed out, with still no way to turn it off. Any ideas? so I can use melodyne again.
1 Like
Im on mac, and in my case cubase 12 crashes when I make a four bar loop, punch in the recording and pressing stop after I recorded for the full loop. I tried, different versions of melodyne, didn’t help. Im on a Mac M1 running in rosetta mode on monterey 12.5.1 … Maybe its the same issue only on mac it doesnt show me the message when it crashes. It would be nice if this could be resolves quickly since I use melodyne in every project…
Hi @comsax1,
Melodyne 5 is currently at version 5.3.1.018.
Perhaps the issue might disappear after having upgraded to this latest version?
Also, complete de-installation of the current installation (faulty, due to possible version mismatch within saved project data?) might be better than just updating Melodyne on top of its (considerably) older version.
No guarantee that this’ll resolve your issue, but this is what I’d do.
- Reference (Celemony website, help category Melodyne 5 assistant, stand-alone):
→ Version history
Cheers,
Markus
.
.
[-Screenshot-] (Windows Pro 10 22H2, Melodyne 5.3.1, stand-alone / ARA in Cubase Pro 12.0.70)
Thanks, the original post was wrong I edited it , and I do have the latest version of Melodyne 5. I uninstalled melodyne and re installed the Yamaha usb driver, and cubase will record now. I will wait until I finish tracking and then try re-installing melodyne. Again Thanks for the reply
1 Like
Hi @comsax1,
thanks for the additional information, also for the solution mark, and I’m glad you can record again.
I do hope that you’ll still be able to record after re-installing Melodyne.
Sometimes it can be next to impossible to really find an underlying software error. So reinstalling relevant components, restarting the PC, etc. often tend to resolve randomly appearing issues better than to endlessly search for “the error” (which can get quite frustrating and is sometimes futile).
Best wishes,
Markus