Universal Blue•5mo ago

Audio dropouts over HDMI (Rog Ally X / Bazzite)

Using most recent version of Bazzite on the Rog Ally X. I am experiencing audio dropouts / stutter over HDMI when docking to an external display, generally after sleep. It may be to do with the machine not recognising the display properly. From sleep the display settings still read as 'gamescope 7" display scaling', but after reboot whilst the machine is docked this correctly updates to 'gamescope 64" display'.

10 Replies

Chas_HodgesOP•5mo ago

Testing all morning, on my particular setup, ROG Ally X running latest Bazzite update (or any of the most recent builds which I tried rebasing to) audio is unusable over HDMI after waking from sleep. I've tried using the decky plug in 'pause games' which did not help, and I've poked around with a few different pulseaudio / pipewire settings reccomended online for similar issues. No good. There is a non-zero chance that one of the issues in my setup is my JSAUX dock. Trying an alternative dock may have alleviated the crackle and drop-outs. Need to test more tomorrow when I've got some more time, but it's food for thought anyway!

degen2k4•5mo ago

How's the audio sync? It's completely out of sync when I use HDMI on my ally via dock.

Potajito•5mo ago

Have you tried restarting pipewire after wake up? Could be a workaround

Chas_HodgesOP•5mo ago

This is still an issue. I replaced the dock I was using that was definitely adding its own issues with crackling and latency. The new dock seems fine, but I still get audio drops of less than a second every minute or so. Sleep doesn't seem to be the issue as from a cold boot it can exhibit the same problems. There's a chance it could be HDMI cables / TV as well, so I'm trying to scientifically test things one by one! In my current setup I've changed docks, and tested with no PSU, 65watts and 100watts - problem persisted each time I've moved things around just in case there was power interference in the melee of wires behind the TV

Potajito•5mo ago

Does it happen under load (aka games) or also uf you just play an MP3?

Chas_HodgesOP•5mo ago

sat on the home screen, under low load, or heavy load testing across devices in my house there's a good chance it's related to my main TV - I can't say for certain, but I wasn't able to reproduce the audio blips on my other screens whether on a cold boot or waking from sleep I've ordered new HDMI cables, but I think it might be connected to my samsung TV's stupid pass through box that all HDMI signals are routed through odd that it never presented any problems when using my Steam Deck before though - only started noticing it at the point I was using the Ally X with Bazzite, so the packet transfer over HDMI must be doing something slightly different via the Bazzite configuration

Potajito•5mo ago

You can up pipewire default quatum, cant link right now, Im on phone but it has helped me with sound issues in the past.

Chas_HodgesOP•5mo ago

What lower default shall I set? Will it introduce audio delay / latency? I found the config, just wasn't sure on the best values

Potajito•5mo ago

not lower at /home/user/.config/pipewire/pipewire.conf default.clock.quantum = 2024 default is 1024 and restart pipewire i also disable suspension editing /home/user/.config/wireplumber/wireplumber.conf.d/51-disable-suspension.conf with

monitor.alsa.rules = [
  {
    matches = [
      {
        # Matches all sources
        node.name = "~alsa_input.*"
      },
      {
        # Matches all sinks
        node.name = "~alsa_output.*"
      }
    ]
    actions = {
      update-props = {
        session.suspend-timeout-seconds = 0
      }
    }
  }
]
# bluetooth devices
monitor.bluez.rules = [
  {
    matches = [
      {
        # Matches all sources
        node.name = "~bluez_input.*"
      },
      {
        # Matches all sinks
        node.name = "~bluez_output.*"
      }
    ]
    actions = {
      update-props = {
        session.suspend-timeout-seconds = 0
      }
    }
  }
]

monitor.alsa.rules = [
  {
    matches = [
      {
        # Matches all sources
        node.name = "~alsa_input.*"
      },
      {
        # Matches all sinks
        node.name = "~alsa_output.*"
      }
    ]
    actions = {
      update-props = {
        session.suspend-timeout-seconds = 0
      }
    }
  }
]
# bluetooth devices
monitor.bluez.rules = [
  {
    matches = [
      {
        # Matches all sources
        node.name = "~bluez_input.*"
      },
      {
        # Matches all sinks
        node.name = "~bluez_output.*"
      }
    ]
    actions = {
      update-props = {
        session.suspend-timeout-seconds = 0
      }
    }
  }
]

but thats probably more to do with my hardware

Chas_HodgesOP•5mo ago

what hardware are you using? will try some of this later Tested my unit on a 4k screen at a family member's house - no drop outs, so I think I can confirm this is not a bazzite issue at this stage Just some weird issue with my primary TV unfortunately

Gaming

Programming

Audio dropouts over HDMI (Rog Ally X / Bazzite)