Will the Vero V support 2560x1440?

Will this resolution will be supported with a future update? QHD resolution isn’t listed when I connect my Vero V to my QHD monitor. Thanks!

It should be supported already. Please post full logs so we can check what happens when you boot with that monitor.

https://paste.osmc.tv/zeyaqokoxu

thanks!

It looks like your monitor Cooler Master Tempest GP2711 does not support higher resolution than 1920x1080 on hdmi → Egnyte.

According to the manual both DP and HDMI support 2560x1440? So I’m curious where you found this information? Maybe the resolutions reported by EDID are wrong here?

Please note that I could select QHD on my Vero 4K but it gave a blank picture (no signal). I currently have no HDMI to display port convertor at hand but I could try that later this week.

Previously, we couldn’t get QHD to work on Vero V so it is currently filtered out. I can’t recall why we thought it didn’t work as no-one on the team has a display that supports that mode.

Maybe with your help we can solve this. I’m building a kernel now which restores that mode.

@JimKnopf my reading of the specs is it’s only 2560x1440@165hz that’s not supported under HDMI.

Yes, V does seem to have a different issue than 4k. I can’t tell why you don’t get a picture with vero4k though.

Thank you, I’ll be happy to test and give as much feedback as possible :slightly_smiling_face:

Interesting that 165hz @ 1440 isn’t supported by this monitor as it should be well within the HDMI 2.0 bandwidth specs if I’m not mistaken. 60Hz support would be more than enough in my case.

According to that spec, it needs a pixel clock of 664MHz which is more than HDMI2.0 (600MHz). I have a kernel now that seems to work - my Vertex thinks there’s a signal anyway. I’ll ask @sam_nazarko what’s the best way to get it to you.

1 Like

sorry for the confusion, I misread page 19 where it ends with an fhd resolution

Hi

Hopefully the issue is now addressed

I’d appreciate it if you could test this and provide feedback before we potentially release this as an update to other users. To test this update:

  1. Login via the command line
  2. Run the following command to add the staging repository:
    echo 'deb http://apt.osmc.tv bullseye-devel main' | sudo tee /etc/apt/sources.list.d/osmc-devel.list
  3. Run the following commands to update: sudo apt-get update && sudo apt-get dist-upgrade && reboot
  4. Your system should have have received the update.

Please see if the issue is resolved.

I also recommend you remove /etc/apt/sources.list.d/osmc-devel.list after updating.

This will deactivate the staging repository. You can do so with the following command:
sudo rm /etc/apt/sources.list.d/osmc-devel.list.

Please note that we will automatically disable this update channel after 14 days on your device in case you forget to do so to ensure that your system reverts to the stable update channel.

Thanks for the quick update! :smiley:

The GUi now let’s me select 1440 at 59 and 60 Hz and 4K YouTube and 4K content is playing without any problems at 1440 according to the monitor :+1:

I don’t have any >=1440 50Hz content, will Kodi now be able to play this at 50Hz in 1440p resolution?

When doing some further testing I tried playing DVB-C content (50Hz I) but using PVR now crashes Kodi regardless of the GUI resolution.

I’ve uploaded the logs: https://paste.osmc.tv/usozarixij and I’ve kept the dev source enabled for now :slight_smile:

No. 1440p50hz is not supported by your monitor, according to the EDID.

Can you turn on debug logging, please, and repeat?

Sure, here’s the debug log: https://paste.osmc.tv/qisadagace

Thanks. I think that’s a problem with the upgraded Kodi (21.0). Does it happen when playing recordings?

Playing a recording works fine, thanks.

1 Like

If you try all values of Settings -> TV & Radio -> Fallback Framerate, does it make any difference watching live TV based on DVB-C?

It certainly does! Both 59 and 50Hz work (and “off” makes Kodi crash).

I guess you’re located in Europe (PAL region) and your DVB-C provider uses 50 fps for the most channels. Glad to hear that this fallback feature helps.

Yes, that’s correct. I’ll remove myself from the development channel updates for now as my requested feature has been added and this workaround works fine for me.

Thanks again for the quick support!

1 Like