Pro Tools 2022.9 "Saving ARA Data"

[cmbourget]

Originally Posted by noiseboyuk

Sheesh.

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

As I mentioned above in the post-scriptum : 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.

[midnightrambler]

Seems like we collectively delete preferences so often it makes you wonder why Tools bothers saving any preferences at all.

[cmbourget]

Originally Posted by midnightrambler

Seems like we collectively delete preferences so often it makes you wonder why Tools bothers saving any preferences at all.

Indeed! These are daily preferences...

[Felix]

I appreciate knowing this problem is widespread and the wise obvious suggestion to go back to using the plugin format. This is frustrating in it's own ways, but way better than using the ARA mess.
This seems like a dark time for ProTools. The ARA thing and Apple silicon... I've had this understanding that they are absurdly slow(like last place in the DAW race) to adapt to important new advancements because they are making sure the changes are fully tested and stable. Solid integration for professional environments. I don't know what's going on now but all I know is ProTools has been having some serious issues lately with it's official releases. ARA was clearly not ready for prime time. And Silicon Apple... ? Maybe they're not focusing as much on Rosetta and more on the Native cpu version moving forward. I hope so.
Ideascale. Looks like that went away a while ago. The thing on Avid Link is nothing like it was. Oh well. I'll create a support ticket, ,,,

[Neale Eckstein]

Anyone updated to PT 2023.3 to see it fixed this issue?

[drumbreaker]

Yes. Issue persists. And now we have even bigger issues. Melodyne data creating in 2022.12 in some cases being lost or artifacted in 2023.3. Started another thread about that

[Neale Eckstein]

I love the old “not only did we not fix the problem….we made it even worse” school of programming.

[Caramiafreddie]

Hello, I have the same issue on protools 2023.3.
«*saving ARA data*» everytime.

[tonwurm]

Originally Posted by Caramiafreddie

Hello, I have the same issue on protools 2023.3.
«*saving ARA data*» everytime.

same here

now I´m avoiding to work with ARA Melodyne, instead instanciating the "old" Melodyne plugin

[Dizzi45Z]

So here is the thing. This issue needs to be resolved. I really really really hope that Avid does not think the "Saving Ara Data" lag is acceptable. It is a complete distraction to the workflow process.

Here's the thing. Why didn't the plugin version ever cause this to be an issue. I have Massive sessions with 20+ instances of the plugin that run very smooth and Pro Tools never has to freeze and I have never lost any Melodyne edits.

One thing I have been doing is working on keeping the ARA data as small as possible. This means that every time I use Melodyne, I only select the segment I am needing Melodyned and then rendering a new clip for that section (option-shift-3) and then activating Melodyne on that small section. This avoids Melodyne importing the audio for the whole clip. This typically works great until I finally hit the threshold of too much ARA data where now every time you edit any clip that has Melodyne Data in it, the session will have to freeze for 3 seconds randomly at the point that the session auto-saves.

What I don't get is that after you hit the threshold, any Melodyne edit of any kind is permanently a 3 second pause no matter what. I have gone through and rendered all of the Melodyne edits on the clips and turned off Melodyne everywhere. So at this point, the ARA data should be extremely small and not need a long ARA Save.

However, if I create a tiny clip to perform Melodyne on it and then hit save, it once again, takes 3 seconds to save. This doesn't logically make sense to me? Also...where is the ARA data being saved to that requires such a long pause?

On top of this, to have the new 2023.3 update automatically render Melodyne on everything on a track that is Tick based almost guarantees everyone using Tick based tracks to be stuck in the 3 seconds to save mode.

Please Avid! Don't leave us hanging with this. It really isn't acceptable to have these pauses. I understand that only requiring the save when something is edited with an ARA clip was an attempt to fix it. But a simple trim or fade added to any Melodyne'd clip requires another 3 second pause.

Please Please Please don't settle with the current solution.