kubaszym1

[kubaszym1]

Hi Silvo,

It seems that everything works fine. Let me explain how our audio support works on Linux:

When you connect to a physical display, NoMachine captures audio from the default speaker (you can check the current default speaker system settings). If you want to forward microphone from your client machine to the remote desktop, you need to click “Mic in” in nxplayer settings (as you did). Then the audio data will be transferred to NoMachine Output (you can see this device as a speaker, but please don’t set it as default, it’s only for collecting voice data) and then recorded by Remapped NoMachine Output (it can also be called NoMachine Microphone) that should be set as the default microphone when you want to record something through the remote desktop.

To sum up, in order to forward microphone from the client machine and record something on the remote machine, you need to:

1) Click “Mic in” in the session settings

2) Ensure that NoMachine virtual device is set as the default microphone (you should have it set automatically during the connection)

After that you should be able to record whatever you want. Just open a recording app on the remote machine and speak to your local microphone.

Best regards,

Kuba

[kubaszym1]

Hi,

I’ve read the logs you send, but unfortunately I didn’t find anything that would suggest where the problem was. Can you send a sample of bad playback from Avid? It will be easier to investigate if I know how it sounds.

It’s possible that it’s the Avid’s fault. Please check if there are known Avid’s issues with remote desktops.

I will look at your logs once more, hopefully I’ll find out some more information.

Regards,

Kuba

[kubaszym1]

Hi,

I need some information in order to investigate your issue.

Which sound server do you use on each side? I see that you use PulseAudio from pactl info but you also have PipeWire server. I need to know which one works on each side (server and client).

Did the update to NoMachine 8.9 change anything? We fixed some issues related to PulseAudio in NoMachine v8.x, the audio and voice transfer should work well. If the audio or voice still breaks, I will have to check it again.

I also noticed that you probably connect to a virtual session (since you have nx_audio_in set as the default device). Do you experience the same issues on physical session as well?

Best regards,

Kuba

[kubaszym1]

Hi,

In the NoMachine session the  default voice device should be NoMachine Microphone Adapter and the default audio device should be one of your audio devices. If NoMachine Microphone Adapter sets automatically as the default speaker, please let us know so we can fix this issue.

On several Windows machines audio drivers don’t allow capturing raw data – in that situation NoMachine receives only processed data (i.e. muted data). We mute the server by default, so if your audio driver doesn’t send us raw data, then we are not able to play sound on the client.

Fortunately, there is a simple workaround for your issue. You can install manually the NoMachine Audio Adapter and set it as the default device when using NoMachine. Please follow the steps from this article: https://kb.nomachine.com/AR04T01159?s=nomachine%20audio%20adapter

Regards,

Kuba

[kubaszym1]

Hi,

As far as I understand, you are still using pipewire sound server. You can just try to restart it this way:

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

Please pay attention to the output of command “pactl info”. Server String should be /run/user/1000/pulse/native and Server Name should be PulseAudio (on PipeWire 0.3.x). If the Server String is not set properly, you can set it manually this way:

export PULSE_SERVER=/run/user/1000/pulse/native

You are probably using WirePlumber as your session manager. You can check if it runs properly by running wpctl status. In the output you should see something like this:

Settings
└─ Default Configured Node Names:
0. Audio/Sink    alsa_output.pci-0000_00_1b.0.analog-stereo
1. Audio/Source  alsa_input.pci-0000_00_1b.0.analog-stereo.37

If no sinks are set as default, you can set them this way:

wpctl set-default <node-id>

You can see the node ids in the Audio Sink/Sources section of the “wpctl status” output.

Regards,

Kuba

[kubaszym1]

Hi,

