[TESTING][S905(X)] 10bit/HDR/Dithering Test Builds & Discussion

Thank you kszaq. Again, none of this would be possible without the work you've done. Hopefully soon we'll have made enough progress this work can be merged back into your branches.

afl1 thank you for the device tree. I've updated the OP with it.

Regarding 60fps h264 playback, I'm first focusing on video that doesn't have frame skips on the MM kernel. The 60fps big buck video is also h264 L5.2, which was never supposed to be supported (only up to 5.1). As a side note, I have a high bitrate 60fps/h265/10bit/bt2020 movie that plays back in a watchable state (still frame skips, but not near as bad as just h264 4k).

Quote from Strompel

I tested it with my marantz nr1606. It did not fix it for me. But then I have been having issues with the video switching in almost every build of libreelec for 905x. I have a mini m8s II box and a hisense 4k TV.

When libreelec starts it is just a black screen after boot logo. This also happens after switching back to libreelec interface after watching 4k(hdr) video.

I change the hdmi settings to standard and then back to enhanced in my TV setup menu. And I will get dislay. I have libreelec set to 3840x2160p at 60hz If I connect it directly to the TV it is ok without hdmi setting switching.

The only build that works fine without switching hdmi settings through my avr is 8.0.1g of kszaq. No issue at all with the startup of libreelec and video file hdr and 4k switching.

Hope this information can be useful.

This sounds different than the output issue some users were facing on 4k output alone. The null fix of kszaq's for mode switching may help (but probably not)

Do you have this issue if you set the GUI to another resolution such as 720 or 1080? 1080 for the GUI is recommended since LE supports resolution switching and has poor upscaling.

Edit: I introduced artifacts with those buffer changes on the last test build (not in OP). Still working on those.

Uploaded a new build, and updated the download link in OP to point to github releases (no longer using an ad-ridden upload site). All changelogs between releases will also be posted there. If more users who had 4k output issues on nougat report this is working well for them, I think we could be close to making these "standard" builds

Changes:

• kernel: Partially revert experimental buffer changes to reduce artifacts and improve frame skip situation.
• kernel: Revert a cache change for "less memory" devices that negatively affected frame skips on my 1G ram box -- LE is light enough.
• kernel: Fix 4k h264 video (needs more testing).
• kernel: Fix 4k video output compatibility issue introduced in the franken-nougat kernel -- needs more testing by users with 4k output issues on nougat.
• kodi: bump to 21c2dba (kszaq)
• projects/S905: use "null" display mode only when needed (kszaq)
• SMBFile: Remove year old workaround (kszaq)

Quote from saltanar

From samba share I can't find /storage/.config folder

The "Configfiles" samba share maps to /storage/.config. Add the echo command in OP to an "autostart.sh" file in that folder.

Quote from kubrickdave

I can report that the frame skips seem to be gone.

I was previously on the 20170603182409 Frankenstein build and had a perfectly smooth gradient in my hdr_banding.mkv file. With the full Nougat build, the banding returned. There appears to be no difference between 8bit and 10 bit in attr.

Since I got a video of the same name from a post on this forum I've been using for testing, is that a smurfs intro? Could you upload the dmesg of playback with and without attr set to 10bit? I unfortunately can't recreate in 8bit with dithering, or 10bit without dithering.

Edit: there might still be issues if there's any playback before it's set.

Quote from kubrickdave

That's right, I created that file.

10bit attr:

Code

hdmitx: set clk: VIC = 93  cd = 5  frac_rate = 1

8bit attr:

Code

hdmitx: set clk: VIC = 93  cd = 4  frac_rate = 1

Output is 10bit and 8bit respectively (confirmed by AVR), but both appear identical.

I write to the attr node in autostart.sh. The GUI output after boot is 10bit.

Edit: complete kernel log snippet

mN4mSwbW

Display More

I believe you, but really can't recreate. Is the banding as extreme as your previous image from krypton (OZsfOvG.jpg)? Additionally on the 8bit output, you should see a bit of a "jitter" around where the banding would occur.

Quote from kubrickdave

It appears less severe, but I'm largely going from memory here. I'll do some more testing, when I have time.

Maybe someone else can chime in.

Edit: The gradation is definitely less bad than on the old kszaq builds.

After a bit more testing, I think you're comparing to a build that still had dithering enabled for 10bit output.

Quote from saltanar

I tried it, with 8 bit is all ok, with 10 bit I have no 4k video out

Need more info such as tv and possibly avr, as well as a log (dmesg). If you have a spare hdmi cable laying around, it would be helpful if you could try that as well.