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/alsa-acp-device.c:     char card_index[16], card_name[64], *p;
spa/plugins/alsa/alsa-pcm.c:    char card_name[64];
spa/plugins/alsa/alsa-pcm.c:    char card_name[256];
spa/plugins/alsa/alsa-pcm.h:    char card_name[128];


Steve

> Hi Steve,
> 
> Pipewire may be the culprit here.
> 
> I'm currently running WSJT-X on a Raspberry PI4 with Raspberry OS 12
> ( 
> bookworm ) 64bit
> without issues.
> 
> I'm using IC-7300 but FT-710 should be similar when it comes to
> audio.
> 
> If you open terminal and enter "ps -fjH -u $USER", do you see a line
> "/usr/bin/pipewire-pulse" there?  This is ( I think ) some kind of
> brdige
> allowing pulse applications to use pipewire.
> 
> 'Kari
> 
> On 6/30/24 17:32, Steve Brown wrote:
> > 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, rather a problem in pipewire. I'll
> > look.
> > 
> > I'm especially suspicious of the rig's long device name.
> > 
> > Steve WA9OLA
> > 
> > On Sat, 2024-06-29 at 22:27 +0300, Kari Sillanmäki via wsjt-devel
> > wrote:
> > > Hi Steve,
> > > 
> > > Do you have "libqt5multimedia5-plugins"  installed?
> > > 
> > > 73's de Kari, oh2gqc
> > > 
> > > On 6/29/24 22:04, Steve Brown via wsjt-devel wrote:
> > > > Hi,
> > > > 
> > > > No problem on Ubuntu 24.04 on an amd64, but no audio on RPi 5
> > > > with
> > > > the
> > > > same OS. Receive works on both.
> > > > 
> > > > I rebuilt wsjtx so the images are identical on both (2b9d65).
> > > > 
> > > > The settings are identical.
> > > > 
> > > > The sound output name is
> > > > "alsa_output.usb-C-Media_Electronics_Inc._USB_Audio_Device-
> > > > 00.analog-
> > > > stereo"
> > > > 
> > > > The log is spammed with
> > > > 
> > > > Jun 28 14:48:00 wsjtx kernel: retire_capture_urb: 1014
> > > > callbacks
> > > > suppressed
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: hw:2:
> > > > snd_pcm_status error: No such device
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: hw:2:
> > > > snd_pcm_recover error: No such device
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: get_status
> > > > error
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: hw:2:
> > > > snd_pcm_drop
> > > > No such device
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: hw:2: close
> > > > failed:
> > > > No such device
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: front:2:
> > > > snd_pcm_drop No such device
> > > > Jun 28 14:48:01 wsjtx pipewire[1007]: spa.alsa: front:2: close
> > > > failed: No such device
> > > > Jun 28 14:48:01 wsjtx kernel: usb 1-2.2: reset full-speed USB
> > > > device number 4 using xhci-hcd
> > > > Jun 28 14:48:03 wsjtx pipewire[1007]: spa.alsa: front:2:
> > > > snd_pcm_drop No such device
> > > > Jun 28 14:48:03 wsjtx pipewire[1007]: spa.alsa: front:2: close
> > > > failed: No such device
> > > > Jun 28 14:48:03 wsjtx kernel: usb 1-2.2: reset full-speed USB
> > > > device number 4 using xhci-hcd
> > > > Jun 28 14:48:05 wsjtx pipewire[1007]: spa.alsa: front:2:
> > > > snd_pcm_drop No such device
> > > > Jun 28 14:48:05 wsjtx pipewire[1007]: spa.alsa: front:2: close
> > > > failed: No such device
> > > > Jun 28 14:48:05 wsjtx kernel: usb 1-2.2: reset full-speed USB
> > > > device number 4 using xhci-hcd
> > > > 
> > > > If I set wsjtx audio output to the hdmi audio device, I get FT8
> > > > tones
> > > > and no complaints in the log.
> > > > 
> > > > The rig indicates transmit, but no audio, so no RF.
> > > > 
> > > > Any suggestions on tracking this down?
> > > > 
> > > > I tried uncommenting some of the qDebug calls, but can't
> > > > find/enable
> > > > the output.
> > > > 
> > > > Steve WA9OLA
> > > > 
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > wsjt-devel mailing list
> > > > wsjt-devel@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > wsjt-devel mailing list
> > > wsjt-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 



_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to