I agree... its pretty concerning really ! how can a flagship unit be left with a flaw like this ... a processor thats not processing properly ? how are you experiencing this StephenB on any particular tracks and any sort of work around for you ?This seriously annoying "thing" has been around Q3 of 2019 with no fix. Given that it is now some 18 months later and we still have this "thing", I doubt Dolby is working on a fix or if they are, a fix is even possible. I hope I am wrong.