Having issues with getting my sound bar detected on UZdoom

[axredneck]

... and having to use pavucontrol to move the output every time you run the game is hardly good...

For me it remembers the device permanently if "Default" device is selected in app's (e.g. UZDoom's) settings.

[Chris]

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:

[...] 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]

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:

[...] 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.

Done. I sent you a private message. Let me know when you read it.

[Chris]

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.

[TurkmentbashiB]

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.

Hmmm. Does this mean that UZdoom only works with Pipewire or that Pavucontrol is conflicting with it.

[Chris]

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.

[TurkmentbashiB]

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.

Any edit I can make to fix that? Surely it's a bug on Pirewire's end. Must be something that could be done.

[Chris]

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]

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.

Took a look after the command line. This is the results(if there's nothing more that can be done, I won't hold it against you).

saga-0-1@saga-0-1-B760M-Pro-RS-D4:~$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 3598
Tile Size: 65472
User Name: saga-0-1
Host Name: saga-0-1-B760M-Pro-RS-D4
Server Name: pulseaudio
Server Version: 17.0
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.usb-Dell_Dell_AC511_USB_SoundBar-00.analog-stereo
Default Source: alsa_input.usb-Dell_Dell_AC511_USB_SoundBar-00.analog-stereo
Cookie: 23ca:dc83
saga-0-1@saga-0-1-B760M-Pro-RS-D4:~$

[Chris]

It looks like you are running native PulseAudio for some reason. As far as I know, Ubuntu switched to PipeWire by default in 22.10, so I'm not quite sure why PulseAudio would be installed and running for you, unless it's an old installation that's been upgraded over time and it's just never been removed. There are some things I could suggest to try, but it depends on how comfortable you are managing installed packages. If you're not too keen on removing the pulseaudio package, or know what's needed to ensure you have PipeWire's compatibility layer installed, it may be a good idea to ask on the Ubuntu forums about PulseAudio possibly conflicting with PipeWire over that device, and how to properly get rid of native PulseAudio in favor of PipeWire.

[Guest]

Chris wrote:
> It looks like you are running native PulseAudio for some reason. As far as
> I know, Ubuntu switched to PipeWire by default in 22.10, so I'm not quite
> sure why PulseAudio would be installed and running for you, unless it's an
> old installation that's been upgraded over time and it's just never been
> removed. There are some things I could suggest to try, but it depends on
> how comfortable you are managing installed packages. If you're not too keen
> on removing the pulseaudio package, or know what's needed to ensure you
> have PipeWire's compatibility layer installed, it may be a good idea to ask
> on the Ubuntu forums about PulseAudio possibly conflicting with PipeWire
> over that device, and how to properly get rid of native PulseAudio in favor
> of PipeWire.


Could rmoveing Pulse Audio be the answer. Will that instantly fix this?

[Chris]

For anyone else reading, they managed to fix the issue by uninstalling pulseaudio (which was conflicting with PipeWire) and installing pipewire-pulse, then after rebooting, their sound bar started working with PipeWire (thus OpenAL/UZDoom).