2020-03-14, 23:48
Funny and why I did not notice the bug for so long:
Multi-Channel / DTS / AC3 / DD+ look like this:
Stereo (including AAC):
Long story short: I wrongly pushed the timestamp calculated getTimeStamp-Delay into our Audio-Engine. The HW-Delay you see is the difference that the TimeStamp API calculates (fritschfiretv + Matrix) in comparison to standard Kodi Leia. Means for this content (Stereo) FireTV 4K was always roughly 180 to 200 ms wrong on average (and will stay wrong on official Leia builds), depending on sample even more.
Multi-Channel / DTS / AC3 / DD+ look like this:
Quote:2020-03-14 22:35:03.069 T:24866 DEBUG: Delay - Timestamp: 671.4166666611447
2020-03-14 22:35:03.070 T:24866 DEBUG: HW-Delay (1): 42.0833333333519 ms
2020-03-14 22:35:03.070 T:24866 DEBUG: Combined Delay: 671.4166666611447 ms
2020-03-14 22:35:03.070 T:24866 DEBUG: Delay Current: 635.341667 ms
Stereo (including AAC):
Quote:2020-03-14 22:38:51.730 T:24866 DEBUG: Delay - Timestamp: 305.3125000000705 ms
2020-03-14 22:38:51.731 T:24866 DEBUG: HW-Delay (1): 178.47916666666563 ms
2020-03-14 22:38:51.731 T:24866 DEBUG: Combined Delay: 305.3125000000705 ms
2020-03-14 22:38:51.731 T:24866 DEBUG: Delay Current: 304.126389 ms
Long story short: I wrongly pushed the timestamp calculated getTimeStamp-Delay into our Audio-Engine. The HW-Delay you see is the difference that the TimeStamp API calculates (fritschfiretv + Matrix) in comparison to standard Kodi Leia. Means for this content (Stereo) FireTV 4K was always roughly 180 to 200 ms wrong on average (and will stay wrong on official Leia builds), depending on sample even more.