Error -20021

[marianna]

Originally Posted by Leverson

I’ve been seeing this too for the first time, the ‘automation too dense’ message followed by that error code, on OS Ventura and PT Ultimate 2024.10.0. As far as I can tell it seems totally random. Quitting Pro Tools and re-opening seems to fix it for a while. I’ve thinned automation but it doesn’t seem to actually be related to dense automation as far as I can tell (my session isn’t particularly dense or heavy). Again as far as I can tell it just comes up randomly and intermittently. I am using track and routing folders in the session if that makes a difference.

2024.10.2 is to resolve that Leverson........

2024.10.2 - Fixed an issue that was introduced in 2024.10.0 which caused an increase in AAE -2200x errors when playing video with a Pro Tools | Sync X / HD attached (PT-333639)

“Playback could not be started. This may happen due to a CPU issue, a problematic driver, a slower hard drive, or because playback was started immediately after an engine change. You may also try to increase the Play Start Latency setting in Preferences.”

UPGRADE!

Marianna

[Leverson]

Fantastic, glad there is a fix for it! Didn’t realize there was a new 2024.10.2 that was just released. Cheers!

[Frank Kruse]

Originally Posted by marianna

2024.10.2 is to resolve that Leverson........

2024.10.2 - Fixed an issue that was introduced in 2024.10.0 which caused an increase in AAE -2200x errors when playing video with a Pro Tools | Sync X / HD attached (PT-333639)

“Playback could not be started. This may happen due to a CPU issue, a problematic driver, a slower hard drive, or because playback was started immediately after an engine change. You may also try to increase the Play Start Latency setting in Preferences.”

UPGRADE!

Marianna

Marianna,

I'm slightly confused now. The fix reads like it's only for the "2200x" errors and only for SYNC HD users. This thread is about the 20021 error that has been bugging us for about 7 years.
Ironically on my rig I have been getting 22003, 22005 and 006 errors since the 24.10.2 update that I had never seen before.

Can you confirm that 24.10.2 update was only for the single digit 2200x-type errors and not the 200xx errors? I know a lot of users who have been getting both and don't even use a SYNC HD or any avid hardware for that matter.

Thanks!

[barden]

Marianna,

Like Frank I, too, am concerned there may be some confusion here with respect to the error codes we are reporting.

The “automation too dense” errors (solved temporarily only by closing and reopening the session) are -20021 errors, not -220xx.

I am on HD Native and not HDX and I don’t have a Sync interface installed.

[resonatee]

yep, still getting those with 2024.10.2

The only solution is to restart pro tools and open the session again. works for a while....sometimes a very short while, might downgrade for that very reason.

[Benny Mouthon]

And it's back....got this in late summer and now -20021 is here again.

Running Ultimate 2024.10.2, Mac Studio 14.7.2, 1h45m stereo show (PBS, don't ask..), nothing too crazy going on.

[DominikS]

Same thing here. Impossible to work with that version even with a fairly simple session. Went back to 2024.3.1 and it's fine. Still a pity to lose all the newer features...

[Fulwave]

We have also had to roll back all of our systems to 2024.3.1.

Multiple stages with multiple computers and S6 consoles all reporting lots of errors.

Hopefully next release will address these issues.

[bad jitter]

Yes, this silly error can happen even in places where there is no audio or automation at all.

Originally Posted by Leverson

I’ve thinned automation but it doesn’t seem to actually be related to dense automation as far as I can tell (my session isn’t particularly dense or heavy).

[tope d]

To those experiencing this issue,
What happens if you suspend all automation? Does the problem still occur?
Please update this thread after trying the following steps:

1. Rename the Pro Tools Preferences and delete the databases
See the KB Article for detailed instructions:
https://avidtech.my.salesforce-sites...ocedure%20will

Preferences
- Go to folder ~/Library/Preferences/Avid/Pro Tools
- From the Finder, click on the Go menu in the menu bar.
- Select Go to Folder. (shortcut “Shift + Command + G”)
- Type in the following: ~/Library/Preferences/Avid and click Go.
- Rename the 'Pro Tools' folder > xPro Tools


Pro Tools Workspace database files

Try deleting these if you experience file-based issues, such as problems searching for audio files in the Workspace.
- Go to folder /Users/Shared/Pro Tools
- From the Finder, click on the Go menu in the menu bar.
- Select Go to Folder.
- Type in the following: /Users/Shared/Pro Tools and click Go.
- Delete the Pro Tools folder, which contains the following three files:
- Workspace.wksp
- WaveCache.wfm
- MiscSettings
Note: Deleting the workspace file will also delete any user-created catalogs.

2. Launch Pro Tool and create a new session without a template
3. Import your recent session, use the "Import Session Data" (link to source media)
4. Select all the clips, then go to Pro Tools edit > Automation > Thin all
5. Test it and see if the issue occurs.

If the same issue occurs, please create a support case at https://www.avid.com/pro-tools/learn-and-support (bottom of the page), then let me kno the case number on this thread so I can jump on it ASAP.

Thank you