Posts by popcornmix

    I’m using the original cable included with the RPI. Tried to include”hdmi_force_hotplug=1“ in config.txt, but it doesn’t solve the problem.

    In general, hdmi_* lines in config.txt apply to deprecated firmware display driver.

    A more suitable line would be to add:

    Code
    video=HDMI-A-1:1920x1080@60D

    to the end of cmdline.txt (on the same line).

    For testing you can also try switching to the fkms driver. In /flash/distroconfig.txt change:

    Code
    dtoverlay=vc4-kms-v3d,cma-512

    to

    Code
    dtoverlay=vc4-fkms-v3d,cma-512

    Can you confirm that you have two displays that behave this way?

    One display that doesn't play nicely would be surprising, two seems very unlikely and may suggest an issue elsewhere (but your issue is not affecting the vast majority of users).

    Can you confirm you don't have a case with hdmi extenders?

    BTW. Maybe it could be useful for developers to have the edid files from not-working configurations to analyze.

    If i am not mistaken, the edid create saves the edid-HDMI-A-1.bin file to /storage/.config/firmware/edid/ folder (and also edid-HDMI-A-2.bin for devices with two HDMI ports like RPi 4B etc.).

    And it's possible to look what's there with:

    edid-decode /storage/.config/firmware/edid/edid-HDMI-A-1.bin

    I'm happy to receive edid files that cause a problem, but I think most issues are due to a lack of edid file.

    If the hdmi cable is missing hotplug, SCL or SDA lines (which cheap cables can do to save costs),

    then we can't read the edid.

    This issue can also be caused by the Argon One case which does a similar thing with cable extenders.

    Less common is a fault on display (worth trying different hdmi inputs, or a different display).

    You can run:

    Code
    edid-decode /sys/devices/platform/gpu/drm/card?/card?-HDMI-A-1/edid

    on a booted system (ssh in if display is blank). If you get lots of info about modes supported, then you have an edid.

    If you get an error, then we can't read the edid, and the only solution (apart from fixing the underlying issue) is editing config files.

    I think the simplest change to get a picture without an edid would be to add to end of cmdline.txt:

    Code
    video=HDMI-A-1:1920x1080@60D

    (or some other resolution you know the display supports).

    But note, without an edid, kodi won't know the range of refresh rates supported (for "adjust display refresh rate to match video"), and CEC and audio passthrough are unlikely to work fully.

    Basically I just want to have the best video and audio possible, as currently with using one HDMI port I am limited to the bandwidth of ARC (DTS, DD, 2.0 PCM). Today I used "getedid create" for the first time which ensures that the RPI also outputs video when the TV is turned on afterwards/later. Couldn't a custom EDID file be created which combines the max video settings of the TV and the max audio settings of the AVR? At least I imagine that the TV receives the correct video but cannot play the audio signal and the AVR receives the HD audio although the picture might not be correctly displayed as my AVR is not HDR compatible (only 4k) which I wouldn't care about.

    ARC doesn't support HD audio formats.

    (Note: there is a HDMI2.1 eARC standard that does, but it would need to be supported by TV and AVR, and I suspect they don't).

    Assuming you are connected as:

    Pi<---hdmi--->TV<---ARC--->AVR

    then fudging the EDID won't help. The ARC connection can't support it.

    If you can connect:

    Pi<---hdmi--->AVR<---hdmi--->TV

    Then HD audio should work.

    Using the second hdmi connector should be possible.

    Forget about config.txt hdmi_* settings - they apply to the old firmware display driver that is not longer used.

    Your symptoms suggest an issue with the edid.

    Run:

    Code
    edid-decode /sys/devices/platform/gpu/drm/card0/card0-HDMI-A-1/edid

    and check that produces output and contains an "Audio Data Block" section. Post output here.

    I've never heard of this issue. Possibly you have some invalid/corrupt settings?

    Can you try:

    Code
    systemctl stop kodi
    mv ~/.kodi ~/.kodi_back
    systemctl start kodi

    and then play the file? If it doesn't help you can put thing back:

    Code
    systemctl stop kodi
    rm -rf ~/.kodi
    mv ~/.kodi_back ~/.kodi
    systemctl start kodi

    (or if you have a spare sdcard, just check if a clean install has the issue).

    There are LE nightly Matrix builds which include some additional fixes from 10.0.2.

    Giving that a test might be useful.

    There are also LE 11 nightly builds which include even more changes (including a kernel bump from 5.10 to 5.15) which may be worth trying if previous build doesn't help.

    If these don't help then a way of reproducing this issue more quickly would be useful.

    Perhaps try with just a single video on loop. The shorter the video the better as issues tend to occur on startup/shutdown of the codec.