Posts by blueribb

    The audio did return after running the first code but the second code gave this result:

    LibreELEC (official): 9.2.0 (Generic.x86_64)

    LibreELEC:~ # cat >/storage/.config/sleep.d/99-toggle_rate.power <<'EOF'

    > #!/bin/sh

    > case "$1" in

    > post)

    > xrandr -display :0 --output HDMI1 --mode 1920x1080 --rate 59.94

    > xrandr -display :0 --output HDMI1 --mode 1920x1080 --rate 60

    > ;;

    > esac

    > EOF

    -sh: can't create /storage/.config/sleep.d/99-toggle_rate.power: nonexistent dir ectory

    LibreELEC:~ #

    Here's a debug log I uploaded earlier today. I started Kodi by waking my Intel NUC from Suspend and then enabled debug logging. There was NO audio. If I were to reboot the NUC, the audio would return. I did not reboot for the log below.

    Debug Log

    Here's the output of xrandr (no sound, wake from suspend):

    LibreELEC (official): 9.2.0 (Generic.x86_64)

    LibreELEC:~ # xrandr

    Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767

    DP1 disconnected primary (normal left inverted right x axis y axis)

    DP2 disconnected (normal left inverted right x axis y axis)

    DP3 disconnected (normal left inverted right x axis y axis)

    HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm

    1920x1080 60.00*+ 59.94 24.00 23.98

    1920x1080i 60.00 59.94

    1400x1050 59.95

    1280x1024 60.02

    1280x720 60.00 59.94

    1024x768 60.00

    800x600 60.32

    720x480 60.00 59.94

    720x480i 60.00 59.94

    640x480 60.00 59.94

    HDMI2 disconnected (normal left inverted right x axis y axis)

    HDMI3 disconnected (normal left inverted right x axis y axis)

    VGA1 disconnected (normal left inverted right x axis y axis)

    VIRTUAL1 disconnected (normal left inverted right x axis y axis)

    LibreELEC:~ #

    Here's the output of xrandr after a clean reboot (sound working):

    LibreELEC (official): 9.2.0 (Generic.x86_64)

    LibreELEC:~ # xrandr

    Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767

    DP1 disconnected primary (normal left inverted right x axis y axis)

    DP2 disconnected (normal left inverted right x axis y axis)

    DP3 disconnected (normal left inverted right x axis y axis)

    HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm

    1920x1080 60.00*+ 59.94 24.00 23.98

    1920x1080i 60.00 59.94

    1400x1050 59.95

    1280x1024 60.02

    1280x720 60.00 59.94

    1024x768 60.00

    800x600 60.32

    720x480 60.00 59.94

    720x480i 60.00 59.94

    640x480 60.00 59.94

    HDMI2 disconnected (normal left inverted right x axis y axis)

    HDMI3 disconnected (normal left inverted right x axis y axis)

    VGA1 disconnected (normal left inverted right x axis y axis)

    VIRTUAL1 disconnected (normal left inverted right x axis y axis)

    LibreELEC:~ #

    Thanks but that's just a little over my head. It looks like toggling to 50 and back to 60 in a script but that's about all I get out of your post. I would need basic instructions to attempt something like that. One thing that comes to mind is the pop-up message I got when changing the refresh rate manually the other night - it asked if I wanted to save the changes. If this script works, then what would happen to the pop-up question ?

    After a week dealing with this issue, I'm pretty sure my problem is with the NUC's resume from suspend and not a timing issue at all. I tried reaching out to Intel Tech Support but they shut me down saying my NUC is now obsolete and there is no further support. I wonder if the HDMI handshake waking from suspend is the same as a power on or reboot. I cannot power my NUC on from a full power down unless I press the NUC's power button. There is no remote control support for power on from this old NUC.

    I'm now shopping for NUC8i3BEK (2018 model) to replace my much older 2013 i5 NUC. I'll gain 4K support and the no sound issue should be fixed.

    Update: I found a work-around tonight. If I start my system in TV mode (Verizon Cable Box) and then switch to Kodi which wakes my Intel NUC from suspend, the sound works every time. I'm guessing the TV mode completes the hdmi handshake and EDID, which the new receiver remembers until it's shut off. I can switch between Verizon TV & my NUC and the sound remains, even though the NUC goes into SUSPEND when the TV mode is on.

    My guess is that the NUC's hdmi handshake / EDID signal or whatever is much stronger during POWER ON, than it is resuming from SUSPEND and that the new Yamaha Receiver is more sensitive to this. Maybe if I had chosen another brand of receiver, like Denon, I might not have this problem at all.

    Have you already tried a Custom EDID?

    Actually, I just finished my phone call with Yamaha Tech Support and the guy was very knowledgeable. He said it does sound like an EDID issue. I don't know anything at all about EDID, so any help would be greatly appreciated. In the meantime I am going to try a new HDMI cable, another HDMI input and then as Da Flex suggested - an HDMI Audio Splitter. I'll click the link supplied for Custom EDID above.

    Update: I connected my Intel NUC directly to my Sony TV (2009) using an HDMI cable. I then connected my Sony TV's Digital Audio output to my Yamaha Receiver. This fixed the HDMI handshake problem BUT I cannot leave it this way because of two new problems. First, the video is over-saturated with both contrast and color. And secondly (most important), my Sony TV does NOT pass HD Audio of any type. I guess the TV is just too darn old to handle HD Audio.

    I really don't want to buy a new Intel NUC and TV at this time. I'm going to call Yamaha Tech Support to see if they have a fix. Rebooting the NUC every time I want to use it is frustrating and a little time consuming.

    Could you describe your HDMI cabling please?

    If it's NUC -> receiver -> TV, then your new receiver might block (don't update) HDMI communication after suspend.

    Yes, the cabling is as you show. My 2009 Yamaha Receiver did not have this problem. My brand new 2019 Yamaha Receiver (same basic specs) has this problem. It's definitely an HDMI issue but I'm clueless as to how to fix it. For the meantime, I will reboot my NUC every time I use it.