kubaszym1

[kubaszym1]

Hi,

It seems that you experience an issue that is specific for Arch-based platforms. If you open NoMachine application from the tray and then connect to a server, the list of audio devices doesn’t load, so you can’t hear sound from the server. Try opening NoMachine with a command (/usr/NX/bin/nxplayer) and then  connect to your server and check if there’s sound during the session.

I hope this will help to solve your issue.

Regards,

Kuba

[kubaszym1]

Hi,

It seems that NoMachine doesn’t mute HDMI speakers properly. Do you only have HDMI speakers? There can be two reasons:

1) It used to work better in the past and muting controls with “Playback Volume” in their name was enough.

2) Muting HDMI causes issues with streaming audio data to the client machine. The relation between different speakers, ALSA, and pipewire/pulseaudio is a bit complicated. For certain speakers, i.e. bluetooth headphones, you can’t mute the device and stream audible audio data to the client at once becasuse of linux audio architecture. Maybe it’s similar for HDMI.

If you mute the HDMI speakers manually, does it interrupt streaming audio to the client or you can still hear the audio from the server on the client?

Regards,

Kuba

 

[kubaszym1]

Hi,

I investigated the logs you send and everything seems fine there – NoMachine process shows that it successfully muted your sound card. I only see one sound card there in the logs, but to ensure you can run this:

ls /dev/snd | grep controlC

in order to list your sound cards.

Here’s the list of controls in your sound card: [numid=33%%60-numid=9%%87,87-numid=68%%255,255-numid=14%%0,0-numid=1%%87,87-numid=3%%87,87-numid=5%%87-numid=6%%87-numid=16%%0,0-numid=12%%0,0]. You can use it to manually mute your sound card. I’d like to ask you to do it, in order to check if the issue is related to our script or directly to the amixer command. So the command is:

amixer -c 0 cset numid=<numid> 0%

If you call the command above for all numids, the sound should be muted. If it works, then I’ll try to investigate why it doesn’t work for you when called from our script.

Regards,

Kuba

[kubaszym1]

Hi,

We will try to reproduce your issue on our computers. I looked at the logs you send but I need to investigate it more deeply. For now I can give some hints and also ask some questions that will help investigate your issue.

1) NoMachine uses alsa functionalities to mute/unmute sound during session, so your ubuntu should have alsa installed in order work correctly with NoMachine. I found a case that may be similar to yours: https://askubuntu.com/questions/1511648/audio-not-working-ubuntu-24-04

2) I saw that you tried to list all you audio devices. It failed because you used pacmd (a command specific to pulseaudio). Instead you can use “pactl list sinks short” or “pw-cli ls Node” for more detailed info. Although NoMachine does not mute audio devices – it mutes the whole sound card, that’s why we need to use alsa functionalities. We need it like that, so we can stream data with having the server muted at the same time.

3) The issue may be caused for two main reasons: NoMachine’s muting script didn’t work or it wasn’t run at all because of some problems in the higher layer.  Can you check if unchecking and then checking the ‘Mute audio on the server’ option again actually mutes sound on the server?

Regards,

Kuba

[kubaszym1]

Hi,

It seems that there are some issues with audio configutation on your Linux machine. Can you show the output of the “pactl info” command? The first line should be “Server String: /run/user/1000/pulse/native”. Please check if directory “/run/user/1000/pulse” exists on your Linux machine. If it doesn’t, please try to find if you have a directory somewhere with pulseaudio socket in it. You can also check the value of environment variable XDG_RUNTIME_DIR. The pulseaudio socket will probably be placed in XDG_RUNTIME_DIR/pulse/native.

Regards

Kuba

[kubaszym1]

Hi,

We are still investigating your issue. Can you please send us the logs again? Since you use pulseaudio, the logs should be significantly different than before. Also, can you show us the output of the command “pactl info”? Can you also check what was your version of pipewire?

Regards,

Kuba

[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

[Author]

Posts