Forum / NoMachine for Linux / USB Microphone input
- This topic has 10 replies, 2 voices, and was last updated 10 months, 4 weeks ago by kubaszym1.
-
AuthorPosts
-
October 23, 2023 at 08:22 #45756SlivoParticipant
Good morning 🙂
I’ve started using NoMachine again a week ago trying to limit the complexity of using both my ubuntu laptop and my windows desktop PC on the same desk.
It mostly works fine at the moment but I don’t seem to be able to forward my USB blue snowball input from the Windows computer to the remote Ubuntu I’m taking control of.
I enabled “Mic in” on client side and selected my USB mic as an input device (see screenshots: https://ibb.co/qn8SM3Z and https://ibb.co/37MwFTw)
On the controlled Ubuntu however I don’t have any added input device. (I would expect a “NoMachine input https://ibb.co/KrM8hZg). The system settings does however show what seems to be a NoMachine mic (https://ibb.co/4jptvL1)I’m not sure why and how to troubleshoot this,
Thanks for taking the time to readRegards
October 23, 2023 at 14:26 #45768SlivoParticipantForgot version and system details:
– Free version of NoMachine
– Windows 11 with NoMachine 8.9.1
– Ubuntu 22.04.3 LTS (gnome) with NoMachine 8.9.1 (xps 9320)
– Physical displayOctober 24, 2023 at 11:53 #45774kubaszym1ParticipantHi 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
October 25, 2023 at 09:02 #45781SlivoParticipantHi !
Unfortunately as you can see on the third link from my initial post and there https://ibb.co/PQGZq9r I don’t have any “NoMachine virtual device” in the input device list, even after enabling “Mic in” in the session setting
Thanks for your answer, time and help 😀
Regards
October 27, 2023 at 10:30 #45818kubaszym1ParticipantHi,
It seems that there is an error during the connection that breaks the process of creating virtual devices. There are several explanations for such issue, so I need some more information. Please gather logs from the server side as described here: https://kb.nomachine.com/DT07S00243 and send them to forum[at]nomachine.com.
Regards,
Kuba
October 30, 2023 at 09:20 #45833SlivoParticipantGood morning,
I collected some logs and sent them by email as you asked!
Thanks for your time 🙂
November 6, 2023 at 14:30 #45927kubaszym1ParticipantHi,
I checked your logs and unfortunately I couldn’t find the explanation for your issue. Can you ensure that you set the highest log level (9 – Debug) and gather logs again? Without debug logs I cannot tell why NoMachine Microphone is not created.
Regards,
Kuba
November 13, 2023 at 09:14 #45999SlivoParticipantGood morning,
I just collected and sent a new log archive to the forum mail address
I didn’t find a way to check / set the log level to 9 however. I used the following commands
nxserver –debug –enable all
nxserver –debug –collectI also spotted that the input device is somehow set to “blank” as you can see here : https://ibb.co/mz2pxjC
Thanks for your help
November 22, 2023 at 14:18 #46100kubaszym1ParticipantHi,
You can already try the next version – NoMachine 8.10.1. It’s possible that it will solve your issues. If not, please check your configuration – I noticed that your logs contain some configuration errors on the server side. Please check if the property AudioInterface from /usr/NX/etc/node.cfg is set to “pipewire”. You can also check the environment of the nxnode process. Find nxnode PID using i.e. ‘ps -aux | grep nxnode’, run ‘cat /proc/<pid>/environ’ and look for XDG_RUNTIME_DIR=/run/user/<user_id>. If XDG_RUNTIME_DIR is not set properly you can experience issues with transferring audio.
Best regards,
Kuba
December 9, 2023 at 14:47 #46267SlivoParticipantHi,
Thanks for your support.
I’ve updated both server and client, behavior is still the same.
Both node.cfg and xfg runtime are properly set as you explainedBest regards
December 12, 2023 at 14:23 #46297kubaszym1ParticipantHi,
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
-
AuthorPosts
This topic was marked as solved, you can't post.