Studio Pro crashing on ARA

[gabo]

I have a very large file, from a live show so it's 14 tracks of audio that's over 2 hours long. I spent 4 or 5 hours working on tracks in Melodyne, all worked ok. I finished my session, saved the file and closed Studio Pro without a problem.

Now today, I can't open the file. It gets to "loading melodyne" and goes to about 48 percent, then jumps to 96 percent, then just crashes. When I opened it again, I can choose options to disable. If I disable ARA, then it opens fine, but of course I don't have all my melodyne edits.

If I then go back and open it with ARA enabled, it crashes again.

Is there a way to start ARA after you've loaded the file? I also tried removing the cache folder (copied it to another location), but that didn't do anything.

Is there any way around this? Of course I can start over, I have a backup of the original files, or I can probably save it again with ARA off and recover it from there. But I will lose about 5 hours of work!! Very frustrating, it's a long and complex file with lots of tedious work already done on it, to start over gives me major heartburn.

 

[Stuart Welwood]

What happens if you try to edit one of the tracks with Melodyne with ARA turned off? Is that even an option?

 

[gabo]

What happens if you try to edit one of the tracks with Melodyne with ARA turned off? Is that even an option?

No, it acts like melodyne is not installed. And of course that wouldn't help anyway as I would still lose all my edits. But an interesting question..

I haven't tried, but I assume that once it's opened without ARA I can save it to another folder or even save it to the same folder, then reopen it with ARA turned on and then edit it.

That would actually be better than starting from the backup as I did do other things as well with some plugins, eq, levels, etc... So better than nothing, but the vast majority of the time was spent editing with melodyne.


UPDATE: I saved it to a new folder and was able to open it with ARA enabled. And melodyne was still installed on the tracks it was on before, but I lost all my edits and it also analyzed the tracks with the default algorithm. So just like you put melodyne on the tracks fresh. I still have the old folder if anyone has a magical way to get that to open and salvage my edits. Otherwise, I'll do all the edits again and this time I'll bounce the tracks before I save/close. Which sucks because if I have further editing to do I'll have to add melodyne again and re-analyze the track and bounce again. Not a great solution, but workable.

 

[gabo]

Got through this song, but it was a tedious task. Just in case someone else has this issue, here's what I had to do to get through it.

- Try to open the file, it would crash.

- Upon reopening, it would prompt to disable things or start normally. I would disable ARA support and open.

- The file would open, then I would save it. No edits, just save it.

- Reopen the file normally with everything enabled.

- It would open, all the instances of melodyne would be on the tracks, but none of the edits would be there. It would immediately start analyzing those tracks using the default algorithm, which in my case is the melodic algo.

- Since this was a live performance, it had many songs. I would select all the tracks and cut the first song before the start and after the finish. Then I would do all my melodyne edits for that one song.

- After I finished all the edits on that song, I would bounce each of the events that had melodyne edits on them so the edits were "baked in" to the audio for that one song.

- Then I would save the file. But once I did that and tried to reopen the file, it would crash. But disabling ARA, saving, then reopening, the bounced audio would be there and it would start analyzing the rest of the tracks with melodyne on them.

- So I would go through the above procedure again, cut all the tracks for the next song, do my edits for that song, bounce the song events, save the file, exit. And again upon reopening it would crash, I would reopen without ARA, save, reopen with ARA, cut next song, do melodyne edits, bounce events, save..

- rinse and repeat until I had all the songs done.

I don't know what is causing this, maybe a bug in melodyne or in ARA that only affects very large/long files. I've used studio pro for single songs and used melodyne without any issues.

I should have opened a ticket, but I didn't have time for that and the artist wouldn't have let me share the full tracks anyway. So there wasn't going to be a way to send something to show the problem. Maybe after all this is done, I'll try to record something very long and see if it happens, if it does I can open a ticket.