Pro Tools 2022.9 "Saving ARA Data"

[Burbree]

Originally Posted by Diegokuuk

Same here. Even after deactivating all Melodyne instances, keeps saying "Saving ARA data"

I'm on Mac OS Mojave

Had the same thing, seems to happen when a track becomes more edit dense.

Also have observed that when commiting a comp which has many regions and fades (switching off Melodyne and selecting Commit) some edits dont commit in the correct place on the timeline. Consolidating the edit and then commiting that fixes this.

Bare in mind that even when you switch off the Melodyne on a track and commit, the ARA regions created will remain in the Clip list. (You can see they have a little waveform icon next to them) So a Cmd+Shift+U will select them once you've commited your tuning and a Cmd+Shift+B will clear them out of this version of the session. This stops the Saving ARA dialog.

[Ru_C]

Originally Posted by midnightrambler

The only thing is I really like being able to use the TCE trim tool and get 'Melodyne' stretching instead of standard Elastic, I think it might actually be my favourite thing about the whole implementation. When I first tried it I thought, "Well this is obviously never going to work", shortly followed by "Woaaaaaaaaah!"

That is interesting! Does it work on grouped drum tracks? I've always found Elastic Audio a bit iffy on cymbals/overheads. Is it possible to use the Melodyne algorithm across a dozen grouped/phase-locked drum tracks?

I would try it, but I'm holding off on updating until a get a couple of jobs finished.

[lesbrunn]

Originally Posted by orangepopsongs

I'm constantly getting workflow interruptions with "Saving ARA Data" window. I have only two tracks with Melodyne on and both are frozen. Am I wrong in thinking ARA should not be constantly updating in the background when the tracks it's on are frozen? The interruptions are making the function unusable. Anyone know how to minimize this?

I hadn't seen this at all till today, and the reason is that I'd been engaging ARA on very short clips at a time. I'm sure most people who get this are editing long clips, such as maybe a whole lead vocal track. I tried that today, and sure enough, I saw the ARA data message. The way around this is to engage ARA on very short clips at a time, like one vocal phrase or line at a time. You can cut your vocal into short clips and edit them one at a time. It can then all be consolidated after you are done editing. That way, Melodyne doesn't have to update the whole clip after every little edit. With short clips, the message doesn't show up at all (at least in my current workflow). I hope this helps.

[thin ice]

I'm wondering if it might be possible to have a "disengage ARA" option in preferences. It might be better to use the old ARA trick of freezing and unfreezing a track to run audio into Melodyne if this persists.

[PIANO2000]

Same issue here. I have committed all melodyned tracks and yet i keep getting this annoying message "saving ARA data". "ARA" means madness in my native language

Windows 10
Melodyne Studio
PT Studio

[trackone]

Originally Posted by thin ice

I'm wondering if it might be possible to have a "disengage ARA" option in preferences. It might be better to use the old ARA trick of freezing and unfreezing a track to run audio into Melodyne if this persists.

I believe if you use the Melodyne plugin on the track rather than the right click "Edit in Melodyne" it works as it always did.

[oscarpatxot]

Originally Posted by midnightrambler

The only thing is I really like being able to use the TCE trim tool and get 'Melodyne' stretching instead of standard Elastic, I think it might actually be my favourite thing about the whole implementation. When I first tried it I thought, "Well this is obviously never going to work", shortly followed by "Woaaaaaaaaah!"

wait wait wait, that is amazing, never thought to try that! That's the first Ill try when I get to the studio today.

[Daveporter33765]

Originally Posted by albee1952

Avid is aware of this issue and are working on a fix for the next release. Meanwhile, you are still free to use Melodyne as an insert like before(IOW, you are not forced into using the ARA version)

How in the world did a bug like this in a flagship, highly publicized, new feature get away from the developer quality control team and the beta testers?

This sounds like the kind of bug that should have easily been identified before the update was released.

[itsjustmeee123]

Originally Posted by Daveporter33765

How in the world did a bug like this in a flagship, highly publicized, new feature get away from the developer quality control team and the beta testers?

This sounds like the kind of bug that should have easily been identified before the update was released.

Maybe it’s not a bug. Could be that’s just the way Melodyne is baked into this version of ProTools. All I know is that it could’ve been implemented a lot smoother. As I’ve said in earlier comments on this thread, with Logic Pro the ARA is seamless.

[AINSLIE]

Originally Posted by itsjustmeee123

Maybe it’s not a bug. Could be that’s just the way Melodyne is baked into this version of ProTools. All I know is that it could’ve been implemented a lot smoother. As I’ve said in earlier comments on this thread, with Logic Pro the ARA is seamless.

Gotta be improved - I'm back to using the plugin. The saving ARA time suck makes it a non starter for any serious Melodyne editing.