Hi there,
I’m running a Vero4k+ with the latest June update. 4k movies play back the way they should with the 4k finally arriving at the TV.
4k from TV/Satellite “pretend” to be 4k and the system’s information confirms that but my TV says 1080p. Everything else is OK.
Does anyone know how to fix that?
Thank you
BobW (Michael)
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device twice(!)
reproduce the issue
upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
OSMC skin screenshot:
Thank you for the how-to.
I followed the instructions, turned on the logging, played 10 secs of a UHD movie and then 10 secs of a UHD TV recording.
When sending the log files form “myOSMC” it worked to 100% but then I got the message
“Could not retrieve URL, want to save to SD-card” something like that, I am running kodi with the German localization.
What now?
Sorry, my bad. Did not reboot the vero4k so the logs were way too big…
So the URL for logs is: https://paste.osmc.tv/fafutuzahu
Your whitelist is…
Whitelist:
3840x2160: 23.976p, 24p, 25p, 29.97p, 30p
1920x1080: 23.976p, 24p, 29.97p, 30p, 50p, 59.94p, 60p, 120p
Which results in this because it is generally more advantageous to downscale than to change the framerate…
2023-06-30 19:25:35.025 T:3061 info <general>: [WHITELIST] Searching the whitelist for: width: 3840, height: 2160, fps: 50.000, 3D: false
2023-06-30 19:25:35.025 T:3061 debug <general>: [WHITELIST] Searching for an exact resolution with an exact refresh rate
2023-06-30 19:25:35.025 T:3064 info <general>: running thread: video_thread
2023-06-30 19:25:35.025 T:3061 error <general>: ** T99 ** 3840/2160 vs. 1920/1080 - 50.000000 vs. 23.976025, flags: 0x0
2023-06-30 19:25:35.026 T:3061 error <general>: ** T99 ** 3840/2160 vs. 1920/1080 - 50.000000 vs. 24.000000, flags: 0x0
2023-06-30 19:25:35.026 T:3061 error <general>: ** T99 ** 3840/2160 vs. 1920/1080 - 50.000000 vs. 29.970030, flags: 0x0
2023-06-30 19:25:35.026 T:3061 error <general>: ** T99 ** 3840/2160 vs. 1920/1080 - 50.000000 vs. 30.000000, flags: 0x0
2023-06-30 19:25:35.026 T:3061 error <general>: ** T99 ** 3840/2160 vs. 1920/1080 - 50.000000 vs. 50.000000, flags: 0x0
2023-06-30 19:25:35.026 T:3061 error <general>: ** T99 ** 3840/2160 vs. 1920/1080 - 50.000000 vs. 59.940060, flags: 0x0
2023-06-30 19:25:35.027 T:3061 error <general>: ** T99 ** 3840/2160 vs. 1920/1080 - 50.000000 vs. 60.000000, flags: 0x0
2023-06-30 19:25:35.027 T:3061 error <general>: ** T99 ** 3840/2160 vs. 1920/1080 - 50.000000 vs. 120.000000, flags: 0x0
2023-06-30 19:25:35.027 T:3061 error <general>: ** T99 ** 3840/2160 vs. 3840/2160 - 50.000000 vs. 23.976025, flags: 0x0
2023-06-30 19:25:35.027 T:3061 error <general>: ** T99 ** 3840/2160 vs. 3840/2160 - 50.000000 vs. 24.000000, flags: 0x0
2023-06-30 19:25:35.027 T:3061 error <general>: ** T99 ** 3840/2160 vs. 3840/2160 - 50.000000 vs. 25.000000, flags: 0x0
2023-06-30 19:25:35.028 T:3061 error <general>: ** T99 ** 3840/2160 vs. 3840/2160 - 50.000000 vs. 29.970030, flags: 0x0
2023-06-30 19:25:35.028 T:3061 error <general>: ** T99 ** 3840/2160 vs. 3840/2160 - 50.000000 vs. 30.000000, flags: 0x0
2023-06-30 19:25:35.028 T:3061 debug <general>: [WHITELIST] No match for an exact resolution with an exact refresh rate
2023-06-30 19:25:35.028 T:3061 debug <general>: [WHITELIST] Searching for an exact resolution with double the refresh rate
2023-06-30 19:25:35.029 T:3061 debug <general>: [WHITELIST] No match for an exact resolution with double the refresh rate
2023-06-30 19:25:35.029 T:3061 debug <general>: [WHITELIST] Searching for an exact resolution with a 3:2 pulldown refresh rate
2023-06-30 19:25:35.030 T:3061 debug <general>: [WHITELIST] No match for a resolution with a 3:2 pulldown refresh rate
2023-06-30 19:25:35.030 T:3061 debug <general>: [WHITELIST] Searching for higher resolutions with the exact refreshrate
2023-06-30 19:25:35.031 T:3061 debug <general>: [WHITELIST] No match for a higher resolution with an exact refresh rate
2023-06-30 19:25:35.032 T:3061 debug <general>: [WHITELIST] Searching for a desktop resolution with an exact refresh rate
2023-06-30 19:25:35.032 T:3061 debug <general>: [WHITELIST] Matched a desktop resolution with an exact refresh rate 1920x1080 @ 50.00 - Full Screen (16)
2023-06-30 19:25:35.032 T:3061 info <general>: Display resolution ADJUST : 1920x1080 @ 50.00 - Full Screen (16) (weight: 0.000)
Thank you for the information.
Unfortunately this happens with an empty whitelist as well. As there is no entry for 3840/2160 @ 50Hz it does not seem possible to watch UHD TV in full scale with vero4k+.
Michael
.
It might help to see the logs again, with an empty whitelist being set.
Right, that is the issue. What happens if you plug it directly into your TV, does 4K@50hz show up then?
No need, Kodi isn’t seeing the mode in question. The default whitelist is going to act the exact same way in this particular instance.
Thank you for pointing me in the right direction. Connecting vero4k directly to the TV works. Both media are played at the correct scale of 3840/2160.
So the culprit is my Denon A/V Receiver and NOT vero4k.
Thanks again, I’ll have a word with the Denon guys.
Michael
It could be that your AVR doesn’t support that much bandwidth. It could also be that there is an option that you have to enable in the AVR’s menus. If not supported there is still a possibility that you can get away with it anyway with a bit of tweaking, but I would look into if your AVR is actually claiming support for 4K@>30hz.
Make sure the Denon is plugged into a socket on your TV that has ‘full fat’ HDMI enabled.
Not relevant to your issue, but you should set ‘Use limited colour range’ ON.
@grahamh: Why would I want to use a limited colour range, as I own an OLED-TV black would not be black anymore.
That setting probably doesn’t quite mean what you think it means…
“Limited” is the format that virtually every video is stored in and that the TV expects to receive. If you output full range then, at best, the source will have to convert from limited to full and the TV will convert it back again - which will likely introduce subtle colour and luminance errors - and at worst you may even lose near-blacks and near-whites entirely.
The only displays that expect a full-range signal are things like computer monitors - devices that are primarily designed for use with a PC. They often prefer RGB rather than YUV as well. For a domestic TV you want limited YUV.
Thanks to everyone for their help.
Michael