![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#41
|
|||
|
|||
![]()
Just came to say hello that after 20 years I had my first 20021 today.
Macbook M1 with HDX in a Sonnet chassis and Pro Tools 2024.6.0 with no video engine active. |
#42
|
||||
|
||||
![]()
Getting this too after going to 2024.10, never had this before and it's on a simple 5.1 52 min. session w/ DNXhd video
here's that conversation in the main PT thread: https://duc.avid.com/showthread.php?t=429774 Rolled back to 2024.6 and everything is fine again.. An AVID moderator in the other thread said it was plugins, but they're all up to date so..?? Only thing that changed was updating PT..go figure Last edited by Benny Mouthon; 10-30-2024 at 08:27 AM. |
#43
|
|||
|
|||
![]()
I just found this thread. I am getting automation too dense, followed by Error -20021 many times daily. No ChannelStrip here. Before those, I often get Audio processing deadline was not met errors. That error also says, "This may have been caused by the following plugin: Fabfilter Pro-Q3."
I'm not sure if I got these errors before updating to 2024.10. My session is a 5.1 TV series mix with six episodes and 32 GB audio in the timeline, all cached. I sent the errors to Fabfilter support, and they responded that Pro-DS could be the issue and advised turning lookahead off. But that didn't help. My session is indeed from a template updated over the years. |
#44
|
|||
|
|||
![]()
I had Automation too dense errors and 9173 related to FF plugins.
The template we used had to be remade from scratch. |
#45
|
|||
|
|||
![]() Quote:
I hope the new Pro-Q4 will fix this. |
#46
|
|||
|
|||
![]()
I got this error the other day WITHOUT an "Automation too dense" warning. No Fabfilter plugins in the entire session. There was a Channelstrip on the track but I'm not sure it even had any automation on it except for the initial write. I was adjusting panning for one short section and got the error. I could not playback until I closed the session and reopened. And it didn't come back
![]() Any known cause for it besides automation too dense?
__________________
~Will |
#47
|
|||
|
|||
![]()
I haven't had -20021 for quite a while. When I ran PT 2024.6 on my Mac Studio M1 Ultra, everything worked super smoothly.
Then I upgraded to 2024.10.1 and now I get 9179 followed by -20021 A LOT. I also switched from Ventura to Sonoma, don't know if the OS update could have an impact. My colleague though has the same configuration on a Mac Pro M2 Ultra and doesn't seem to have any of these issues. Does anyone know what 9179 and 20021 are all about? I don't understand why AVID doesn't just list ALL AAE errors with explanations. Cheers |
#48
|
|||
|
|||
![]()
hi, I've been having this same error for a week and a half. It coincides with the upgrade to 2024.10.1. I'm in contact with Avid and it seems to be a random error. I suspect it must be something related to importing old sessions. I've solved it these days by deactivating and activating track groups. I'm still testing but there is a coincidence with some track group. As soon as I have more information I will share it
Regards |
#49
|
|||
|
|||
![]()
Have a look for another thread about this topic to which I replied and suggested that automation too dense errors *might* have something to do with folders being open. I was plagued with them for several days but could predictably prevent them by closing a folder in my session.
~sb Sent from my iPhone using Tapatalk
__________________
PT2024.10 EuControl 2024.10 macOS Ventura 13.4.1 Mac Studio M1 Ultra 128GB RAM HD Native / HD OMNI / Dock / S1 www.imdb.com/name/nm0002486 |
#50
|
|||
|
|||
![]()
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.
|
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
AAE - 20021 was encountered? | Cheesehead | Post - Surround - Video | 7 | 11-07-2020 12:51 PM |
AAE Error -20021 | DonaldM | Pro Tools 12 | 5 | 09-07-2017 08:01 PM |
Pro Tools 9 Playback Error Lead to DAE Error 743 Which Lead to A CPU Overload Error | EricMulhern | macOS | 1 | 11-20-2011 06:39 PM |
Error type 10,address error ,illegal error, buss error ,illegal instruction | KasticK | Pro Tools TDM Systems (Mac) | 3 | 05-14-2003 12:21 PM |
Buss error,Address error,ilegal instruction,error type 10 | KasticK | Pro Tools TDM Systems (Mac) | 1 | 02-08-2003 06:49 PM |