kubaszym1

[kubaszym1]

Hi,

Here are the expected audio settings:

1) virtual session: default speaker: nx_audio_in, default microphone: nx_remapped_out

2) physical session: default speaker: built-in speaker or other device (headphones, monitor speakers etc. – in case there’s no physical device nx_audio_in is created). default microphone – nx_remapped_out

nx_voice_out shouldn’t be set as the default speaker because it is used for handling  voice. In the virtual session you shoudn’t see any devices other than NoMachine virtual devices (nx_audio_in, nx_voice_out, nx_remapped_out). What is more, nx_remapped_out is a remapped source based on nx_voice_out.monitor so if you set nx_voice_out as a speaker and nx_remapped_out as a microphone, there is a high possibility you will experience echo or other strange effects.

With this source, mic is configured correctly. I could record from a sound recorder software. I cannot hear recorded sound.

Do you mean hear that you cannot hear recordings made in a virtual session? You have nx_audio_in set as a default speaker which is typical for virtual sessions.

I navigate to settings’ interface. I update audio sink to another sink, External Monitor Audio.

Do you describe the behaviour in a physical session from this point? You shouldn’t be able to set External Monitor Audio in a virtual session.

Please let me also know if you are able to get the expected audio settings that I described above.

Best regards,

Kuba

[kubaszym1]

Hi,

Do you experience the same issues in virtual session? In a virtual session audio settings should be the same as in a custom session. PULSE_SERVER should be set to .nx/nxdevice/…/native.socket, you should see devices NoMachine Output and NoMachine Microphone.

PULSE_SERVER remains set to /run/user/1000/pulse/native only in a physical session.

Please check one more thing. You wrote that PULSE_SERVER was set to ‘/home/test/.nx/nxdevice/D-1001-72AD68BE3EE123C5F5E56100240CAE6E/audio/native.socket’. But ‘D-1001-…’ directory is usually used for handling devices in physical session, not virtual or custom sessions. For virtual and custom session directories like ‘D-1002-…’, ‘D-1003-…’ should be created (1002, 1003 are display ids). Maybe all sockets were created properly but PULSE_SERVER was set to a wrong path. Check if you have a native.socket in a directory ‘.nx/nxdevice/D-1002-…/audio’ when you create a new virtual/custom session. Then you can switch to a proper pulse server by changing environmental variable :

export PULSE_SERVER=~/.nx/nxdevice/D-1002-…/audio/native.socket.

After this step it’s possible that restarting pulseaudio service will be required.

Thank for your detailed description of the issue and I hope that my answer will help you somehow.

Regards,

Kuba

[kubaszym1]

Hi,

It seems that our software doesn’t recognize your audio devices. Can you show your sound settings? By default NoMachine client should play sound through your default device.

You can check the logs for warning and errors. The client connection logs will be on your client machine under .nx/R-<display>-<session-id>/session. In the meantime our testers will try to reproduce your issue.

Regards,

Kuba

[kubaszym1]

Hi,

We were able to reproduce a very similar issue on Manjaro and we are working on a solution. It seems that it is a specific issue on Arch-based distributions.

You said that pipewire or pulseaudio sockets are not under the paths that I suggested. Can you check under which path do you have pipewire/pulseaudio sockets and config files? That would help us solve the problem.

Regards,

Kuba

[kubaszym1]

Hi,

Let me ask you a few questions in order to help me reproduce and investigate your issue.

Which sound server do you use on your ubuntu? Ubuntu 22.04 should use PipeWire as default, but pulseaudio modules are also installed and you could switch to pulseaudio if you wanted to. You can check it by running ‘pactl info’. If “Server Name” simply says “pulseaudio” – you use pulseaudio. If “Server Name” is something like “PulseAudio (on PipeWire)” – then you use pipewire.

Did you uninstall the old package and then install the new one? Or did you do the upgrade directly from the NoMachine application? If you did the latter, you can check if uninstalling and installing will help. Just download the DEB package you want and run:

sudo dpkg -P <old_package_name> && sudo dpkg -i <new_package>.deb

If you want to restart PipeWire server you should run:

systemctl –user –now restart pipewire.{service,socket}

You can also check audio configuration in /usr/NX/etc/node.cfg. The variable “AudioInterface” should be set to “pipewire” if you use pipewire or “pulseaudio” if you use pulseaudio.

Regards,

Kuba

[kubaszym1]

One more thing – it’s possible that it’s caused by an issue found in some Arch-based distros. The workaround is:

1) In /usr/share/pipewire/pipewire-pulse.conf change:

