Other devices (HDMI audio, Built-in laptop speakers, headphones plugged into audio jack, and specifically the similar Behringer U-Phoria UMC22 device) are unaffected. No issues when Sound Settings app is closed. I used a USB 3 hub to easily connect/disconnect the 22 device, but i was able to still reproduce the same behaviour with the 404 and 22 connected to my laptop's USB 3 and USB 2 ports respectively. This specific behaviour is demoed in the video. Incredibly, when I connect in my Behringer U-Phoria UMC22, a 2-channel I/O device, even when its not the active outputting device, the bug resolves itself on the 404 device. Note that once the bug is triggered, as long as that application is still trying to perform playback, trying to do I/O in the non-triggering applications also does not work. While I was mostly just able to test output, the input does still appear to be affected in the same manner (eg. Some applications trigger this bug (Youtube on Firefox, Rhythmbox), others do not (Youtube on Chromium, MuseScore 4).
Switching between these "broken" and "working" states, in both directions, the first time it attempts to play audio in the new state, I will hear some speaker "popping" noises.Ī lot of variables which causes the bug to occur or not In the other direction, while this bug is occurring, closing Sound Settings will cause playback to resume after a few seconds. Instead the bug takes place the next time audio is outputted (given a few seconds of silence in between audio playbacks). If audio is actively playing, launching Sound Settings will not immediately trigger this bug. a Youtube video will halt, being fully unable to play either audio or video. It's almost as if it chokes playing audio/video, it's not a simple sound muting, but e.g. Specifically when the Sound Settings app is open (even minimized), attempting to output to my USB Audio device, a Behringer U-Phoria UMC404HD (4-channel I/O) halts audio & video playback in some applications. Note the video demo is me recording my computer screen on a phone and giving commentary, because I tried using a screen recorder, but that altered the reproduction conditions of the bug! I've placed a video demo of the bug and what I thought might be relevant files (including inxi -Fxz output) here. I'm not sure about the right place to file it (it could be kernel, application, or Cinnamon level), so I figured I'd start here. I've got a bit of an integration nightmare bug and any help is very much appreciated.
0 kommentar(er)
