Hello,
Today I've been able to see an important warning message that most
likely is the alarm for the cause of the audio issue in my WSJT-X for Linux:
*ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred**
*
I've installed pipewire on place of the default pulseaudio and I don't
know if I should adjust something in the settings for this new sound
environment.
Any thought is very appreciated.
Thanks and regards,
---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**
l 11/11/22 10:37, Marco Calistri via wsjt-devel ha scritto:
Il 11/11/22 09:26, Uwe, DG2YCB ha scritto:
Hello Marco,
FYI. The second issue should be fixed with v2.6.0-rc5. We have
fine-tuned some GUI settings so that it now works better with
different font sizes and on different operating systems.
And issue #1 can also be RFI. Does it also happen on all bands or
only on some? Check whether the error is still there when TX PWR is
very low.
73 de DG2YCB,
Uwe
________________________________________
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB
Hi Uwe and thanks for your reply!
Regarding issue 1 it is not RFI related since it doesn't occur under
WSJT-X for Windows using same rig and computer, it is an isolated
behavior between computer's sound system and WSJT-X under Linux,
because as I wrote, by using any other apps to play sounds, it is
working perfectly.
Il 11/11/22 08:35, leo bistmans via wsjt-devel ha scritto:
1)
Does pavucontrol show a difference at fail time?
Does dmesg -w show some lines at fail time?
I had something like this when hdmi screen came out of power save
modem the Linux thought there was a new audio default: the non
existing speakers in the screen via the hdmi out ...
2)
I just do Dark on gnome desktop:
wsjtx -r ft-891 --stylesheet :/qdarkstyle/style.qss
73 de on1aad Leo
Hi Leo!
1) To be honest I've not checked the logs but as I wrote if I play a
video on same environment, without touching nothing on sound system,
the sound works perfectly. I'm suspecting after some guessing, that
this sound interruption under WSJT-X could be related to my tests
using the "*ondemand*" cpu-governor kernel option.
I roll back to "*schedutil*" now and I will keep monitoring if such
issue occurs again.
2) I use XFCE as desktop environment and I start WSJT-X program from
within CQRLOG, which as far as I tested, is not accepting "composed
commands on same string" as the one you mention above.
BTW I would like to ask from where you take the *qss* styles?
Il 11/11/22 08:21, Kari Sillanmäki via wsjt-devel ha scritto:
Hi Marco,
Never had this problem. What Linux version and radio are you using?
Why not just set environment variable QT_STYLE_OVERRIDE="Fusion" ?
73's de Kari, oh2gqc
Hi Kari!
I'm using openSUSE Tumbleweed 64 bits and my radio is the YAESU FT-100.
Your suggestion is interesting but it will force the style globally
for any user's application so, IMHO is not the best solution because
it could not be ideal for different apps (maybe...).
*Thanks everybody for your feedback!*
Best regards!
Am 10.11.2022 um 21:40 schrieb Marco Calistri via wsjt-devel:
Hello,
I'm using latest release of WSJT-X (2.6.0-RC4) and I faced two
issues so far related to my Linux installation:
1 - Suddenly the audio IN/OUT communication with the default sound
system get lost and WSJT-X stop to receive and to send audio.
*Please note that it happens just within WSJT-X and the default
sound system,* I verified this by opening a YouTube video whose
audio plays perfectly. To resolve this issue I have to
"*pkill*"wsjtx, eventually delete its lock file in /tmp and restart
the app.
2 - With my desktop environment (XFCE), I need to start WSJT-X with
a specific *"style"* option, otherwise the band frequencies and
other graphical details (buttons, menus) of the program window are
resulting not perfectly adjusted for the window itself. More in
detail, I use a script to start my WSJT-X which executes the
following command:
*/home/marco/WSJT-X_build/.wsjtx/bin/wsjtx -style Fusion*
Would like to know if is there an option, during the program source
compiling of WSJT-X, to *force* a specific starting window
environment style.
3 - Please note that the issue at point 1 is *not present with
WSJT-X for Windows as I could verify under Windows 11.**
*
Many thanks for your kindest attention!
Best regards,
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
