![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#11
|
||||
|
||||
![]()
I've never seen this happen on any of our rigs, ranging from 12.8.3 to 2019.6, macos 10.12.6.
Though we hardly use the channel strip, maybe just a few tracks but most are still eq7 (old habits) and a LOT of clip eq these days. |
#12
|
|||
|
|||
![]()
Yeah, it's the first time I've seen these in such an extreme way. First time ever was during an Atmos theatrical mix 2 years ago but that was a very complex setup with multiple rigs and an RMU. And back then we thought it was HDX related and we saw them in connection with the red RMU TCP errors that sometimes happen.
Then it re-surfaced this summer on a much simpler 5.1 project and everyone incl. the mix is on HDn. It's definitely an automation related thing as it only happens in certain sequences of a sessions and can be "fixed" by wiping out automation breakpoints in the area where it happens but it doesn't really cure it once it's in there. No connection to video playback at all over here.
__________________
PTHDnPCIe 2024.10.2 (OSX14.7.2), 8x8x8, MacPro 14,8, Decklink SDI 4k, SYNC HD, Nanosyncs HD, 64GB RAM, Xilica Neutrino, Meyersound Acheron |
#13
|
||||
|
||||
![]()
I run into this (Automation Too Dense) when I am on an Atmos Mix that is fairly busy. The template I am running is from way back that has been updated and tweeked over the years. Now that I am reading this I am going to build a new Atmos template from scratch but using the same layout and see if it does the trick.
It's very obvious on Super Sessions so let's see if this solves my issues. BTW I am running 2019.5.0
__________________
Marti D. Humphrey CAS aka dr.sound www.thedubstage.com IMDB http://www.imdb.com/name/nm0401937/ Like everything in life, there are no guarantees just opportunities. |
#14
|
|||
|
|||
![]()
Automation too dense messages are fairly normal to have (let’s say a couple of times over the course of a mix) with bigger PT sessions (I’d say over about 320 voices). The solution is often to move a sudden Automation change (levels/EQ/reverbs/etc) of tracks so that not everything changes at the same time over lots of track.
The errors -20021 I’ve never seen. I don’t use Channelstrip however (FabfilterQ3 is my go to these days). Greetings, Thierry
__________________
http://www.a-sound.com/ |
#15
|
||||
|
||||
![]()
I also don't use channel strip. There are times where no major automation change is happening and I still get "automation too dense" notifications.
Let me replicate it and do some more investigating.
__________________
Marti D. Humphrey CAS aka dr.sound www.thedubstage.com IMDB http://www.imdb.com/name/nm0401937/ Like everything in life, there are no guarantees just opportunities. |
#16
|
|||
|
|||
![]()
I was doing a playback for clients yesterday and we had 3 of these in the course of a 90 min film.
25 mins in automation too dense then -20021 and timeline won't play - restart PT. Pretty embarrassing. It was after 20 to 25 mins of constant play each time, although I do get them when not constantly playing also, but less often. I might try playing back again today and see if it happens at the same spots. Or is it something that's building up over time like a memory leak or some such?
__________________
M2 Ultra Mac Studio, OSX 14.5, HD-Native TB, Trinnov DMon, MTRX Studio, Sync HD, AJA Ttap, Avid Dock, Avid S1, PT Control, Soundflow, PT 2024.10.2 |
#17
|
|||
|
|||
![]() Quote:
Meanwhile my support case has been closed and won't re-open (to busy to start the conversation from scratch) so if anyone has one open about this forward them the info. Maybe it helps. Frank.
__________________
PTHDnPCIe 2024.10.2 (OSX14.7.2), 8x8x8, MacPro 14,8, Decklink SDI 4k, SYNC HD, Nanosyncs HD, 64GB RAM, Xilica Neutrino, Meyersound Acheron |
#18
|
|||
|
|||
![]()
Bring back nice memories, Frank, thanks!
![]() |
#19
|
|||
|
|||
![]()
Ha! Probably Markos playing tricks on us.
__________________
PTHDnPCIe 2024.10.2 (OSX14.7.2), 8x8x8, MacPro 14,8, Decklink SDI 4k, SYNC HD, Nanosyncs HD, 64GB RAM, Xilica Neutrino, Meyersound Acheron |
#20
|
|||
|
|||
![]()
I did some pretty intense testing on this today.
It played through the film once with no errors and on the second playthrough the error occurred about 50 mins in. It was a section of about 5 mins that wouldn't play without the error. If I went to the beginning of the film it was fine, end was fine just this one area gave the dreaded 20021. Frank's fix worked if you overwrote all automation, but not ideal. I tried various other things and discovered that at least on my session, if I disabled and then re-enabled all my individual DX tracks (not the buses) it cleared the problem. Can someone else try and see if that works on your sessions and then maybe we can narrow it down to what type of automation causes it?
__________________
M2 Ultra Mac Studio, OSX 14.5, HD-Native TB, Trinnov DMon, MTRX Studio, Sync HD, AJA Ttap, Avid Dock, Avid S1, PT Control, Soundflow, PT 2024.10.2 |
![]() |
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 |