The shortest way to put it is that you should just enable 10-bit in rc.local for now. You won’t get banding or flickering.
No – because as explained above, the auto switching does not always work. This was added as an experimental feature. The goal is to simplify HDR autoswitching in the future. For now however, we have fixed banding and flickering when colour depth is set properly.
Our focus is to work on improving the HDR autoswitching now, which is why I’m trying to finalise this topic, as the original reported issue is fixed.
Ok… for the first time i understand the meaning of the hdr auto switch and the entry in the rc.local - think my banding problem is solved… it looks like that the entry in my rc.local has an typo error so the hdr content was played in 8bit and the result was banding… i wonder that before april upate i don´t see banding but after i set the entry new yesterday and do some tests with the 4k demo i haven´t seen any banding yet…thanks again for your support!
The combination of the April update and the hot-fix fixed all the banding and flickering issues I was having with 10-bit 4K HDR material on my Panasonic OLED. Thanks Sam!
I’m reasonably adept with Linux on PC (Mint, Kali) and Pi (Raspbian), etc, but don’t have time to diagnose and recover a destroyed Vero 4k if applying the April update goes wrong (I have major surgery pending).
Is there a simple way to backup and restore my system as-is, given the o/s is stored on hard-wired internal storage?
If you had a failed update that damaged your system. you could reinstall from Download - OSMC in 2-3 minutes with a spare SD card or USB stick. We haven’t had any reports of damaged systems or boot issues after this update on any OSMC supported devices, including Raspberry Pi.