Pro Tools 2022.9 "Saving ARA Data"

[cmbourget]

I've just found a way to get rid of the (crazy and cumbersome) save function including the Melodyne (ARA) files. However, it's through the render function. But instead of rendering each clip or a set of clips, you remove the Melodyne track from the Plug-in Elastic Audio menu in the track header (renamed Plug-in Elastic Audio or ARA). At this point, a message appears informing you that all the ARA clips will be rendered (I hope you understand my English translated from French). Then, the saving is instantaneous. Phew!

[cmbourget]

Originally Posted by cmbourget

I've just found a way to get rid of the (crazy and cumbersome) save function including the Melodyne (ARA) files. However, it's through the render function. But instead of rendering each clip or a set of clips, you remove the Melodyne track from the Plug-in Elastic Audio menu in the track header (renamed Plug-in Elastic Audio or ARA). At this point, a message appears informing you that all the ARA clips will be rendered (I hope you understand my English translated from French). Then, the saving is instantaneous. Phew!

See image..

[Franklyn]

Originally Posted by cmbourget

See image..

Yes that's fine, but you lost the editing page.

Is the 3 seconds save process (with active melodyde mode) any better in ProTools 2022.12?

[cmbourget]

Originally Posted by Franklyn

Yes that's fine, but you lost the editing page.

Is the 3 seconds save process (with active melodyde mode) any better in ProTools 2022.12?

This is what I explain VS a situation where you have finished editing, because ARA keeps everything in memory (and saves it) even if you have rendered everything manually.

No, I don't see why 2022.12 would be better, nothing is announced in that sense (unfortunately).

[Vadym]

Originally Posted by cmbourget

But instead of rendering each clip or a set of clips, you remove the Melodyne track from the Plug-in Elastic Audio menu in the track header (renamed Plug-in Elastic Audio or ARA). At this point, a message appears informing you that all the ARA clips will be rendered

Another option here is to use the Track header context menu. Mouse right click -> Melodyne -> Render will render all ARA clips on the selected track(s) while Melodyne plug-in will stay in place for the track.

[Vadym]

Originally Posted by cmbourget

I've just found a way to get rid of the (crazy and cumbersome) save function including the Melodyne (ARA) files. However, it's through the render function.

Not ideal since you will lose the possibility to edit the rendered clip.

There are two tips to decrease the annoying "Save ARA..." appearance.
1. Consolidate exact clip you going to edit with Melodyne if it was trimmed from a bigger original clip. Especially if it is 2hr record or so. Because Melodyne analyse all original file, not the trimmed clip only (for you to be able to trim out and crossfade), this results in tons of ARA data and slow saving. The less unneeded ARA data you have, the shorter Save ARA nag you will see (or won't see at all if its less than 3 sec)
2. With no new ARA edits only the very first next back-up or manual session Save will happen with "Save ARA..." nag, while all the next will use super fast cache of the previous ARA saving data. But just you made any new ARA edit(s), Pro Tools needs to reCreate and reSave in slow way the whole ARA data you have in the session (not the changes only, unfortunately).

Take it into account and I hope it will help you to reduce the annoying "Save ARA... " nags.

[cmbourget]

Originally Posted by Vadym

Another option here is to use the Track header context menu. Mouse right click -> Melodyne -> Render will render all ARA clips on the selected track(s) while Melodyne plug-in will stay in place for the track.

Yes, thank you.

Originally Posted by Vadym

Not ideal since you will lose the possibility to edit the rendered clip.

There are two tips to decrease the annoying "Save ARA..." appearance.
1. Consolidate exact clip you going to edit with Melodyne if it was trimmed from a bigger original clip. Especially if it is 2hr record or so. Because Melodyne analyse all original file, not the trimmed clip only (for you to be able to trim out and crossfade), this results in tons of ARA data and slow saving. The less unneeded ARA data you have, the shorter Save ARA nag you will see (or won't see at all if its less than 3 sec)
2. With no new ARA edits only the very first next back-up or manual session Save will happen with "Save ARA..." nag, while all the next will use super fast cache of the previous ARA saving data. But just you made any new ARA edit(s), Pro Tools needs to reCreate and reSave in slow way the whole ARA data you have in the session (not the changes only, unfortunately).

Take it into account and I hope it will help you to reduce the annoying "Save ARA... " nags.

What you're explaining is precisely what I do (it's a logical path that we take right away). I consolidate the (short) clip before Melodyne and then render it. But it doesn't really work here and that's why I described the problem. ARA keeps saving a mountain of data. Even with a full render, ARA goes back to being long after a few new clips are processed, but Pro Tools sessions take even longer to save, breaking the workflow considerably.

+ the other problems, that's a lot.

See here:

https://duc.avid.com/showthread.php?t=421889


P.S. Next: I deleted the Pro Tools preferences, as it is often advised, and it's been better since. We'll see with use, but there's a big difference.

Translated with www.DeepL.com/Translator (free version)

[noiseboyuk]

Has this issue really not been addressed in 2022.12?

[cmbourget]

Originally Posted by noiseboyuk

Has this issue really not been addressed in 2022.12?

No, zero.

[noiseboyuk]

Originally Posted by cmbourget

No, zero.

Sheesh.

This very much falls into the “easy for me to say” category, but it seems crazy this hasn’t been fixed by now.