
Alternatively you can use the text-based config utility by opening a terminal window and type. The option to force audio through HDMI / 3.5m jack is in the Advanced Options. All of the remote access protocols Ive mentioned are freely available (either with an OS or as a.
RASPBIAN NO AUDIO NOMACHINE INSTALL
Ability to install JRiver Media Center and NoMachine (remote desktop software). NoMachine NX, mentioned already, is one such project. Description of Problem: Audio on NoMachine works fine if audio is already playing when opening a new session, if audio is paused or isn't playing for a while then it will not play any more audio.

There should be an option to start the utility. audio linux optimized system based on Gentoo, includes various system. This allows us to use a NoMachine server to stream audio coming into and out of a Raspberry Pi. You can access the configuration utility through Menu / Preferences. I wasn’t sure which linux audio system nomachine uses, but found this recent post – – and ran the NX sound setup and ensured that pulseaudio was running. The NoMachine server for Raspbian, the Linux distribution that runs on the Raspberry Pi, has the ability to interface with a Linux PulseAudio streaming audio server. In all cases, I can get alsamixer to configure and aplayer to play stuff to the relevant device but nomachine’s sound settings don’t offer any devices in the drop-down lists for speakers and mic selection and there is no sound. I’ve tried the built-in analogue audio, HDMI audio and a USB (C108) sound device.
RASPBIAN NO AUDIO NOMACHINE FULL
The Win10 machine shows the volume muted initially for a device “NoMachine microphone adapter” whether this is muted or at full volume makes no difference to the lack of sound on the Pi.

I decided to try NoMachine and it seems to be working very well windows-to-windows and for most purposes on the Pi3 (Debian Jessie) vs a Windows 10 remote. If so, and it is set up for a per-user configuration, (which has been the default for a while now) then the hardware is locked to the user that logged in first - and this is one thing that the super-user - who you (temporarily) seem to become when using sudo can not then use because it/the audio hardware is locked to the 'un-sudo' identity.
