OSMC announced new Vero4k, opinions?

Just wanted to post about some progress we've made.

(2017-05-28, 22:50)wesk05 Wrote: PCM audio: Output is limited to 16-bit and is capped at 96 kHz. Hi-resolution 24-bit audio will be dithered to 16-bit. 176.4 and 192 kHz are down sampled to 96 kHz.

As of OSMC 2017.06-1, this is no longer the case Smile

Quote:HDR: Rec.2020 color space and HDR10 metadata passthrough works only when there is no refresh rate switching (either disabled or refresh rate is set to match the frame rate manually).
Dolby Vision HDR sample clips play OK, but Dolby Vision metadata cannot be detected in the output. Similarly, HDR10 videos in VP9 profile 2.0 format can be played, but the output doesn’t seem to have HDR metadata.

HDR improvements are in the works and we will have it in better shape soon enough.

Quote:Color Fidelity: Native 8-bit output is fine. 10-bit content is dithered to 8-bit and has huge chroma errors. From an academic stand point, this will be considered as unwatchable. This seems to be a problem with the Linux driver because LibreELEC builds also show same errors.

There are now improvements to this (see above). I'd love to know of any clips that are not playing back well; as well
as any equipment that you're having problems with.

Quote:3D: HSBS/HTAB playback in 1080p doesn’t trigger 3D signaling. You have to manually select the 3D mode on the TV. When output resolution is set to 2160p, HSBS/HTAB content is played only in the left half or top half of the screen.

Working on this; as well as adding support for Frame Packed output. We had some 3D (including autoswitching) improvements in 2017.06-1
but it needs a bit more work


Thread Rating:
  • 4 Vote(s) - 4 Average

Messages In This Thread
RE: OSMC announced new Vero4k, opinions? - by Sam.Nazarko - 2017-07-18, 05:30

Logout Mark Read Team Forum Stats Members Help
OSMC announced new Vero4k, opinions?44