2019-12-05, 15:29
Hint: https://github.com/fritsch/xbmc/commit/a...7be5d34789 - I will check if I can use a different Android API to get this specific value out there. Sadly amazon themselves tell to use a "private API" - I hope for the best.
(2019-12-05, 15:28)fritsch Wrote:Does the stereo audio delay bug happen in Amazon's own VOD offerings or just Kodi? There's plenty of Amazon content with a stereo track. If so, there may still be hope.(2019-12-05, 04:00)Kodroid Wrote:(2019-11-27, 07:58)wizziwig Wrote: Is there some way to automate that delay so it only applies to stereo and not other files? I only noticed it on stereo aac so far.Looks like we will just have to wait for the firmware fix, it if ever happens.
Yes. That's what I did in those firetv builds. But as this is a "special device hack", I won't push that into Kodi. Why device hacks are evil we currently see with the amlogic clibber workaround code, that breaks modern Cube, which is also amlogic driven, which btw. shows again: Chip vendor has the standard conform code, box sellers sadly have no interest at all to fix their firmware ...
(2019-12-05, 15:29)fritsch Wrote: Hint: https://github.com/fritsch/xbmc/commit/a...7be5d34789 - I will check if I can use a different Android API to get this specific value out there. Sadly amazon themselves tell to use a "private API" - I hope for the best.Has anybody tried contacting the Product Manager for FireTV about this issue? He's very chatty on reddit and Twitter.
(2019-12-05, 18:10)Kodroid Wrote:Try it, but don't feel sad afterwards :-)(2019-12-05, 15:29)fritsch Wrote: Hint: https://github.com/fritsch/xbmc/commit/a...7be5d34789 - I will check if I can use a different Android API to get this specific value out there. Sadly amazon themselves tell to use a "private API" - I hope for the best.Has anybody tried contacting the Product Manager for FireTV about this issue? He's very chatty on reddit and Twitter.
https://old.reddit.com/user/esaba
https://twitter.com/Elias
esaba.com
(2019-12-05, 18:05)Kodroid Wrote:(2019-12-05, 15:28)fritsch Wrote:Does the stereo audio delay bug happen in Amazon's own VOD offerings or just Kodi? There's plenty of Amazon content with a stereo track. If so, there may still be hope.(2019-12-05, 04:00)Kodroid Wrote: Looks like we will just have to wait for the firmware fix, it if ever happens.
Yes. That's what I did in those firetv builds. But as this is a "special device hack", I won't push that into Kodi. Why device hacks are evil we currently see with the amlogic clibber workaround code, that breaks modern Cube, which is also amlogic driven, which btw. shows again: Chip vendor has the standard conform code, box sellers sadly have no interest at all to fix their firmware ...
(2019-12-05, 21:02)fritsch Wrote:<Off topic>(2019-12-05, 18:10)Kodroid Wrote:Try it, but don't feel sad afterwards :-)(2019-12-05, 15:29)fritsch Wrote: Hint: https://github.com/fritsch/xbmc/commit/a...7be5d34789 - I will check if I can use a different Android API to get this specific value out there. Sadly amazon themselves tell to use a "private API" - I hope for the best.Has anybody tried contacting the Product Manager for FireTV about this issue? He's very chatty on reddit and Twitter.
https://old.reddit.com/user/esaba
https://twitter.com/Elias
esaba.com
You could ask something like: What's the standard Android method to query AudioTrack in order to find out the processing delay of their internal stereo to dd encoder? And why they did not expose it via the normal AudioTrack delay API.
(2019-12-05, 15:29)fritsch Wrote: Hint: https://github.com/fritsch/xbmc/commit/a...7be5d34789 - I will check if I can use a different Android API to get this specific value out there. Sadly amazon themselves tell to use a "private API" - I hope for the best.
Quote:2019-12-06 20:49:30.474 T:29428 NOTICE: Head-Position 1479168 Timestamp Position 1470175 Delay-Offset: 187.354 ms
2019-12-06 20:49:30.475 T:29428 NOTICE: HW-Delay (1): 0.187354
2019-12-06 20:49:30.475 T:29428 NOTICE: Delay Current: 130.365278
2019-12-06 20:49:30.540 T:29428 NOTICE: Delay Current: 119.269444
2019-12-06 20:49:30.541 T:29428 NOTICE: Framecounter: 1473322 Time: 1048306589149711 Current-Time: 1048306590688019
2019-12-06 20:49:30.542 T:29428 NOTICE: Delay - Timestamp: 323.979 (ms) delta: 2.13515 (ms) playtime: 30696.3 (ms) Duration: 31020.3 ms
2019-12-06 20:49:30.543 T:29428 NOTICE: Head-Position 1482240 Timestamp Position 1473424 Delay-Offset: 183.667 ms
2019-12-06 20:49:30.543 T:29428 NOTICE: HW-Delay (1): 0.183667
2019-12-06 20:49:30.544 T:29428 NOTICE: Delay Current: 125.240278
2019-12-06 20:49:30.603 T:29428 NOTICE: Framecounter: 1473322 Time: 1048306589149711 Current-Time: 1048306652561942
2019-12-06 20:49:30.603 T:29428 NOTICE: Delay - Timestamp: 302.417 (ms) delta: 63.7991 (ms) playtime: 30758 (ms) Duration: 31060.4 ms
2019-12-06 20:49:30.603 T:29428 NOTICE: Head-Position 1485312 Timestamp Position 1476384 Delay-Offset: 186 ms
2019-12-06 20:49:30.603 T:29428 NOTICE: HW-Delay (1): 0.186
2019-12-06 20:49:30.604 T:29428 NOTICE: Delay Current: 122.677778
2019-12-06 20:49:30.605 T:29428 NOTICE: Framecounter: 1473322 Time: 1048306589149711 Current-Time: 1048306654948173
2019-12-06 20:49:30.607 T:29428 NOTICE: Delay - Timestamp: 338.917 (ms) delta: 67.3968 (ms) playtime: 30761.6 (ms) Duration: 31100.5 ms
2019-12-06 20:49:30.607 T:29428 NOTICE: Head-Position 1485312 Timestamp Position 1476557 Delay-Offset: 182.396 ms
2019-12-06 20:49:30.607 T:29428 NOTICE: HW-Delay (1): 0.182396
2019-12-06 20:49:30.608 T:29428 NOTICE: Delay Current: 132.915278
Quote:2019-12-06 20:52:48.001 T:29428 NOTICE: HW-Delay (1): 0.0581875
2019-12-06 20:52:48.002 T:29428 NOTICE: Delay Current: 575.288889
2019-12-06 20:52:48.008 T:29428 NOTICE: Framecounter: 432403 Time: 1048503259921492 Current-Time: 1048504057984184
2019-12-06 20:52:48.008 T:29428 NOTICE: Delay - Timestamp: 646.563 (ms) delta: 798.386 (ms) playtime: 9806.77 (ms) Duration: 10453.3 ms
2019-12-06 20:52:48.008 T:29428 NOTICE: Head-Position 473088 Timestamp Position 470725 Delay-Offset: 49.2292 ms
2019-12-06 20:52:48.009 T:29428 NOTICE: HW-Delay (1): 0.0492292
2019-12-06 20:52:48.009 T:29428 NOTICE: Delay Current: 583.111111
2019-12-06 20:52:48.015 T:29428 NOTICE: Framecounter: 432403 Time: 1048503259921492 Current-Time: 1048504064702108
2019-12-06 20:52:48.015 T:29428 NOTICE: Delay - Timestamp: 650.5 (ms) delta: 805.112 (ms) playtime: 9813.5 (ms) Duration: 10464 ms
2019-12-06 20:52:48.015 T:29428 NOTICE: Head-Position 473088 Timestamp Position 471048 Delay-Offset: 42.5 ms
2019-12-06 20:52:48.015 T:29428 NOTICE: HW-Delay (1): 0.0425
2019-12-06 20:52:48.015 T:29428 NOTICE: Delay Current: 593.777778
2019-12-06 20:52:48.022 T:29428 NOTICE: Framecounter: 432403 Time: 1048503259921492 Current-Time: 1048504071531338
2019-12-06 20:52:48.022 T:29428 NOTICE: Delay - Timestamp: 654.271 (ms) delta: 812.011 (ms) playtime: 9820.4 (ms) Duration: 10474.7 ms
2019-12-06 20:52:48.022 T:29428 NOTICE: Head-Position 475136 Timestamp Position 471379 Delay-Offset: 78.2708 ms
2019-12-06 20:52:48.022 T:29428 NOTICE: HW-Delay (1): 0.0782708
2019-12-06 20:52:48.022 T:29428 NOTICE: Delay Current: 590.222222
(2019-12-06, 23:07)fritsch Wrote: Testbuild is here: http://mirrors.kodi.tv/test-builds/andro...bi-v7a.apk (mirror will need to sync a bit)
If you have suggestions to this PR, two things are conditionally mandatory:
a) uncut Debug Log (always) - I don't run behind "me too" people
b) If you think delay is totally fucked up in comparison to normal Leia, turn on Component Logging for Audio (only the audio component) additionally to a), reproduce the issue, post the log. Component Logging will fill your logfile quite heavily, therefore take care to only reproduce and post.
(2019-12-07, 12:48)A600 Wrote: @fritsch. I compiled your branch for Leia: https://github.com/fritsch/xbmc/tree/timestamp and, so far, it seems that audio sync issues are fixed for me.
Previously, I always had the issue no matter what audio settings I chose on Kodi or the FireTV with the all audio formats and I had to rely on the latency advanced setting.