Welcome to the ZDoom Forums!

Chris wrote: Sun Jan 18, 2026 6:25 pm

TurkmentbashiB wrote: Sun Jan 18, 2026 2:42 pm Any edit I can make to fix that? Surely it's a bug on Pirewire's end. Must be something that could be done.

It would be something to ask the PipeWire devs about. I unfortunately don't know PipeWire well enough to say what could be keeping UZDoom/OpenAL and pw-dump from seeing the device, while other apps like pavucontrol can. Unless your system is running a native PulseAudio server and a native PipeWire server at the same time for some reason rather than using PipeWire's PulseAudio compatibility layer, which could prevent PipeWire from using the device, but even then I'd expect PipeWire to still at least see the device. You can check the output of

Code: Select all

$ pactl info

and it should contain a line like Server Name: PulseAudio (on PipeWire 1.4.9) to indicate it's using PipeWire's compatibility layer (the version number may be different, but as long as it says "on PipeWire" it's fine). Other than that, I can only think it's a permissions issue, PipeWire being configured to not allow certain apps from knowing the device is there, which you'd have to ask someone more knowledgeable about PipeWire's permission restrictions to change it.

TurkmentbashiB wrote: Sun Jan 18, 2026 2:42 pm Any edit I can make to fix that? Surely it's a bug on Pirewire's end. Must be something that could be done.

$ pactl info

Chris wrote: Sat Jan 17, 2026 1:16 am UZDoom works with PipeWire, PulseAudio, ALSA, and various other audio systems (or really, OpenAL works with them, which is what UZDoom uses for audio mixing/output). It will automatically use what's available on the system, which in your case is PipeWire. There shouldn't be any problems with pavucontrol, it's just PipeWire not telling some apps about the device for some reason.

Chris wrote: Fri Jan 16, 2026 7:55 pm I read it, thanks. This is very odd. There doesn't seem to be any sound bar device described in the log, the only mention of one is the metadata tags for "default.configured.audio.sink" and "default.configured.audio.source" (which is the user-configured default device values, separate from "default.audio.sink" and "default.audio.source" as the actual defaults that specify the HDMI device). There's no other mention of SoundBar or Sound Bar or AC511 anywhere. This may be something to ask the PipeWire devs about, as I have no idea why it would up show in pavucontrol, but not be listed in pw-dump or other apps like UZDoom/OpenAL. The only thing I can think of is some permission settings preventing certain apps from being told about it, but I'd expect at least pw-dump to have those permissions. I don't know where such permissions would be set/configured either, to be able to suggest where to look.

Chris wrote: Fri Jan 16, 2026 4:35 pm

TurkmentbashiB wrote: Fri Jan 16, 2026 3:30 pm What info would you need? Is there a way to create a log on the game launching?

I'd need the output of pw-dump, as I said in my previous response:

Chris wrote: Thu Jan 15, 2026 6:09 pm [...] I might need the output of pw-dump to see what information PipeWire itself has. Be aware that this will contain information about active audio and video streams, and various devices and apps running on your system, so if you're concerned about anything like that in a public log, feel free to send me a private message with the log attachment. You can make the log by running this in a terminal:

Code: Select all

$ pw-dump > pipewire.log

and it will create a pipewire.log file with the info.

TurkmentbashiB wrote: Fri Jan 16, 2026 3:30 pm What info would you need? Is there a way to create a log on the game launching?

Chris wrote: Thu Jan 15, 2026 6:09 pm [...] I might need the output of pw-dump to see what information PipeWire itself has. Be aware that this will contain information about active audio and video streams, and various devices and apps running on your system, so if you're concerned about anything like that in a public log, feel free to send me a private message with the log attachment. You can make the log by running this in a terminal:

Code: Select all

$ pw-dump > pipewire.log

and it will create a pipewire.log file with the info.

Chris wrote: Fri Jan 16, 2026 1:56 pm... and having to use pavucontrol to move the output every time you run the game is hardly good...

Chris wrote: Fri Jan 16, 2026 1:56 pm

axredneck wrote: Fri Jan 16, 2026 12:53 pm Look at "Playback" tab:

That's not a good solution, since OpenAL will likely just open the HDMI device again next time if it's not seeing the sound bar device, and having to use pavucontrol to move the output every time you run the game is hardly good. It would be better for me to figure out why OpenAL isn't recognizing the sound bar as a valid output device so I can fix the issue and make it selectable properly.

axredneck wrote: Fri Jan 16, 2026 12:53 pm Look at "Playback" tab: