On Sun, Feb 4, 2024 at 11:59 AM, Dave, N1AI wrote:
I have done manual setups for using RTP streams using Pulse in Debian 11 with the "quisk" app driving the Hermes-Lite 2 SDR.
It more or less happens automatically if you use ssh with x-windows tunneling enabled, but you may need to set some environment variables to get things to work the way you want.
To try to add more detail, if you do 'man ssh' on a linux box you should see the '-X' option described as:

?
I guess it's proper name is "X11 forwarding" but most of us call it "tunneling".
On my Linux laptop I enable this by default by having the following in .bashrc:

When I use ssh from my laptop to the sbitx pi then start the 'vlc' program, its video is sent in the ssh tunnel using X forwarding to my laptop.
If I then use vlc's 'Media -> Open File' menu to open an audio file and hit the || button to play, I hear the audio.
The tunnel contains both xlib primatives for graphics as well as RTP/RTSP streams for audio.
This works because vlc is sending audio to the default PulseAudio device on the sbitx which is sending the audio via RTP that is then tunneled by ssh session to the Linux laptop which then sends it to the local PulseAudio to play on the laptop's default device.
If you run the PulseAudio 'pavucontrol' app on the laptop you can see that it is getting audio from VLC which is NOT running on the laptop!

If I start the sbitx application I do see its video, but do not hear any audio, it is playing to the sbitx speaker still.?
This is because the sbitx application hard codes use of the ALSA 'audioinjectorpi' device which writes the audio samples to the sbitx speaker.??
If you have a good 'ssh' client for Windows I believe all the same things will still happen when you use the equivalent of the '-X' flag to start it.
My favorite is MobaXterm ( ,? ).??
My head exploded when I first encountered it in the late 2010s.? It has an entire X server, plus ssh client, plus bash, plus all the rest of the Cygwin linux command set for DOS, plus lots of other stuff, all in a single Windows application?? I had worked with X on early RISC processors of the 1980s and 1990s, as well as early Linux x86 boxes from '386 onward.? All that stuff in a single Windows program?? I just could not believe it!!!
Having said that, these days I don't use Windows much so I have never tried it for this exact purpose, but I am pretty confident that it will work.
--
Regards,
Dave, N1AI