Everyone stop using ARA right now

[midnightrambler]

This was literally fine at 11.30pm last night. And now it isn't. And LITERALLY the only thing that's changed between then and now is I managed to get some sleep.

So sick of this.

[midnightrambler]

I can't tell you how upset I am about this. It was sounding SO good last night. Feel like I should invoice AVID and Celemony for wasting my f'ing time.

[mr xy]

oooof. I feel your pain.

I've had a few minor disastors with ARA myself. I still use it now but my approach is to do the editing and then commit before I close the session, saving an unprocessed version in a playlist if I think there is any possibility I may want to revisit anything. Not ideal but it's certainly not to be trusted. It's great tech, I hope it works reliably one day.

[lesbrunn]

Originally Posted by mr xy

oooof. I feel your pain.

I've had a few minor disastors with ARA myself. I still use it now but my approach is to do the editing and then commit before I close the session, saving an unprocessed version in a playlist if I think there is any possibility I may want to revisit anything. Not ideal but it's certainly not to be trusted. It's great tech, I hope it works reliably one day.

+1 for saving unedited tracks and committing. My way around ARA issues is to:

1. Edit very short clips at a time (that way there are no stalls while ARA is saving. I don't even get the ARA saving message.)
2. Render Melodyne edits
3. Commit the rendered clips

Even after doing this I sometimes get those ARA error messages when I open a session, but there's no grief because the edits have been rendered. You can always revisit clips if you need to do more editing, or copy unedited clips for re-editing if you need to.

[TOM@METRO]

I'm another Melodyne user, but seldom with ARA.

[itsjustmeee123]

This same issue and message turned up on a Logic Pro session I was doing last night. All of my ARA info was lost on all of the tracks. So it’s probably a Melodyne problem and not Pro Tools.

[camshash]

This has been happening to me with every ARA melodyne edit, in every session. Extremely frustrating. Upon closing a session with ARA edits and opening it up again I get this notification.

M1 max Monterey 12.6.6 pro tools 2022.12

[wwittman]

Originally Posted by lesbrunn

+1 for saving unedited tracks and committing. My way around ARA issues is to:

1. Edit very short clips at a time (that way there are no stalls while ARA is saving. I don't even get the ARA saving message.)
2. Render Melodyne edits
3. Commit the rendered clips

Even after doing this I sometimes get those ARA error messages when I open a session, but there's no grief because the edits have been rendered. You can always revisit clips if you need to do more editing, or copy unedited clips for re-editing if you need to.

I admit I’m curious as to what committing does that having rendered melodyne hasn’t already.
Why do both?

[its2loud]

Originally Posted by wwittman

I admit I’m curious as to what committing does that having rendered melodyne hasn’t already.
Why do both?

Absolutely nothing. Committing is redundant to Rendering.

[Rich Breen]

Originally Posted by midnightrambler

This was literally fine at 11.30pm last night. And now it isn't. And LITERALLY the only thing that's changed between then and now is I managed to get some sleep.

So sick of this.

I had this error pop up once in the last few weeks on a melodyne-heavy project I was working on. Same as you; did a bunch of work on a track (reliable, trouble free external SSD), closed the session, opened it the next day, and that scary message popped up. Fortunately it seemed spurious as there was nothing lost that I could find, but it's *very* disconcerting. I wish Avid would give us some clue as to WTF is going on under the hood here and what conditions might possibly cause this.

The new workflow is great, but if we can't rely on it it's useless.