friendlier it would be great. I have udev rules to name the
serial ports, alsa cards and pulse descriptions after the rig names.
With multiple rigs plugged in it is not pretty.
Thanks all
73
Glenn VE9GJ
On 2021-02-17 2:45 p.m., Topher Petty wrote:
Oddly, WSJT-X DOES show up in pavucontrol fo
help describe the issue.
First 2.1.2
https://youtu.be/MF8sPvode9c
then
2.2.1
https://youtu.be/x89NKQqLxU4
Sometimes it is not too bad but it does seem the longer it runs the
worse it gets.
73
Glenn VE9GJ
___
wsjt-devel mailing list
wsjt-devel
happen very fast.
With 2.1.2 I could run 3 instances of WSJT-X without issue.
With 2.1.2 top shows wsjtx cpu ~5% mem 3%
With 2.2.2 top shows wsjtx cpu ~10% mem ~3%
2.2.2 also show jt9 running between 15 and 60%
Thanks for all the great work and just ask if I can supply more details.
73
Glenn VE9GJ
it is applied to
both the RX and TX frequency. At the moment I run with no offset in
WSJT-X and manually set the 80m freq on VFO B and put the Kenwood in
split and it seems to work OK. It would be great if an offset could be
specified for just TX.
Keep up the great work!
73
Glenn VE9GJ