[TESTING] Linux 4.9 kernel and improved video stack for Vero 4K / 4K +

[tommyhome]

Yeah, its Samsung, so I’m hoping that there is a way to detect which resolution is available in HDR and that the Vero 4k+ could be made to automatically switch to a suitable mode? (like it does to match the refresh rate)

according to the logs it does exactly what it’s supposed to do.
https://paste.osmc.tv/gajexaqehe

Edit:
after playing around it seems like my tv does HDR in 1080p, if I force it to use 60Hz instead of the native 23.975 (removed that one from the whitelist) it plays with HDR in 1080p.
Here’s a new log: https://paste.osmc.tv/wacugideyu

[hdmkv]

Any update on 3D MVC being re-enabled in the latest test or official build?

[sam_nazarko]

We need to release Buster first.

[grahamh]

@tommyhome

according to the logs it does exactly what it’s supposed to do.

Difficult to confirm that. In the first log it seems you have not whitelisted any 1080 modes. Guisettings says your desktop resolution is 4k23.9Hz but it was 720p when Kodi started. Then since you didn’t turn on debug logging I can’t see when you changed the desktop to 4k or what happened when you tried to play that video without the GUI set to 4k. If 1080p wasn’t whitelisted, it’s not surprising it didn’t play as 1080p.

@tommyhome

if I force it to use 60Hz instead of the native 23.975 (removed that one from the whitelist) it plays with HDR in 1080p

That should not happen but again, without debug logging it’s difficult to see what happened when you tried to play it with 1080p23.9hz whitelisted.

I recommend you don’t whitelist the ‘VESA’ modes. That may be part of the problem.

[tommyhome]

Here’s a full debug log: https://paste.osmc.tv/vabezoxapo
First with the 1080p 23.98 whitelisted, then with it removed from the whitelist.
with it in the whitelist it plays at the correct framerate but with wrong colors, with it removed from the whitelist kodi doubles the framerate and plays it in hdr.

(yeah, I have the gui set to 4k at the moment, I usually run it in 1080p, but that doesn’t make any difference, the problem is the same, removing the whitelist doesn’t make any difference either, but it does play in hdr upscaled by kodi to 4k without doubling the framerate).

[grahamh]

It looks like we are sending the right signals

Jul 19 04:14:57 osmc-Vero4K kernel: hdmitx: video: Colorimetry: bt2020nc
Jul 19 04:14:57 osmc-Vero4K kernel: hdmitx: video: HDR data: EOTF: HDR10
Jul 19 04:14:57 osmc-Vero4K kernel: hdmitx: video: Master display colours:
                                    Primary one 0.2650,0.6900, two 0.1500,0.0600, three 0.6800,0.3200
                                    White 0.3127,0.3290, Luminance max/min: 1000,0.0000
Jul 19 04:14:57 osmc-Vero4K kernel: hdmitx: video: Max content luminance: 851, Max frame average luminance: 96

What may be confusing your display is you have the quantisation range set to full. There’s normally no need for that. Try setting it to limited.

[maartenjf]

Just a quick message to say I am currently testing this kernel and am experiencing no problems whatsoever. I’ve been running it without any issues whatsoever for a couple of weeks, the main reason being Wireguard compatibility.

For Wireguard to work, I had to install the wireguard-dkms package, and with this, even wg-quick works flawlessly.

Media playback: no issues whatsoever. I only play 1080p tho.
I think I only had one sad face in Kodi, but that was just around the time that I restored the Kodi backup so that could’ve triggered the sad face for some reason, but no issues at all after that.

[sam_nazarko]

The next (4.9) kernel will have Wireguard support included.

Sam

[maartenjf]

Well, like I wrote, I’ve got it up and running with no issues whatsoever with your current version! (So I’m super pleased with this already) It was an absolute no-go on stable (kernel 3.*).

Do you mean it will have Wireguard compatibility in the included (default) repositories?

Do you expect any issues by the way for testers like me when updating/upgrading or falling back to stable when this becomes mainstream?

[sam_nazarko]

It just means the kernel module will be included for now. Userland won’t be bundled by default – at least not yet.

@maartenjf

Do you expect any issues by the way for testers like me when updating/upgrading or falling back to stable when this becomes mainstream?

Yes – it’s possible you won’t be able to update smoothly to Buster. I’m still trying to work out an update path.

[querty1000]

any news on an official build with the 3D feature?

[sam_nazarko]

When it’s ready, it will become part of the stable update channel.

[querty1000]

Yes, i know, but

• it is a lot to do
  or
• it is nearly ready
  or
• do we get another testbuild

The vero “nerves” with update information, so it would be cool to see at least another/newer testbuild

[sam_nazarko]

There will of course be some more test builds

Sam

[krtinicfix]

I get this as well, when trying to start the video or when stopping it. I get the same thing over SMB, SFTP or Simple IPTV addon. I also tried turning off automatic refresh rate adjustment and some plugins just in case, but it still happens, even when I try using the interface slowly.

I also would get a bad link when uploading log, something like “paste.osmc.tv/< html >”, so I’m sending it to you this way
1.12 MB file on MEGA

If you want me to help out by testing stuff I can. Thanks for your effort

[Psxavatar]

Hi Sam, if you could give an indication when the 3d functionality can roughly be expected it would be very helpful as requested by querty1000. I personally have no idea when I can watch 3d movies with this great piece of technic. Really appreciate your support and help!!

[sam_nazarko]

I don’t have a firm ETA, sorry.
My wish (and this is purely speculation) is for mid September.

There is a lot of work behind the scenes and we keep moving forward.

Sam

[KaraokeAmerica]

@sam_nazarko

My wish (and this is purely speculation) is for mid September

Sam, I’m new here and have never even seen the OSMC interface before yesterday when i installed it on a Pi3B. It worked great for me…similar to LibereELEC, but with less tweaking required to get 3D-MVC to work. Basically none actually. I actually didn’t even see many of the settings I saw in the LibreELEC build. I am running it through a Denon Atmos/DTS-X capable receiver to a 1080, 3D projector and t just worked. Awesome!

I also want to say that your support seems to be great based on the threads I have seen. Thank you for that! Not all products have the actual developers in the forums!

However, I just purchased a Vero-4K yesterday in my never ending quest for a box that can “do it all” and in reading this thread it is making me wonder if it is fully functional. Does it play 3D-MVC now or is it waiting for a new build to work fully? Things like “version of Kodi” or other behind the scenes things are beyond my knowledge. frankly, i hate Kodi and even on my Pi OSMC install I immediately installed the “Plex for Kodi” add on and use it that way. I simply tolerate Kodi because it’s the only non-proprietary platform that will play 3D-MVC that I’m aware of at all.

Will this Vero-4K be fully functional when I get it in playing 3D of any format I throw at it?

Thanks again for the cool stuff!

[ActionA]

You need to follow this thread

3D Frame Packed output

For a while now, we’ve been working on adding support for Frame Packed (MVC) output when playing 3D content. Side-by-side and Top-and-bottom output have been possible for some time over the years, but this isn’t ideal as the resolution is halved. With these test builds, you should be able to play MVC content and output as Frame Packed 3D if your equipment supports it. These are still test builds, and we need more feedback before we can make this part of OSMC as standard. Many thanks to @tanio9…

[sam_nazarko]

You just need to install the 3D MVC Kodi build and you will be able to play this content.