Forum / NoMachine for Linux / CachyOS (Arch) No audio pass-through
Tagged: audio
- This topic has 14 replies, 3 voices, and was last updated 7 months ago by Britgirl.
-
AuthorPosts
-
March 10, 2024 at 21:18 #47314gerardParticipant
For the life of me I’m unable to get AUDIO passing through from my Linux server running CachyOS which is just arch.
The audio system is pipewire and I’ve tested several other desktop sharing tools and they were able to pass through the audio just fine. However I found NoMachine offered better display performance overall so it be nice if I can figure this out with the help of someone if possible?
– NoMachine 8.11.3 (from AUR Repo) (same on Windows11 machine which views this server)
– Using Free Version
– Problem is persistent and I checked config and from what I can tell its set to Pipewire so that is correct.
– Plasma5 and 6 issue.I can provide logs once I know exactly what is relevant.
March 11, 2024 at 12:22 #47320BritgirlKeymasterPlease try with official NoMachine packages from our own website. We don’t officially support Arch, so to install you need to run:
wget https://www.nomachine.com/free/linux -O nomachine_current.tar.gz sudo tar zxf nomachine_current.tar.gz -C /usr sudo /usr/NX/nxserver --install redhat
If the problem still persists, please show us your connection and options log files. You can find them in .nx/R-<session_id>/ on the machine you are connecting from.
Your logs from the connection would help us a lot (both client and server sides). You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
March 11, 2024 at 12:59 #47321gerardParticipantOk here is a log dumb. Followed instructions, no audio still. Tried to change audio device to a few other things, nothing.
March 11, 2024 at 15:01 #47325BritgirlKeymasterThey’re getting caught in our filter, so send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
March 11, 2024 at 16:21 #47329gerardParticipantDone
March 12, 2024 at 15:37 #47351kubaszym1ParticipantHi,
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
March 12, 2024 at 16:02 #47352kubaszym1ParticipantOne 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 workaround2) Create a symlink /var/run/pipewire/pipewire-0 to /var/run/user/{uid}/pipewire/pipewire-0
Regards,
Kuba
March 13, 2024 at 07:57 #47369gerardParticipantI will check and do these things you suggest.
March 13, 2024 at 08:09 #47370gerardParticipant#47351
Yes processes owned by user.
printenv shows XDG_RUNTIME_DIR=/run/user/1000
WHILE
cat /proc/1559/environ (there are 3 pids) shows this
PWD=/usr/NX/etcNX_FEATURES=underverse-server,GigabyteTechnologyCo.Ltd.AB350N-GamingWIFI,Linux,CachyOS,6.7.9,x86_64,AMD Ryzen 5 3600 6-Core Processor ,12,33574191104,316PERL5LIB=/usr/NX/lib:/usr/NX/lib/perl:/usr/NX/lib/perl/include:/usr/NX/lib/perl/nxnode:/usr/NX/lib/perl/libperlNX_SYSTEM=/usr/NXPERL5INCLUDE=/usr/NX/lib/perl/nxnodeNX_VERSION=8.11.3SHLVL=0LD_LIBRARY_PATH=/usr/NX/lib:/usr/NX/lib/perl:/usr/NX/lib/perl/include:/usr/NX/lib/perl/nxnode:/usr/NX/lib/perl/libperlPATH=/usr/NX/lib:/usr/NX/lib/perl:/usr/NX/lib/perl/include:/usr/NX/lib/perl/nxnode:/usr/local/sbin:/usr/local/bin:/usr/binDBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/busUSER_PAM_ENV_KEYS=
March 13, 2024 at 08:16 #47371gerardParticipant#47352
neither of these locations exist under Arch for pulse native or pipewire-0
March 13, 2024 at 08:21 #47373gerardParticipantIn saying all that there is some funky stuff going on with pulse on this server for some reason.
Odd however how all other desktop sharing apps have no problem with all this.
Attachments:
March 22, 2024 at 12:37 #47497kubaszym1ParticipantHi,
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
March 22, 2024 at 14:12 #47501gerardParticipantMAN files excluded.
Pipewire-pulse package files:
/usr/bin/pipewire-pulse /usr/lib/pipewire-0.3/libpipewire-module-protocol-pulse.so /usr/lib/pipewire-0.3/libpipewire-module-pulse-tunnel.so /usr/lib/systemd/user/pipewire-pulse.service /usr/lib/systemd/user/pipewire-pulse.socket /usr/share/pipewire/media-session.d/with-pulseaudio /usr/share/pipewire/pipewire-pulse.conf
Pipewire package files:/usr/bin/pipewire /usr/bin/pw-cli /usr/bin/pw-config /usr/bin/pw-dot /usr/bin/pw-dump /usr/bin/pw-link /usr/bin/pw-metadata /usr/bin/pw-mon /usr/bin/pw-profiler /usr/bin/pw-reserve /usr/bin/pw-top /usr/bin/spa-inspect /usr/bin/spa-json-dump /usr/bin/spa-monitor /usr/lib/pipewire-0.3/libpipewire-module-access.so /usr/lib/pipewire-0.3/libpipewire-module-adapter.so /usr/lib/pipewire-0.3/libpipewire-module-client-device.so /usr/lib/pipewire-0.3/libpipewire-module-client-node.so /usr/lib/pipewire-0.3/libpipewire-module-combine-stream.so /usr/lib/pipewire-0.3/libpipewire-module-link-factory.so /usr/lib/pipewire-0.3/libpipewire-module-metadata.so /usr/lib/pipewire-0.3/libpipewire-module-portal.so /usr/lib/pipewire-0.3/libpipewire-module-profiler.so /usr/lib/pipewire-0.3/libpipewire-module-protocol-native.so /usr/lib/pipewire-0.3/libpipewire-module-rt.so /usr/lib/pipewire-0.3/libpipewire-module-rtkit.so /usr/lib/pipewire-0.3/libpipewire-module-session-manager.so /usr/lib/pipewire-0.3/libpipewire-module-spa-device-factory.so /usr/lib/pipewire-0.3/libpipewire-module-spa-device.so /usr/lib/pipewire-0.3/libpipewire-module-spa-node-factory.so /usr/lib/pipewire-0.3/libpipewire-module-spa-node.so /usr/lib/spa-0.2/control/libspa-control.so /usr/lib/spa-0.2/libcamera/libspa-libcamera.so /usr/lib/spa-0.2/support/libspa-dbus.so /usr/lib/spa-0.2/support/libspa-journal.so /usr/lib/spa-0.2/support/libspa-support.so /usr/lib/spa-0.2/v4l2/libspa-v4l2.so /usr/lib/spa-0.2/videoconvert/libspa-videoconvert.so /usr/lib/spa-0.2/videotestsrc/libspa-videotestsrc.so /usr/lib/systemd/user/pipewire.service /usr/lib/systemd/user/pipewire.socket /usr/share/pipewire/client-rt.conf /usr/share/pipewire/client-rt.conf.avail/20-upmix.conf /usr/share/pipewire/client.conf /usr/share/pipewire/client.conf.avail/20-upmix.conf /usr/share/pipewire/minimal.conf /usr/share/pipewire/pipewire-pulse.conf.avail/20-upmix.conf /usr/share/pipewire/pipewire.conf /usr/share/pipewire/pipewire.conf.avail/10-rates.conf /usr/share/pipewire/pipewire.conf.avail/20-upmix.conf
There are a number of other pipewire related packages as you can see in the arch repo website search system. But I think these two are the ones of most importance.
March 29, 2024 at 02:04 #47570gerardParticipantI noticed in this session log file it has some audio errors. (yes my quicksync is also busted for some reason)
Attachments:
April 4, 2024 at 13:59 #47645BritgirlKeymasterAbout the workaround that was already provided, it’s from the Trouble Report here: https://www.nomachine.com/TR09U11006 which we originally opened on Gentoo and it’s the same for Arch-based distributions such as Cachy OS. The problem is that to make sound work on arch/gentoo distros, it means that NoMachine should change the configuration files of the already built-in pulseaudio/pipewire server during installation (/usr/share/pipewire/pipewire-pulse.conf). This is not a solution. Changing the system’s configuration can only be made by the administrator/owner, so for this reason the creation of a symlink is the best workaround.
-
AuthorPosts
This topic was marked as solved, you can't post.