I only added it last night at the request of a customer.
Sam
1 Like
Awesome. Is it possible to customize the hotfix name? [deprecated] doesnt really roll or the tongue nicely 
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!
Not at this time
Sam
You only have to do it once.
Will future update effect this Hotfix or is it set once and never need to do again?
You can set it once, provided you’re happy with the results.
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 am glad to hear this.
Once this thread closes and everyone’s on the same page we can work on improving auto-switching.
Sam
Hi 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?
The next update will not destroy your Vero 4K.
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.
See Backing up Settings - General - OSMC for how to make a backup.
I wish you the very best of luck with your surgery.
Sam
1 Like
Applied the Hotfix. All 10 bit movies play fine with no banding. Played various 8 bit movies and can’t fault the picture. Pleased I am.
So, what does the hotfix do exactly? Does it set the bit depth to 10 for everything?
Read the hotfix for yourself: [deprecated]
sudo wget "https://paste.osmc.tv/raw/edawoyazuh" -O /etc/rc.local
sudo chmod +x /etc/rc.local
reboot
[deprecated]
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
echo '444,10bit' > /sys/class/amhdmitx/amhdmitx0/attr
exit 0
This is exactly what it does.
4 Likes
Thanks for the info, so it sets the output to 10 bit then, for people that are not able to do that themselves in SSH.
@sam_nazarko Will the setting of 444,10bit in rc.local still enforce BT2020 colorspace for all 4K content like the GUI which is displayed in BT709?
I got it working great now, but at first I still had some slight banding, though that has been resolved by choosing the closest HDMI port on my Denon X3300 !! So, it is pretty darn important to check that you put it in a port closest to the output HDMI port.
Hi Sam.
Thanks for the good luck, it’s very much appreciated.
Reading back my previous post I realise ‘destroy’ was not quite the word I intended to use!
I’ve read up on the recovery process now; all looks fine.
Many thanks for the assistance.
@sam_nazarko I understand you really want to close this thread, but is there gonna be a new thread for the colorspace issue or is it already resolved?
There will be a new thread when we have made improvements to test.
This thread was about banding and flickering however, which is resolved.