Dolby Digital metadata tagging incorrect...again

[SoupDragon57]

This issue was previous resolved (back on the BT Community Forum around late 2023/early 2024 - content now archived), which @DarrenDev helped resolve. However, it has come back with a vengeance 😢

BBC channels seem to be correctly tagging their Dolby Digital metadata to reflect the sound being supplied, e.g. DD+ 2.0 when stereo sound is being transmitted or DD+ 5.1 when full 5.1 audio is being transmitted. However, EVERY other HD channel is now incorrectly showing DD+ 5.1 regardless of the content. This impacts soundbars and AV Receivers when trying to process the sound. This is important if they are trying to up mix the sound to 5.1 or 5.1.2 as the metadata is not matching the content, leading to a much less impressive surround landscape.

I don't know why this has apparently gone wrong again but perhaps someone doesn't understand how the DD metadata is supposed to be used. It absolutely should reflect what the content provided really is, not the maximum possible that might be delivered.

Can we get this corrected again, please?

[DarrenDev]

Sorry to hear that.  Can you please confirm you're seeing this issue on a TV Box Pro? I'll get someone to investigate ASAP.

[DarrenDev]

The encoding team believe they have found the issue, and will test a fix next week.

[SoupDragon57]

It is indeed the BT TV Pro box.

[SoupDragon57]

@DarrenDev  - any update on the fix being rolled out?

[DarrenDev]

Yes, but unfortunately not the answer I'd hoped for. 

The fault was introduced following a forced upgrade on the encoders quite a while ago - no one had noticed until you raised it. When the fault was eventually fixed, this setting wasn't re-enabled.

Whilst it has been confirmed that turning the setting back on does fix the issue in our test environment, we're not currently allowed to turn it on in production. The environment is locked down, as it's in the process of being migrated to a new service. 

This work is due to be complete in the 1st quarter of 2026 - i.e. before April. The setting will be enabled as part of that work, so you'll see channels fixed one by one in the new year.

Sorry I couldn't provide a better answer.

[SoupDragon57]

Thanks for the update @DarrenDev . Not the greatest news timeline-wise, but at least it will get fixed.
Sounds like there's an extra test required in the regression test pack! Hopefully, it won't sneak back again 🤞