Hi Mike,
Thanks for the suggestion. I tried it, but I still get errors at 48000
on my RPi 5.
On my amd64 platform, the 48000 rate gives me 100's of flags on
pskreporter. If I change the output rate to 44100 in soundoutput, I get
zip. Is there an assumption of a 48k sample rate for the output? If so,
can it be changed?
Steve WA9OLA
On Sat, 2024-07-06 at 14:16 +0000, Black Michael wrote:
> Sending sound is only 50% of the sound I/O -- it's the sound reading
> that is being done most the time.
>
> You can minimize hamlib overhead with this data in
> hamlib_settings.json which would go in the same directory as WSJT-
> X.ini
>
> {
> "config": {
> "multicast_data_addr": "0.0.0.0",
> "multicast_cmd_addr": "0.0.0.0",
> "poll_interval": "0"
> }
> }
>
> Mike W9MDB
>
>
>
>
>
>
> On Saturday, July 6, 2024 at 08:33:33 AM CDT, Steve Brown via wsjt-
> devel <wsjt-devel@lists.sourceforge.net> wrote:
>
>
>
>
>
> I changed the sample rate in Audio/soundout.cpp from 48000 to 44100.
> There are no errors logged and the oscilloscope shows data during
> transmit.
>
> It looks like the RPi can't handle the higher rate.
>
> I'm still running to a dummy load, so I don't know yet if I'm getting
> out.
>
> What is interesting is that I can send sound to the rig's sound card
> without errors at 48000. But, if I have rigctl running, I get errors.
> I
> suspect the additional traffic from hamlib is more than the RPi can
> handle.
>
> Steve WA9OLA
>
>
>
> On Sun, 2024-06-30 at 12:07 -0300, Glenn via wsjt-devel wrote:
> > 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 between
> > the
> > 710 and HDMI out every second or so.
> > If I then start mumble configured to use pipewire also and then try
> > to tx in wsjtx all is now OK.
> > Made many QSOs this way with mumble running in the background.
> > Dunno why as that is as far as I got troubleshooting.
> >
> > 73
> > Glenn VE9GJ
> >
> >
> >
> > On June 30, 2024 11:32:31 a.m. ADT, Steve Brown via wsjt-devel
> > <wsjt-devel@lists.sourceforge.net> 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 WA9OLAwsjt-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
> > _______________________________________________
> > 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
