You can zip the file you got from "pastekodi -c" and attach it to a post here.
But it'd be better to reproduce the issue immediately after kodi start, stop playing a few seconds after the issue happened and then create the log - that should be small enough for standard pastekodi upload (if you get an error, retry a few time with some 30-60 seconds between retries, ix.io might be busy and thus fail to accept the paste).
so long,
Hias
Please post a short sample and a full debug log.
This seems to be a kodi bug, might be best to report it on kodi forums or kodi's github.
ffprobe reports the audio stream of DTS-HD MA 7.1 'Dredd' Sound Check.m2ts as DTS-HD-MA
Input #0, mpegts, from 'kodi/DTS-HD MA 7.1 'Dredd' Sound Check.m2ts':
Duration: 00:01:27.91, start: 11.650667, bitrate: 25283 kb/s
Program 1
Stream #0:0[0x1011]: Video: h264 (High) (HDMV / 0x564D4448), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 90k tbn
Stream #0:1[0x1100]: Audio: dts (DTS-HD MA) ([134][0][0][0] / 0x0086), 48000 Hz, 7.1, s32p (24 bit)But kodi reports just dts and seems to choose the DTS core stream
2023-02-03 16:39:05.885 T:1180 info <general>: ffmpeg[0x3807b58]: Input #0, mpegts, from 'smb://lebuild.lan/samples/kodi/DTS-HD MA 7.1 'Dredd' Sound Check.m2ts':
2023-02-03 16:39:05.885 T:1180 info <general>: ffmpeg[0x3807b58]: Duration: 00:01:27.91, bitrate: N/A
2023-02-03 16:39:05.885 T:1180 info <general>: ffmpeg[0x3807b58]: Program 1
2023-02-03 16:39:05.885 T:1180 info <general>: ffmpeg[0x3807b58]: Stream #0:0[0x1011]: Video: h264 (HDMV / 0x564D4448), none, 1920x1080, 90k tbn
2023-02-03 16:39:05.885 T:1180 info <general>: ffmpeg[0x3807b58]: Stream #0:1[0x1100]: Audio: dts ([134][0][0][0] / 0x0086), 0 channels
...
2023-02-03 16:39:05.952 T:1183 info <general>: CAEStreamParser::SyncDTS - dtsHD (core) stream detected (6 channels, 48000Hz, 16bit BE, period: 512, syncword: 0x41a29547, target rate: 0x18, framesize 2128))so long,
Hias
Right now the difference between 10.95.0 and nightlies is basically zero, so that's a placebo update.
This is not quite correct, the kernel update PR (which fixes glitches on all RPis and "no signal with some TVs on RPi4) and an ffmpeg patch update (which can potentially fix playback issues) were merged after 10.95.0 was built
so long,
Hias
For RPi0-3 you have to use the 2.5A one (with a micro USB plug), the 3A one is for RPi4 only (with a USB C plug).
RPi's can't provide more than 1.1A total (!) on all USB ports and the 2.5A is sufficient for that.
so long,
Hias
You have to reapply the changes to distroconfig.txt to get composite out working (the file is overwritten on updates).
I'll have a look again at providing a more robust way (probably we'll need to add a separate distroconfig-composite.txt that you can then include instead of distroconfig.txt).
so long,
Hias
It says undervoltage because it checks if the voltage on the RPi PCB dropped below about 4.75 volts - which will usually "upset" USB devices but can lead to all sorts of problems.
Don't use any charger, use the official RPi power supply and if that's not enough (RPi can only provide a very limited amount of current to USB ports) then use a powered hub or drive.
so long,
Hias
You can safely ignore the "Failed to unmount /flash" message, that's normal, but the "under-voltage detected" message indicates a serious issue:
Use a better power supply (the official RPi one is highly recommended) and/or a powered USB hub or USB drive.
so long,
Hias
Install the system tools addon from the LE repository - it contains 7zip
so long,
Hias
That is great! I'm curious though. What caused this issue on certain tv's?
A tiny, not well defined, optional, bit in the HDMI protocol which we discussed about for quite a long time as it wasn't clear from the spec how it was meant to be used and how TVs should handle it.
Basically the firmware sends a "disable display" flag (set AVMUTE) before handing over to the kernel video driver, but the kernel driver didn't implement the optional set/clear AVMUTE handling and some TVs decided to stick in the "off" state. Solution then was to always send "clear AVMUTE" bit in the control packet.
so long,
Hias
The fix was merged into LE11 a few hours ago and will be included in the next nightly build (20230124)
so long,
Hias
BTW: also have a look at this workaround: RE: LE 10.0.1/10.0.2 RPi4 - "CECActivateSource" stops working when soundbar connected
so long,
Hias
Sorry, no idea, I'm not aware of any changes in that area. If you are using an RPi the changes between 10.0.3 and 10.0.4 are basically just a very minor kodi update with no video/CEC related changes.
hias@lebuild:~/libreelec/xbmc-git$ git log --oneline --no-merges 286694e9df8741313a688b46940661a30f36f35c..19.5-Matrix
9e3e855d1d [Matrix] 19.5 Final
16661d25d0 Update game.controller.snes to v1.0.34
6b6bcf6d50 Update game.controller.default to v1.0.35
dac3e6e596 Revert "[subtitles] Fix CC condition for valid captions"
b6f0c52be6 [DVDDemuxClient] fix memory leak
2fffc98eb3 fix ubuntu ppa packaging for Matrix
9f4863e8ff [Windows] fix refresh rate not switch back to 60Hz/GUI after HDR toggle on Windows 11 22H2
ae0782a351 [Windows] Fix incorrect window position when switching from fullscreen to windowed in some cases
1b55c1d149 [Windows][Xbox] Bump Python to 3.8.15 and OpenSSL to 1.1.1q
85802f5996 [macOS] prevent crash on app quit
40f5992102 [PlayListPlayer] Fixed wrong player playlist with playlist files
1efa67aa5d [network] Use passwords.xml for more protocolsso long,
Hias
Dynamic HDR (HDR10+/DolbyVision) isn't supported in Kodi under Linux so this is expected. Use standard HDR10 or HLG files.
so long,
Hias
It depends on the encryption settings of your stream provider. A few sources only use widevine for authentication and/or decryption (i.e. streams can be HW decoded) but others - like Netflix - use widevide to decrypt and fully SW decode the stream (which leads to high CPU load).
so long,
Hias
Do you still have a backup of the LE10.0.2 installation? If yes, check which widevine CDM version you used with it (inputstream helper addon will show it) and compare it with the version you are currently using.
ISTR widevine versions from about half a year or a year ago cause a very high CPU load (heating up RPi, but streams still watchable on RPi4, but unwatchable/stuttering on RPi2/3 as the load is too high) - older versions were fine (but may not work any longer, depending on the source) - not sure about newer versions.
Personally I gave up on trying to watch Netflix etc with kodi addons, it was just too much hassle and hit-and-miss if it worked every evening when just wanting to watch the next episode of a show or a movie, and use the Netflix app on my TV instead. A cheap chromecast (or similar) device with official Netflix/.. app support is certainly the better choice if you don't like to play the cat-and-mouse game of streaming service changes and waiting for kodi addon updates.
so long,
Hias
As you swapped the firmware for a much newer version my bet would be this is causing the issue - LE 9.2.8 is using an ancient 4.19 kernel and should be running the firmware that came with it.
Just install official 10.0.4 or LE11 nightly versions.
so long,
Hias