I think the wandering time thing got fixed in the full update as well [Fix] Reworked TrueHD MAT packer to support high bitrate Atmos streams (fix audio dropouts) by thexai · Pull Request #20339 · xbmc/xbmc · GitHub
That is excellent news.
Any idea when it’ll make it into an OSMC update?
When the update is ready
Helpful
The answer is always the same, so what do you expect? There’s no firm ETA (there usually isn’t), but we’re working on it - as mentioned in this very thread before twice. Asking for an ETA won’t speed up the process
Or in other words: Questions about “when” are not helpful the other way either, for devs.
Yeah true I’m not sure why I bothered asking as it’s always the same old answer.
So what I hear you saying is that they are very consistent in answering a question that gets asked over and over and over again and that you were just expecting a different answer this time.
Yeah maybe one day we’ll get a different answer, like ‘nearly there’ or ‘we’ve hit some issues might be a few more weeks yet’ , perhaps ‘there’s been a lot of updates to Kodi and we’re working through them bear with us’ etc.
The blanket bugger off it’s ready when it’s ready isn’t very good PR.
I know OSMC runs on loads of devices and is essentially a free OS but for all those that own a Vero and paid would like a working device, the Atmos issue was always a Kodi problem but a fix has now been applied to Kodi and it would be good to have it officially pushed through to OSMC.
Just asking for a rough update, I’m not about to publish a wiki page on OSMC updates and the fact the dev team fell behind on their expected release date that they gave etc.
Like you say it’s a question that pops up numerous times so there is a demand for this kind of info in some format.
As much as an answer to this question to the affect of “in 2 days, if nothing goes wrong” might be nice, it wouldn’t be helpful for anyone really. The team is really small, so a small hickup can cause delays and giving changing ETAs is not only frustrating to users, giving ETAs and explaining delays in detail also takes time that can be spent on actually working on issues and implemeting features…
It’s highly frustrating and time consuming to reply to questions like “Why isn’t there an ETA this time?” quite often although users familiar with our forum and our work will know that the reply isn’t gonna change and that we’re working as quickly and as thoroughly as possible. The results should speak for themselves - updates are being provided and features are being added.
So, long story short: From a user perspective, staying informed is nice, we know, but would you like to trade that for issues actually being fixed quickly and features being implemented?
You can already get the update from the staging repository. Atmos fixed is included.
But we want more testing before we release anything as a stable update.
Nothing stops you installing Kodi v19.3 on your device today.
I don’t recall giving any release date whatsoever for the next update.
it will happen soon, however.
To test this update:
- Login via the command line
- Run the following command to add the staging repository:
echo 'deb http://apt.osmc.tv buster-devel main' | sudo tee /etc/apt/sources.list.d/osmc-devel.list
- Run the following commands to update:
sudo apt-get update && sudo apt-get dist-upgrade && reboot
- Your system should have have received the update.
Please see if the issue is resolved.
I also recommend you remove /etc/apt/sources.list.d/osmc-devel.list
after updating. This will return you to the normal update channel. To remove the file:
sudo rm /etc/apt/sources.list.d/osmc-devel.list
Got family staying at the weekend but might give this a try, never really keen on ‘beta’ but needs must and it might help test.
Hi Sam,
Gave the fix a try with Shang-Chi and it’s a definite improvement but there are still frequent micro drops in the sound - not as prolonged as before though.
I agree. I’ve still had micro drops, too. In Disney’s Luca, for example. I guess this issue is not 100% resolved.
The cause of the micro drops could well be something else. The main problem addressed here was, at first, kodi crashes, then when that was fixed, long drops (maybe a second) at the same locations.
Are they in repeatable locations? Are you able to snip out a clip at one of those locations for others to test?
I was able to repeat the issue in Moana toward the end (pretty much right before the end credits after a flawless viewing till then - repeatable in the same spot after rewinding), but after quitting the movie and restarting it and zipping to the same spot, - the issue didn’t repeat at the same spot. in Luca it borked 2 or 3 times in the first 10 minutes. I’ve been watching a LOT of high-bitrate UHD movies this week, and only these Disney Atmos movies have proved troublesome. Mind you, this is still greatly improved over what it was, but there’s still work to do, it appears.
That’s what people say. They must be pushing the limits of the specification, maybe even exceeding the limits but since we can’t see the spec without signing up with Dolby, can’t be sure.
Debug logs with the problem title and timestamp at which these glitches occur would be useful.
Please verify that users are using properly ripped discs with accurate demuxed TrueHD streams, for example with MakeMKV versions of at least 1.15.4 which uses mlp
Good point. The consequence of not using that demuxer probably depends on the device decoding the audio (AVR). Could be a pop, could be a gap if the AVR detects a pop and blanks it.