[RPi5] 4K/60Hz on LibreELEC 12.0.1

    Ok...My AVR is plugged into HDMI port 2 on the TV -- the ARC port. I plugged the Pi into HDMI port 1, and the TV detected it as a "PC". But I was able to go into the "Source" menu on the TV and change the type to "Home Theater System". That allowed me to keep the calibration settings that I want. That setting appears to persist across a boot or power cycle of the Pi. So all good so far.

    However, Kodi still doesn't show the 2160x3480 60 Hz option in the Whitelist settings -- only 30 Hz. That may be due to the cable I'm using. (It's pretty new, but I'm not sure it's HDMI 2.0 certified.) I'll try again with the HDMI 2.0-certified cable that I have on order. It should be here in about 10 days.

    Problem solved -- I think!

    I enabled "Input Signal Plus" on both ports in the TV settings, and rebooted the Pi. Now it goes to 2160X3480 60Hz in Kodi.

    So, the solution is:

    1. Connect the Pi's HDMI port directly to HDMI port 1 on the TV.
    2. Connect the AVR to HDMI port 2 (ARC port) on the TV and enable ARC on the AVR and TV.
    3. After the TV detects the Pi as "PC", open the "Source" menu on the TV and change the type to "Home Theater System".
    4. Reboot the Pi and add 2160x3480 60Hz to the Whitelist in Kodi.

    Thanks again for all the input! You guys are the best!

    Edited once, last by rkershenbaum: Merged a post created by rkershenbaum into this post. (January 7, 2025 at 4:19 PM).

    Quote from Da Flex

    I think you should try that. We have reports on the forum that different HDMI ports act differently. Usually the first HDMI port of the TV is the most capable one.

    This led me to the solution. See above.

    Only downside is that the AVR's OSD doesn't display on the TV, since it's connected to the unused (except for ARC) port on the TV.

    So it would be slightly preferable to go back to the original setup, with he Pi connected through the AVR -- if I can get 4k60hz that way. I'll try it with the new HDMI 2.0-certified cables when they arrive.

    Edited once, last by rkershenbaum (January 7, 2025 at 4:53 PM).

    Quote from Da Flex

    Yep, the AVR definitely adds some data.

    Yes - the AVR has to add the audio formats it adds support for in an additional EDID block (so that sources know that the AVR+Display sink combo now supports True HD, DTS HD MA etc. and not just the audio formats the TV supports). It can also add data with the AVR name.

    A common problem with early '4K' compatible AVRs is that they only support the low (HDMI 1.4-compatble) bandwidth 2160p50/60 modes with 4:2:0 (which the Pi can't support) OR you have to enabled 'Enhanced HDMI 4:2:2' or similar to allow the high bandwidth modes to be added.

    AIUI some AVR+TV combos will remove formats the TV supports but that the AVR can't pass through from EDID in this situation.

    Also worth knowing that some TVs will go into 'PC' mode when they detect RGB rather than YCbCr (aka YUV - if you are happy to use UV incorrectly ;) ) sources - as most consumer equipment is YCbCr output, and most PCs are RGB output.

    Quote from Da Flex

    I think you should try that. We have reports on the forum that different HDMI ports act differently. Usually the first HDMI port of the TV is the most capable one.

    NB this isn't the case with a lot of Sony displays - particularly those in the early era of HDR UHD and Dolby Vision UHD support.

    On 4 HDMI input Sony models from that era (My XE/XF 9000 series for example), HDMI 1 and 4 are often low bandwidth (so only support 4:2:0 at 2160p50/60 which the Pi doesn't) with HDMI 2 and 3 having full-bandwidth support for 12-bit 4:2:2 at 2160p50/60. One of these is the ARC port which is the port you'd always use for an AVR (so you get TV->AVR audio back to the AVR via ARC)


    (4:2:0 2160p50/60 - at least at 8-bit - was added to the HDMI 2.0 specs as it was backwards compatible with HDMI 1.4 bandwidth connections so allowed old HDMI 1.4 physical hardware to carry 2160p50/60 video... )

    Edited once, last by noggin: Merged a post created by noggin into this post. (January 8, 2025 at 9:21 AM).