State of Pipewire support

[Tromegan]

Hi All,

Searching through the forum I found several mentions of Pipewire and NoMachine not having support for it. In one of the threads it was mentioned that pipewire support was to come with 8.x. Is there any update on the topic? Any way to make NoMachine work properly with Pipewire audio?

 

Thanks!

[Britgirl]

Hi, Pipewire is supported in physical desktop sessions at the moment.

See my comment here: https://forums.nomachine.com/topic/no-sound-with-pipewire-and-el9#post-41530

[Tromegan]

Thanks @Britgirl for your response – is there any documentation on how to get it to work? I am connecting to a physical session, and I do have sound locally, but not via NoMachine..

[Britgirl]

Sorry I forgot to include the link to our article in the KB. Try the tips here and let us know 🙂

How to enable audio on systems relying on PipeWire for sound
https://www.nomachine.com/AR07T01168

[Tromegan]

Hm.. Thanks for the link, but it doesn’t really have anything on how to get pipewire to work.. Maybe I am missing something – it seems to be more focused on “temporary solution for virtual desktop cases” – like what should be set in node.cfg for Pipewire to work? I have “pulseaudio” there – is that right? I have: AudioInterface pulseaudio, EnableAudio 1 and CommandStartPulseAudio “” – is that right?

 

[Britgirl]

What exact version 8 do you have installed and on which Linux distribution?

You could try editing /usr/NX/etc/node.cfg and set:

AudioInterface alsa

and restart the nxserver:

sudo /etc/NX/nxserver –restart

[Tromegan]

My server is Gentoo Linux with NoMachine 8.4.2 and my client is Windows 11 and also 8.4.2

My config is like the following:

# grep Audio ../../etc/node.cfg
AudioInterface alsa
EnableAudio 1
# Specify path and name of the command to start PulseAudio server.
CommandStartPulseAudio “”

and attached is the nxserver log I am getting…

[Britgirl]

Hi, can you send the logs from the server to forum[at]nomachine[dot]com please? Please use the title of the topic as the subject of your email.

[Tromegan]

Done – should be there..

[Britgirl]

Hi, we got the attachment but it was not complete. You sent us one file from the directory and it didn’t include the ~/.nx/node folder. Can you zip up everything and send it again? Thanks!

[Tromegan]

Sorry, my bad – now sent both – userdir and full set of NX server logs as per documentation.

[kubaszym1]

Hi, I analyzed the logs you had sent. For some reason NoMachine is trying to connect to pulseaudio instead of pipewire. Can you check if you have pactl and/or pw-cli commands installed? If you have pactl installed, please run pactl info. If PipeWire is used, there should be a line like this:

Server Name: PulseAudio (on PipeWire 0.3.x)

If pulseaudio is used, it will look like this:

Server Name: pulseaudio

Also, don’t worry that you have AudioInterface pulseaudio. This is right for your current version. What is more, CommandStartPulseAudio is used only for virtual sessions.

[Tromegan]

I do have pactl:

user@host ~ $ which pactl
/usr/bin/pactl
user@host ~ $ LC_ALL=C pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 178572
Tile Size: 65472
User Name: user
Host Name: host
Server Name: PulseAudio (on PipeWire 0.3.63)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_00_1f.3.analog-stereo
Default Source: alsa_input.pci-0000_00_1f.3.analog-stereo.2
Cookie: 83e0:ae3e

[Tromegan]

Any update on this topic? Anything else I can provide to help figuring this out? Something else I should try?

[Bilbotine]

Hi Tromegan,

You can check the article “How to enable audio on systems relying on PipeWire for sound” (here: NoMachine – How to enable audio on systems relying on PipeWire for sound – Knowledge Base)

We support it on physical desktop but not yet on virtual desktop.

[Author]

Posts