Regardless of if wsjt-x is opened first the behavior is the same. QMetaObject::connectSlotsByName: No matching signal for on_serialDeviceListCombo_textActivated(QString) When I launch wfview from a terminal with the debug option using qt audio and pulseaudio loopback there is only $ wfview -d Hard to know if Port Audio and RT Audio are working otherwise…how exactly would I test that? They both appear to produce a valid waterfall but how would I send wfview audio to transmit without cables? system does not want pulseaudio server to run as root, so I don’t. No more difficult than the snd_aloop stuff, and it works like a charm.ī.T.W.

So, for the wfview audio output device, I use MySinkAĪnd for the audio input device I use MySinkB.monitorĬorrespondingly, for wsjtx audio out I use MySinkB

Together with a corresponding input device (the loop back) called. The PulseAudio Commands (pacmd) each create an output device with the given name, The pulseaudio command starts the pulseaudio server. Pacmd load-module module-null-sink sink_name=MySinkB Pacmd load-module module-null-sink sink_name=MySinkA Here is the user-level script I run before firing up wfview and/or wsjtx: #!/bin/sh Instead, you can use the pulseaudio equivalent. Well, snd-aloop is just not supported - the underlying code is just not there. In previous post I documented the difficulty I was having getting the snd_aloop approach, as given in the user guide, to work on my new raspberry pi 400.Ĭame across a blog from Raspberry Pi folks posted early 2021 explaining that they had switched from ALSA sound system to PulseAudio, with a few ALSA plug-ins to maintain some compatibility.

Virtual cable