pulse.properties = {
# the addresses this server listens on
server.address = [
//“unix:native” # -> this path is used by default
“unix:/var/run/pulse/native” # -> this path should be used for workaround

2) Create a symlink  /var/run/pipewire/pipewire-0 to /var/run/user/{uid}/pipewire/pipewire-0

Regards,

Kuba

[kubaszym1]

Hi,

There are several possible explanations of such issue. You mentioned that you checked NoMachine’s configuration and it seems fine – do you mean that AudioInterface in /usr/NX/etc/node.cfg is set to “pipewire”? If yes, you can also check if nxnode process belongs to the user who runs the session. Another thing to check can be the environmental variable XDG_RUNTIME_DIR – it should be set for nxnode process. You can check by running cat /proc/<nxnode PID>/environ.

Meanwhile we will try to reproduce your issue and investigate your logs carefully.

Regards,

Kuba

[kubaszym1]

Hi,

If you still experience this issue, please show us your connection and options log files. You can find them in .nx/R-<session_id>/ on the client side.

Unfortunately we haven’t reproduced the issue yet, audio during a connection between two Mint machines (both with NoMachine 8.11) worked fine. Our testing team keeps trying to reproduce it. Your logs from the connection would help us a lot.

Regards,

Kuba

[kubaszym1]

Hi,

I checked the file “no-sound-forwarding.txt” that you sent and your configuration seems to be fine, all the variables and devices are set properly. Something blocks the audio transfer completely, despite proper configuration. I will try to reproduce your issue and investigate further. In the meantime, can you send me the logs from both sides? You can check it how to do it here: https://kb.nomachine.com/DT07S00243.

Regards,

Kuba

[kubaszym1]

Hi,

Please try again using the commands exactly as they are above. I realised that they were formatted incorrectly, now corrected.

[kubaszym1]

Hi,

You can check if you have “Exclusive mode” set for your headset. Exclusive mode is a feature that allows an application to get exclusive use of an audio device. It’s possible that turning it on (or off) for the bluetooth headset will make a difference. Go to Sound Control Panel, open “Device properties” of your headset, then go to “Advanced”. Then you can check/uncheck “Allow applications to take exclusive control of this device” in order to turn on/off the exclusive mode.

Please let me know if you notice any difference during a NoMachine session.

Regards,

Kuba

[kubaszym1]

Hi,

Do you mean that the headset is connected to the windows machine (server) – you can hear audio from Windows with this headset outside the session? I know you wrote it but I want to be sure. Do you connect the headset before or during the NoMachine session?

If the bluetooth device is connected to the client machine, you should see it on the device list in NoMachine settings (click on right up corner of the NoMachine window, then go to Audio -> Change settings). You can set it as an output device on the client side.

But if your headset is connected to the server, we will try to reproduce the issue and fix it.

Regards,

Kuba

[kubaszym1]

Hi,

It’s also possible that something went wrong in configuration during the installation – you once wrote that you have AudioInterface set to “pipewire” but do you use PipeWire? In order to check, run:

pactl info

1) if Server Name is ‘pulseaudio’ then you use PulseAudio and AudioInterface should be set to “pulseaudio”. You can change this in /usr/NX/etc/node.cfg and then restart NoMachine server.

2) if Server Name is ‘PulseAudio (on PipeWire 0.3.x)’ then you use PipeWire and in this case I will have to investigate your issue in order to find out where the problem is.

Best regards,

Kuba

[kubaszym1]

Hi,

Your issue can be caused by several things. In order to determine if you’re using PulseAudio or PipeWire you can run this command:

pactl info

if ‘Server Name’ is pulseaudio – you use PulseAudio, but if it’s something like ‘PulseAudio (on PipeWire 0.3.x)’ – you use PipeWire. Then you can restart your audio service and hopefully the sound will return:

1) For PipeWire: systemctl --user --now restart pipewire.{socket,service}

2) For PulseAudio: systemctl --user --now restart pulseaudio

In some cases you may need to restart your computer.

Regards,

Kuba

[kubaszym1]

Hi,

PULSE_SERVER should be set automatically to /run/user/<uid>/pulse/native/. If it’s not set properly, the sound won’t work even outside NoMachine session. You can check it’s value by running ‘pactl info’ (first line of the output). This command may crash because you have some issues, so you can also just set PULSE_SERVER manually – ‘export PULSE_SERVER=/run/user/<uid>/pulse/native/’. Then please restart pulseaudio server.

If you experience these sound issues only during NoMachine session you can gather logs from the session and send it to forum[at]nomachine.com. Collecting logs: https://kb.nomachine.com/DT07S00243

Best regards,

Kuba

[Author]

Posts