Hello Bill,
> Here is a little more data on this.
>
> Here's a screenshot showing the issue. KG8DH is transmitting in
> even periods. Red arrows show where his signal is decoded but grouped with
> the previous odd period. This I guess might just be an issue of the "80m"
> separator not being inse
Bill,
Ø Similarly a priori decoding based on the DX Call field are disabled by
clearing the DX call field. If you are going to leave WSJT-X unattended then
clearing the DX Call field is a good idea.
Thanks for that. Noted. It is fully noted and makes sense. Some observations
had occurred aft
Successfully tried it again with a 2nd pi4 that has a usb sound dongle.Working just fine.Will revisit the 1st pi4 that has different sound setup and i use it headless via nomachine.TNX AGN DE N2LO~>-Original Message-From: g4...@classdesign.comTo: wsjt-devel@lists.sourceforge.netSent: 2020-0
A reminder to those of us using non-standard call:
When you don't use TX1 you don't make QSO
190130 Tx 2712 ~ EA3BCX F6BHK JN24
190115 -3 0.3 2426 ~ F6BHK <...>
190215 -7 0.2 2436 ~ F6BHK <...>
190300 -11 0.9 1490 ~ CQ IT9DBN JM77
--
73, de Serge
F6BHK, ex-VR2LL, G5BHT, FM5GC
Great... Working as designed.
AL, K0VM
On 5/14/2020 10:18 AM, Bill Somerville wrote:
On 14/05/2020 15:55, Al wrote:
Just FWIW...
I have set up a test where I have 2.2.0-RC1 and 2.1.2 running in
parallel on the same PC from the same audio source. I notice that the
SNR reported by 2.2.0-RC1 is
I believe this was covered in the User Manual for v2.2
"SNR estimates no longer saturate at +20 dB, and large signals in the
passband no longer cause the SNR of weaker signals to be biased low.
Times written to cumulative journal file ALL.TXT are now correct even
when the decode occurs after the
On 14/05/2020 15:55, Al wrote:
Just FWIW...
I have set up a test where I have 2.2.0-RC1 and 2.1.2 running in
parallel on the same PC from the same audio source. I notice that the
SNR reported by 2.2.0-RC1 is consistently more optimistic vs. 2.1.2.
In some cases up to 13db greater on strong
Andy --
On 5/14/2020 10:23, Andy Durbin K3WYC wrote:
I have seen decode hangs multiple times with v2.1.1 and I have reported
that previously.
Thanks for the report. What we are interested in now is reports about
v2.2.0-rc1.
-- 73, Joe, K1JT
___
Just FWIW...
I have set up a test where I have 2.2.0-RC1 and 2.1.2 running in
parallel on the same PC from the same audio source. I notice that the
SNR reported by 2.2.0-RC1 is consistently more optimistic vs. 2.1.2.
In some cases up to 13db greater on strong signals. Most signals report
at
I have seen decode hangs multiple times with v2.1.1 and I have reported that
previously. In all cases the time keeps updating, and widegraph stays active.
The only way I have found to recover is to restart WSJT-X. I attempted to
find an association with wave files spanning the decode hang ti
On 14/05/2020 15:02, Stephen Ireland wrote:
Hi Folks,
I have analysed the logic of the anomaly in this report These forms of
anomaly - though rare – are something that we may have to watch for
manually … Hence “grit and bare”.
73
Steve i
VK3VM / VK3SIR
*From:*Stephen Ireland
*Sent:* Thu
Hi Folks,
I have analysed the logic of the anomaly in this report These forms of anomaly
- though rare – are something that we may have to watch for manually … Hence
“grit and bare”.
73
Steve i
VK3VM / VK3SIR
From: Stephen Ireland
Sent: Thursday, 14 May 2020 11:47 PM
To: WSJT software develo
Folks,
Reports are asked for ! Do NOT consider this a “knock” … it is just a report !
I am recording approximately 1 serious “false decode” every 12 hours on
average. Note that I am using “AP” mode:
i.e.
200514_03203018.100 Tx FT8 0 0.0 700 CQ VK3VM QF11
200514_03204518
If you're running an older rigctld backwards compatibility was broken and has
been fixed.
For now you should be able to use rigctld-wsjtx in WSJT-X which should always
work together.
de Mike W9MDB
On Wednesday, May 13, 2020, 11:59:32 PM CDT, Saku wrote:
Saku kirjoitti 14.5.2020 k
On 14/05/2020 6:49, Franz (OE3FVU _ PE0WGA) wrote:
Dear All,
Thanks for all the work – it is very impressive.
I have noticed the following behaviour, compared to v2.1.2, running
both the 32bit versions.
1. – Start-up sequence takes 13 to 14 seconds (2.1.2 takes 5-6 seconds)
2 - changing wi
HI Paul,
thanks for that clarification, we too are finding this issue hard to
reproduce so be patient, we will sort it out eventually.
73
Bill
G4WJS.
On 14/05/2020 4:09, Paul Kube wrote:
Hi Bill,
Yes this is with v2.2.0-rc1, Win 10 64 bit.
As I recall, it only occurred when there was just
2.2.0-rc1 Anomaly responding to MSHV (?) station
This morning, running 2.2.0-rc1, I called ZW5STAYHOME on 30M FT8 with “Auto
Seq” checked. It appears that he was using MSHV or another modified clone
of WSJT-X which allows working on 2 stations at a time, as you can see by
the screen capture below.
17 matches
Mail list logo