I would like to order things up to determine whether the bug is in Ubuntu or in NoMachine. If I understand correctly, the audio doesn’t work at all after NoMachine installation. Is it impossible to set it again from system settings? Have you tried restarting pulseaudio or alsa? It seems very strange that the sound is broken even if NoMachine is disabled. Even if the sound from the HDMI speaker is broken, you should be able to hear the audio from the default speaker (built-in device in your laptop). Have you tried to achieve working sound with another speaker (i.e. headphones?). You can uninstall NoMachine, restart your computer and check if that changes something. Also, I found a possible way to deal with such issues on Ubuntu although I’m not sure if it’ll work for you:

sudo nano /etc/default/grub

Change:

GRUB_CMDLINE_LINUX=”” to GRUB_CMDLINE_LINUX=”intel_iommu=on,igfx_off”

Save file and update grub:

sudo update-grub

reboot

If you use NVIDIA drivers, you may need to update them. Go to Software & Updates -> Additional Drivers and check if an update for NVIDIA drivers is available.

Regards,

Kuba

 

[kubaszym1]

Hi,

I found the issue and fixed it. Local printers on Windows should work well in the upcoming release.

Regards,

Kuba

[kubaszym1]

Hi,

I found the issue and managed to fix it. Local printers on Windows should be visible in the upcoming release.

Regards,

Kuba

[kubaszym1]

Hi,

I would need more information to investigate your issue. What OS is on your client machine? What version of NoMachine do you have?

During the session you should see two NoMachine sound devices: NoMachine Audio Adapter and NoMachine Microphone Adapter. NoMachine Audio Adapter should be set as default to be able to stream the data to the client machine. Are these devices visible?

Can you provide us any logs, so we can look for error messages?

Regards,

Kuba

[kubaszym1]

Hi,

The error while unmuting is the following:

amixer: Control sysdefault:0 element write error: Operation not permitted

I checked on my machine that this error occurs when you use HDMI device and a new kernel.

Regards,

Kuba

[kubaszym1]

Hi,

It seems that it’s a kernel related issue. For some reasons ubuntu 22 with linux kernel >= 5.19.0-39 sometimes does not recognize or cannot mute/unmute HDMI devices. I’m trying to figure out a workaround for this, but maybe the only option is to downgrade to kernel like, i.e, linux-image-5.19.0-21-generic. Does the sound work outside NoMachine session if you set HDMI device as defualt? Can it be muted/unmuted outside NoMachine session?

You can check your kernel version by running:

uname -r

Regards,

Kuba

[kubaszym1]

Hi,

We discovered an issue with forwarding devices in custom sessions. We will work on a fix. I noticed that it happens if you open the session in a floating issues. It should work if you run the custom sesssion in a virtual desktop. You can set it when you create a new custom session.

Regards,

Kuba

[kubaszym1]

Hi,

I found some errors in the logs that cause the failure of unmuting process. Although their cause is really hard to track. I noticed that they may occur when HDMI or ELD devices are used. Do you use a device that is plugged in with a HDMI cable?

Also, the output of the command below would be helpful for further investigation:

amixer -c 0 controls | grep “Playback Volume”

Regards,

Kuba

[kubaszym1]

Hi,

Which sound server do you use? Pulseaudio or pipewire? If you have pipewire, you can check this file: /usr/NX/etc/node.cfg. The parameter “AudioInterface” should be set to “pipewire” or “pulseaudio” respectively. If it’s not set in the right way, you can manually change and restart the server. Maybe this will help.

Regards,

Kuba

[kubaszym1]

Hi,

NoMachine mutes the audio on the server by default. You can unmute in session settings if you want. I assume the main issue is that it stays muted even if client disconnects. It can mean two things: either our muting/unmuting script didn’t work on your machine or it wasn’t called at all while closing session. Testers tried to repeat your issue but they couldn’t. I also tried to reproduce because I have ubuntu 22 as well, but everything works fine for me. Our script uses amixer, so you can try the commands below to check if it works on your machine:

amixer -c 0 set Master playback 0% mute
amixer -c 0 set Master playback 100% unmute

You can also enable debug logs in server settings. On the server side, open NoMachine and go to Settings->Server–>Status->Server logs.

Regards,

Kuba

 

 

 

[Author]

Posts