![]() Reinstalled Melodyne from the Celemony site and within CCC, and all is fine now! So the moral of the story.render before you close. So I removed the regions on the clips and saved as a different project (to be safe). I'm going to assume that rendering regions (bouncing) prior to closing out the project is the safest way to do things and will prevent this from happening again. Turns out there were 4 vocal clips that had un-rendered melodyne regions. After that I was able to finally open my project. ![]() Maybe I need to go through Celemony to get this fixed? ~Jeff EDIT (Solved): Melodyne was definitely the problem. Is there a new Melodyne editor update somewhere that I'm missing? I'm at a complete loss here, and cannot open this specific song. I did the Windows update a couple weeks ago and the latest Platinum update. I even tried deleting the actual audio files I thought had Melodyne on them, to no avail. All projects without Melodyne open and operate fine. But as soon as I try to create the Region FX, I get the same crash as noted above. So I then tried opening Melodyne on an audio test track in another project. I tried opening in Safe Mode also, but still get the same Melodyne error and the song won't even open in Safe Mode. It tries, but at the last second, I'm getting a Melodyne error, fault reporter, etc. Melodyne crashing Sonar Yesterday while trying to open a project I've opened without issue in the past, will not now open.
0 Comments
Leave a Reply. |