1080p or 4k: either or, but not both!

[m0ar]

Hi,

Long time OSMC user, but I have an issue that keeps coming back to haunt me. Hoping y’all are able to help me

Hardware:

• Host: Rapberry PI 4B (4GB)
• TV: Samsung Q60t (65" 4k)
• AVR: Yamaha RX-V685

Issue:
a) I see stuttering in some 1080p playback, which I can kinda solve by whitelisting the 1080p resolution/framerates.
b) if I do the above, I break high-bitrate 4k playback, and I have no idea why!

When either works, they work flawlessly. Full size blueray remuxes with HDR + dts/atmos are fine without the pi breaking much of a sweat. But I have a hard time finding a configuration that doesn’t break something.

I have played the same file I’ve used in the logs below recently, without any problems. Same situation with other known good material.

Here is a solid debug info dump, including:

• debug logs from a garbled 4k playback
• modeinfo
• mediainfo for the 4k file
• kodi settings
• a config diff that I think broke 4k but made all 1080p stutter free (maybe don’t focus so much on this, might be a red herring)

Any help would be hugely appreciated Let me know if there is any other information that is needed to get to the bottom of this!

[Tom_Doyle]

Hi,

I suggest reading this guide by @angry.sardine:-

[HowTo] Guide to the Kodi whitelist function and related settings

Platforms: Vero 4K and 4K+, Raspberry Pi 2 and 3. Applies to OSMC v18.x and 19.x I would like to cover the Pi 4 as well, but I don’t possess one; if others would like to research it for me, feel free! I also do not possess a Vero V. If anyone would like to buy me one, please go ahead! I haven’t yet had the chance to evaluate any changes to the whitelist in Kodi v20; for now, assume it works the same way as Kodi v19. Introduction This is a guide to the Kodi whitelist featu…

Regards Tom.

[m0ar]

Hi Tom,

I have done that, but I did another pass and changed my menu resolution which was at 4k/24. Otherwise, I think I’m following all recommendations in there.

Still, no dice. Was there something in particular you noticed? Note sure where to go from here.

The logs show selection of the right whitelisted resolution and frame rate. Any other ideas?

Best regards,
Edvard

[Tom_Doyle]

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:

[m0ar]

Hey Tom, you can find this linked in my initial post

[fzinken]

@m0ar

you can find this linked in my initial post

I only can find one link but that is not a complete OSMC log

[m0ar]

What do you mean? There are multiple files in the link, where one is a long segment from the debug log from start, play, through stop of broken playback.

[ActionA]

grab-logs -A

[fzinken]

@m0ar

What do you mean? There are multiple files in the link,

OSMC Debug logging collects logfiles including kernel logs and EDID details in a collective manner and will make analysis by the team much easier.