On 22 May 2022 21:17:36 BST, lgtngstk via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
>This occurs with 2.5.4 on my Linux system both with the binary package and
>when compiled from source. Sometimes the audio will work for a few
>transmissions and sometimes it fails right out of the gate. When I use
>pulse, nothing shows up in pavu under playback streams after it stops
>working. The only way to get it back is to reset the profile completely.
>Then the same thing happens again. RX works normally unless I try
>transmitting. Then receive freezes until the program is closed and opened
>again. WSJT-X can be closed normally unless I try transmitting. Then trying
>to close it will make the windows disappear but there remains a single
>threaded wsjt zombie process taking 100% utilization for a single CPU core.
>All of this happens regardless of what audio subsystem it's running on. I
>tried pulse and alsa. All of this makes transmitting completely impossible.
>
>I'm a bit surprised no one else is having this problem. It is similar to
>some of the audio problems I've occasionally had with WSJT in the past.
I also have had this problem ... I don't often tx at the moment but when I do
it locks up that thread you mention.
It happens to me if I try to use "pulse" for *both* RX and TX ... how greedy am
I?
If I use pulse audio for one direction and one of the hw-specific names for the
other direction all is well.
I believe many others hit this and some diagnose it but I assumed that it's a
known problem.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
