As a side note, when having problems like this it can be nice to compile
and run wsjt-x in an isolated container, with known and controlled
system environment:
https://sm6vfz.wordpress.com/2023/07/10/building-and-running-wsjt-x-in-a-docker-container/
This is tested by me on RPi 5 as well.
/Dani
Hi Kari,
What's the length of the IC-7300 output device name?
There doesn't seem to be much consistency in the size of card_name in
the pipewire alsa plugin. But, if the name gets truncated, wsjtx should
fail on the amd64 as well and doesn't. I'll ask on the pipewire-devel
list.
spa/plugins/alsa
FWIW I am finding the same thing here.
Ft-710
Pi5
Ubuntu 24.04 stock pipewire but using x11 not wayland
Wsjtx 2.7.0-rc3 set to pipewire
Pressing tune or enable tx would not produce any audio drive on the 710
I then installed pavucontrol.
When trying to tx audio output in pavucontrol would cycle bet
Hi Kari,
It's installed on both systems.
Some more evidence:
I can run aplay and output to the fig's sound output device without
error. However, if I run wsjtx with the audio output set to the hdmi
device, when I run aplay, I get the same "no such device" error.
I don't this is a wsjtx issue, r
