Forum Replies Created
-
Posts
-
Ok, I was able to get output audio working by disabling autospawn in my local pulseaudio.conf and enabling the userspace systemd service. I’m unable to get a microphone to work however. NoMachine doesn’t seem to be creating an input audio device. Any thing I should look for specifically to diagnose that?
I’ve confirmed that pulseaudio was already set there and have rebooted the machine to no avail. One thing I did notice when toggling audio in the client was this error in the journal:
Jan 03 12:43:38 noobtube pulseaudio[4688]: [alsa-sink-ALC1220 Digital] alsa-sink.c: Error opening PCM device iec958:2: Device or resource busy
I’ve tried switching back and NoMachine isn’t creating audio devices on my Linux host. I’m using a Windows 10 client to connect.
I’ve disabled the pipewire systemd service & confirmed that pulseaudio is running and pipewire isn’t:
citra 4620 0.0 0.0 867076 14120 ? Sl Dec07 1:01 /usr/bin/pulseaudio --start --log-target=syslog
citra 550912 0.0 0.1 1551956 30396 ? S<l 08:45 0:00 /usr/bin/pulseaudio --start --log-target=syslogI’m also having an issue with no sound on a headless Arch server w/ pipewire (0.3.60). Running the latest NoMachine (8.2.3). I’m not seeing any audio devices being created.
Any tips to get this working? I know it’s in active development. If it’s not ready to use yet, is there a way I can force NoMachine to use pipewire-pulse?