We hope you've had a good Christmas and New Year. We've been working hard to improve OSMC for all platforms and keep things running smoothly. The end of 2023 was also busy for us, with the announcement of Vero V, our fifth iteration of our flagship device.
I just did the update and even after a second reboot the file “bypass_all” still contains 0 instead of 1 and the visual issues are back. I’ll just keep my own bootup script running for now, but wanted to let you know.
Dear Sam,
you already informed that one of the OSMC tasks is to properly implement DVTM.
Is this going to be part of future updates of Kodi 20.x or 21.x/new kernel will be required instead?
Thanks
This is not a change tied to Kodi and it should work fine with Kodi v20.
With that said, Kodi v21 ships with a newer ffmpeg (6.x) which can detect and handle DV profiles better. This could be beneficial in the future but doesn’t have an impact at this time
So, with the Vero V the value of “/sys/module/di/parameters/bypass_all” should still be 0? I know in that thread you mentioned the issue didn’t concern the V, but just wanted to confirm. On my Vero 4K+ it shows 1, but on my V it shows 0.
Hi Sam, is this related to my topic (Split HDMI signal - #15 by sam_nazarko ) for adding one globally to OSMC that activates in the presence of a file existing. Perhaps /lib/firmware/edid-custom.bin
Correct – it’s now possible to manually configure HDMI capabilities.
You won’t need a custom EDID for this and can configure it via Settings → Display
Ohhh thanks for that! I thought I was going nuts when I tried to watch the first 4K video on the Vero V - and only saw the a tiny video in the upper left part of the TV screen. I was able to work around this by manually scaling the video - but a bugfix sounds better!