If you remove the atmos metadata does the soundtrack play ok?
I’ve not tried that. Currently, for convenience sake (family around), I just have to use the lossy DD 5.1 tracks and that sound quality really blows by comparison. Otherwise it’s digging out the discs and using either the Oppo or Xbox. And I hate discs!
Sometimes I think it’s Disney doing it on purpose to annoy us.
I haven’t tried it either but based on the above info I would assume it would as it’s basically TrueHD at that point.
I’ve only noticed this issue on one movie (Frozen 2), never noticed it on other Disney UHD releases
So many others, too. The Incredibles (on the bridge with the dad and multiple sticky bombs), latest Pirates movie near the beginning etc.
Missing audio on most of the Pirates movies would be an improvement 
1 Like
We all can’t… Nobody here can influence the fixing process and we’re also experiencing the issue at hand. So, that’s life. We have to be patient. The Kodi dev is working on this as we can see in the issue referenced here. What else can we expect?
Only the dev quoted above will probably be able to answer that one.
The Atmos part is not the problem, it’s the TrueHD MAT frame that’s too big. Removing the metadata doesn’t make a difference. A team member has tested this already.
If i read this correctly Dolby say the maximum peak rate is 18000?
https://developer.dolby.com/blog/dolby-audio-over-hdmi-part-1-codecs/
Exactly. The problem is that is being exceeded momentarily when a complex sound is being sent (loud bangs, eg). There is no provision in the publicly available specs for that to happen.
It doesn’t go above 18000kbps. The Atmos dropouts happen at approximately 11Mbit.
We are talking here about very short-term peaks in data. The actual bitrate can’t physically exceed 18Mb/s or thereabouts so one MAT frame overflows into the next one when there’s lots of data to be sent. The rules for how that happens are opaque. It’s not permitted under IEC61937-9.
Really not sure I understand. The issue in question is not that it exceeds 18Mbit. It doesn’t come close to that.
Are you measuring the bitrate every 1/50 sec? If not, you don’t know what the peak bitrate is.
1 Like
No I’m not. But I doubt the bitrate is jumping over 50% “invisibly” to support your thesis. And nothing I’ve read suggests this is the issue. These dropouts can last many, many seconds and it’s always in the ~11Mbit range that I can see. But I’d be happy to be proven wrong.
the issue is that the current implimentation in ffmpeg/kodi maxes out at 10Mbit
The FFMpeg implementation is not yet used at all.
Checking back after a long time. I know it is not fixed yet but is there any war to help? I cannot help from a technical Point of view but maybe it is possible to send a pizza and a few cans of Redbull somewhere;-)
That’s appreciated. For now we just need to wait I believe.
Sam
1 Like
I see a reply to this thread and I’m like OMG MAYBE TODAY IS THE DAY.
Boo.
Next time…next time…
2 Likes
Better check over at the Kodi git repo. This issue has to be fixed on the Kodi side. https://github.com/xbmc/xbmc/issues/16704#issuecomment-627293432
Im sure that if the osmc devs would know how to fix this it would already be fixed