Apologies to the moderator, the previous post was from the wrong email address!
I'm seeing a repeatable failure here where WSJT-X fails after the first transmit audio. I might be doing something very silly, but I don't think so. Here's a detailed run through the configuration and the failure: Configuration: * I'm using a Raspberry Pi 4B and have tested on 8GB and 4GB versions with same results. * Begin with the latest Pi operating system (with recommended software), updated yesterday (17th). * Install WSJT-X prerequisites as per User Guide. * Add the en_US.utf8 locale. * Download and install WSJT-X 2.3.0 as per User Guide * Connect USB soundcard, Ugreen USB audio adapter (Also tried Daffodil with same result). * Run WSJT-X and enter callsign and locator. * Set soundcard input and output to pulse. Rig set to None and soundcard audio out not connected to the rig, so no stray RF. * Use Pi speaker Icons to set audio in and out to USB audio. Failure detail: 1. Run WSJT-X and set mode to FT8 2. Receive works normally with plenty of decodes. 3. Press Tune button and audio appears on the soundcard output. 4. Release Tune and transmit audio ceases and cannot restart. 5. WSJT-X is now in a failed state and won't transmit. 6. Exit WSJT-X and the GUI closes, but Task Manager shows that the wsjtx process continues to run, consuming 25% CPU (1 core?) 7. If I kill the wsjtx process and restart WSJT-X it will receive normally but if I transmit or press Tune it will fail again. In addition to the above steps I've tried running Pulseaudio volume control to monitor the output. When the transmit works, the WSJT-X ALSA device appears in the playback tab. But it doesn't appear when WSJT-X is in the failed state. I do hope someone can help with this. Mike - G4WNC
wsjtx_syslog_2021-03.log
Description: Binary data
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
