It looks like you didn’t update to the test kernel properly then
Sam
Now I’m confused.
So I re-installed the test kernel:
osmc@vero4k:~$ wget https://collab.osmc.tv/s/DKFOE1k8H4QuuCq/download -O /home/osmc/kernel.deb
--2018-09-19 13:21:01-- https://collab.osmc.tv/s/DKFOE1k8H4QuuCq/download
Resolving collab.osmc.tv (collab.osmc.tv)... 185.166.131.120
Connecting to collab.osmc.tv (collab.osmc.tv)|185.166.131.120|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 33037666 (32M) [application/x-deb]
Saving to: '/home/osmc/kernel.deb'
/home/osmc/kernel.deb 100%[=================================================>] 31.51M 9.09MB/s in 3.6s
2018-09-19 13:21:05 (8.75 MB/s) - '/home/osmc/kernel.deb' saved [33037666/33037666]
osmc@vero4k:~$ sudo dpkg -i /home/osmc/kernel.deb
(Reading database ... 22828 files and directories currently installed.)
Preparing to unpack /home/osmc/kernel.deb ...
Examining /etc/kernel/preinst.d/
Done.
Unpacking vero364-image-3.14.29-119-osmc:arm64 (119) over (119) ...
Examining /etc/kernel/postrm.d .
Setting up vero364-image-3.14.29-119-osmc:arm64 (119) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.14.29-119-osmc /boot/vmlinuz-3.14.29-119-osmc
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal-osmc 3.14.29-119-osmc /boot/vmlinuz-3.14.29-119-osmc
run-parts: executing /etc/kernel/postinst.d/inform-updater 3.14.29-119-osmc /boot/vmlinuz-3.14.29-119-osmc
run-parts: executing /etc/kernel/postinst.d/upload-to-emmc 3.14.29-119-osmc /boot/vmlinuz-3.14.29-119-osmc
7+1 records in
7+1 records out
8308736 bytes (8.3 MB, 7.9 MiB) copied, 0.186001 s, 44.7 MB/s
0+1 records in
0+1 records out
83968 bytes (84 kB, 82 KiB) copied, 0.010653 s, 7.9 MB/s
osmc@vero4k:~$ rm /home/osmc/kernel.deb
osmc@vero4k:~$ sudo reboot
I reconnected via SSH following reboot, and the kernel version is still showing as 3.14.29-119-osmc
osmc@vero4k:~$ uname -a
Linux vero4k 3.14.29-119-osmc #1 SMP Wed Sep 12 21:28:17 UTC 2018 aarch64 GNU/Linux
Although the date has changed to Wed Sep 12
So both seem to report the same kernel version, just with a different date, which is confusing.
I downloaded the two files into a directory and did a diff, and they are different:
osmc@vero4k:~$ wget https://collab.osmc.tv/s/DKFOE1k8H4QuuCq/download -O /home/osmc/kernels/kernel-test.deb
--2018-09-19 13:26:10-- https://collab.osmc.tv/s/DKFOE1k8H4QuuCq/download
Resolving collab.osmc.tv (collab.osmc.tv)... 185.166.131.120
Connecting to collab.osmc.tv (collab.osmc.tv)|185.166.131.120|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 33037666 (32M) [application/x-deb]
Saving to: '/home/osmc/kernels/kernel-test.deb'
/home/osmc/kernels/kernel-test 100%[=================================================>] 31.51M 9.29MB/s in 3.5s
2018-09-19 13:26:14 (9.10 MB/s) - '/home/osmc/kernels/kernel-test.deb' saved [33037666/33037666]
osmc@vero4k:~$ wget http://apt.osmc.tv/pool/main/v/vero364-source-3.14.29-119-osmc/vero364-image-3.14.29-119-osmc_119_arm64.deb -O /home/osmc/kernels/kernel-stable.deb
--2018-09-19 13:27:25-- http://apt.osmc.tv/pool/main/v/vero364-source-3.14.29-119-osmc/vero364-image-3.14.29-119-osmc_119_arm64.deb
Resolving apt.osmc.tv (apt.osmc.tv)... 159.253.212.250
Connecting to apt.osmc.tv (apt.osmc.tv)|159.253.212.250|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero364-source-3.14.29-119-osmc/vero364-image-3.14.29-119-osmc_119_arm64.deb [following]
--2018-09-19 13:27:25-- http://ftp.fau.de/osmc/osmc/apt/pool/main/v/vero364-source-3.14.29-119-osmc/vero364-image-3.14.29-119-osmc_119_arm64.deb
Resolving ftp.fau.de (ftp.fau.de)... 131.188.12.211, 2001:638:a000:1021:21::1
Connecting to ftp.fau.de (ftp.fau.de)|131.188.12.211|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 33034604 (32M) [application/x-debian-package]
Saving to: '/home/osmc/kernels/kernel-stable.deb'
/home/osmc/kernels/kernel-stab 100%[=================================================>] 31.50M 9.75MB/s in 3.2s
2018-09-19 13:27:28 (9.75 MB/s) - '/home/osmc/kernels/kernel-stable.deb' saved [33034604/33034604]
osmc@vero4k:~/kernels$ cd ~/kernels
osmc@vero4k:~/kernels$ diff kernel-stable.deb kernel-test.deb
Binary files kernel-stable.deb and kernel-test.deb differ
When I initially installed the test kernel I did check “uname -a” before and after, and did notice a bump in the version, although i didn’t note what the version was beforehand. This is why I’m now confused and wondering whether the link in this post to go back to stable is correct.
I’ve had another go at going back to the stable kernel.
osmc@vero4k:~/kernels$ sudo dpkg -i kernel-stable.deb
(Reading database ... 22828 files and directories currently installed.)
Preparing to unpack kernel-stable.deb ...
Examining /etc/kernel/preinst.d/
Done.
Unpacking vero364-image-3.14.29-119-osmc:arm64 (119) over (119) ...
Examining /etc/kernel/postrm.d .
Setting up vero364-image-3.14.29-119-osmc:arm64 (119) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.14.29-119-osmc /boot/vmlinuz-3.14.29-119-osmc
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal-osmc 3.14.29-119-osmc /boot/vmlinuz-3.14.29-119-osmc
run-parts: executing /etc/kernel/postinst.d/inform-updater 3.14.29-119-osmc /boot/vmlinuz-3.14.29-119-osmc
run-parts: executing /etc/kernel/postinst.d/upload-to-emmc 3.14.29-119-osmc /boot/vmlinuz-3.14.29-119-osmc
7+1 records in
7+1 records out
8306688 bytes (8.3 MB, 7.9 MiB) copied, 0.18885 s, 44.0 MB/s
0+1 records in
0+1 records out
83968 bytes (84 kB, 82 KiB) copied, 0.0102379 s, 8.2 MB/s
...reconnect via SSH
osmc@vero4k:~$ uname -a
Linux vero4k 3.14.29-119-osmc #1 SMP Wed Sep 5 19:09:21 UTC 2018 aarch64 GNU/Linux
Is this correct for the “stable” August release kernel?
Yes that’s the stable kernel
stable is 5 Sept, testing is 12 Sept. There was no version bump.
Thanks for the confirmation, I was obviously getting too hung up on the kernel version number.
Any feedback on these logs ?
No time to look at it here yet.
There are a couple of issues with this kernel. We will revisit after making some changes
Thanks
Sam
I hope one of the issues you’ve noted, is that the banding has not been fixed, at least for me.
re the Vero 4K+: “can play back your 4K, 10-bit HDR content” (Vero - OSMC). Is that a true statement if the output is 8 bit ?
Given that the Vero 4K and 4K+ are running the same software, and using the same chipset, I’d expect if I connected a 4K+ to the same TV and played the same content, I’d also have banding.
The Vero 4K / 4K + can output a 10-bit signal and will if your display advertises support for it; and you are playing 10-bit content.
Your log shows that the new kernel is correctly identifying that you are playing 10-bit content and sending the correct signal. See:
[ 47.409394] codec: (Full type: 0x00501000)
[ 47.409396] codec: Bit depth: 10-bit, Colour range: limited
[ 47.409398] codec: Primaries: bt2020, Transfer function: smpte-st-2084, RGB-YCC: bt2020nc
[ 47.409403] codec: Master display colours:
As we are sending the HDR EOTF and switching to BT2020, 10-bit, 4:4:4; I can’t see how this is an issue with the signal that the Vero is sending.
What’s the make and model of your display?
Model: LG B6.
We fixed banding on models like OLED B6 some time ago.
I will revisit it to see if we’ve accidentally removed something with these changes.
Thanks
Sam
I call it banding, because that’s what the symptoms look like. But whether it’s caused by the dithering issue that I think you’re saying is fixed, or 8 bit colour space, I don’t know.
I can see we’re sending 10-bit signal to your display.
Can you take a photo of what you see so I can compare it on a display here?
Thanks
Sam
Could you try setting your GUI resolution to 1920x1080x50Hz.
And make sure you have adjust refresh rate set to start/stop.
I’m on LG Oled 55B6 and also banding problems with Vero 4k+ and a 4k remux film. Testes 1920x1080x50 and still problem.
Are you using the improvements above?
If not: you’ll need to turn on HDR autoswitch
Sam
nobanding.jpg is the video played back over DNLA by the TV’s own player.
banding.jpg is the video played back by the Vero 4k.
@grahamh the banding is also still there at 1920x1080p 50Hz. But I don’t know where to “adjust refresh rate set to start/stop”.