kubaszym1

[kubaszym1]

Hi,

Unfortunately we couldn’t reproduce your issues in our labs. Although there is a chance that your audio drivers prevent audio processing the way NoMachine tries to do it. In order to work around it, you can install manually NoMachine Audio Adapter. Please make sure that it’s set as the default device during the session (it should be set automatically). I link you an article about how to install and configure NoMachine Audio Adapter.

https://kb.nomachine.com/AR04T01159

Regards,

Kuba

[kubaszym1]

Hi,

So you tried to switch to a built-in device and it was reset automatically to NoMachine Microphone Adapter? On the print screen that you just sent I see that the adapter is still set as default. Does it set itself at the start of the session?

I’m not sure if I understood you well, do you connect from Windows to Linux or from Linux to Windows? What are your audio settings on Manjaro?

It may also happen because of some internal errors. Can you send us the session logs? Here’s how you can gather them:

https://kb.nomachine.com/DT07S00244

Regards,

Kuba

[kubaszym1]

Hi,

If I understand you well, you connect from Windows to Manjaro. In this case, NoMachine Microphone Adapter shouldn’t be set as default. It’s a virtual device that we use to process voice data but only when the machine works as a server. Unfortunately there is a chance that it was set as the default speaker during the installation – we try to handle such situations but maybe it didn’t work in your specific environment. If that’s the case, just switch to your built-in device on Windows before creating NoMachine session.

Meanwhile, I will check if setting NoMachine Microphone Adapter as default during the installation is common on Windows 11.

Regards,

Kuba

[kubaszym1]

Hi,

For your information:

– NoMachine Audio is a virtual speaker, so it’s okay that it set as default.

– NoMachine Output is created as a speaker but it’s used for processing voice data.

– Remapped NoMachine Output Monitor is a remapped source of NoMachine Output and it serves as a microphone for the user. It has to be this way in order to collect and transfer voice data properly. It’s okay that it’s the only selectable microphone in the virtual session

Now, in order to enable voice recording inside a NoMachine session, you need to click up-right corner of the session window to open the session settings. Then go to “Mic in” and click “Enable mic”. At this point voice recording should work.

If you did this step and voice recording doesn’t work for you, we will investigate further.

Regards,

Kuba

[kubaszym1]

Hi,

Thank you for your feedback.

I made a fix for this issue in our codebase, it will be available in the next release.

Best regards,

Kuba

[kubaszym1]

Hi,

For now I can’t tell much but I managed to reproduce this issue on Ubuntu 24. It seems that there are some problems with unmuting PGA channels. We will investigate further.

For your information, NoMachine doesn’t mute audio using pipewire API. Instead, we use amixer functionalities to mute/unmute audio. Otherwise we wouldn’t be able to capture audio properly.

You can try to fix manually but I’m not sure of the effect:

1) ls /dev/snd | grep controlC

example output: controlC0 – 0 is your card id

2) amixer -c <card-id> controls | grep “Playback Volume”

output: the channels to mute/unmute, i.e. numid=9,iface=MIXER,name=’Master Playback Volume’

3) example: amixer -c <card-id> cset numid=9 100% unmute

It should unmute numid 9 and set its volume to 100%. If you unmute all PGA channels this way, does the sound come back?

Best regards

Kuba

[kubaszym1]

Hi,

Please let me ask you a few questions so I can investigate your issue more efficiently.

Do you use the latest version of NoMachine (8.14.2)? If not, please upgrade to NoMachine 8.14.2.

Do you connect to the physical display or to the virtual desktop?

Do you mean that you don’t have any sound on your host immediately after installing NoMachine? And it doesn’t appear when you disconnect from the NoMachine session? Is the sound just constantly muted or is the entire audio system broken (that you don’t see any audio devices in the settings etc.)?

There’s a small chance that you experience some internal pipewire issues. Sometimes it’s enough to restart audio services:

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

You can also check the status of pipewire server:

systemctl --user --now status pipewire.service

Normally the sound should be muted on the server side during NoMachine session and after you disconnect it should unmute automatically. You can also unmute audio on the server during the connection. Click on the top-right corner of the NoMachine window to enter the session settings and then: Audio -> Change Settings -> Mute audio on the server.

Regards,

Kuba

[kubaszym1]

Hi,

Since you have a headless windows it’s possible that your audio service is off by default. Did you check your audio configuration? NoMachine ususally needs a physical audio device for capturing audio. Sometimes it’s necessary to use NoMachine Audio Adapter – in case your audio driver doesn’t support some of the functionalities that NoMachine needs.

Do you mean that normally (outside NoMachine session or using other remote desktop apps) audio devices show up on the Output/Input list? Does NoMachine cause that some devices disappear? Does the sound transfer correctly from your windows server to the client when you set NoMachine Audio Adapter as the default device?

Best regards

Kuba

[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

[Author]

Posts