On 21 Feb 2020 at 9:40, Joe Taylor wrote:
> Hi Martin and all,
>
> Bill has already given you the correct answer. In FT4 and FT8 there are
> only about 2 seconds for decoding before the nominal start of the next
> sequence. If you are using deep decoding, perhaps with AP, and/or have
> a slo
y for top response, need to find how to set my email properly.
-Original Message-
From: Martin Davies G0HDB [mailto:marting0...@gmail.com]
Sent: 21. helmikuuta 2020 2:16
To: WSJT software development
Subject: Re: [wsjt-devel] TImes being incorrectly recorded in ALL.TXT
On 20 Feb 2020 at
development
Subject: Re: [wsjt-devel] TImes being incorrectly recorded in ALL.TXT
On 20 Feb 2020 at 23:10, Bill Somerville wrote:
> Hi Martin,
>
> I suspect the ALL.TXT rows you are referring to were decoded after the
> following period started. The algorithm for allocating to the Rx
On 20 Feb 2020 at 23:10, Bill Somerville wrote:
> Hi Martin,
>
> I suspect the ALL.TXT rows you are referring to were decoded after the
> following period started. The algorithm for allocating to the Rx period
> is simplistic and probably unchanged since times when changeover periods
> were su
Hi Mike,
I'm not sure without reviewing the code, but it probably happens because
the ALL.TXT writing has been abstracted into a common routine so as to
make the format more consistent.
73
Bill
G4WJS.
On 20/02/2020 23:42, Black Michael via wsjt-devel wrote:
Why aren;t the times for ALL.TXT t
Why aren;t the times for ALL.TXT taken from the jt9 decode process which has to
get them right since it's got the wav filename to work with?
de Mike W9MDB
On Thursday, February 20, 2020, 05:16:06 PM CST, Bill Somerville
wrote:
On 20/02/2020 22:01, Martin Davies G0HDB wrote:
I'm r
On 20/02/2020 22:01, Martin Davies G0HDB wrote:
I'm running WSJT-X v2.1.2 0068f9 on a PC with Win 7 (Pro).
Back in late January I posted a message, #5852, on ws...@groups.io
about a 15-second discrepancy I'd observed between the times of FT8
decodes displayed in the Band activity window and t
I just noticed the same thing today. I had two decode periods that both showed
the same time in ALL.TXT when I was debugging problem with JTAlert. I
confirmed they were two separate periods by decoding the WAV files manually.
So the question is where does time for ALL.TXT come from and/or how c
On 20 Feb 2020 at 16:12, Ron WV4P wrote:
> The TX entry is probably because you hit the Watchdog timer.. set it short
> and let it hit it a few times to duplicate.
Sorry Ron, but I can't see how the watchdog timer figures in this at all, and
in any event I
know for certain that the timer wasn't
The TX entry is probably because you hit the Watchdog timer.. set it short
and let it hit it a few times to duplicate.
On Thu, Feb 20, 2020, 4:06 PM Martin Davies G0HDB
wrote:
> I'm running WSJT-X v2.1.2 0068f9 on a PC with Win 7 (Pro).
>
> Back in late January I posted a message, #5852, on ws.
I'm running WSJT-X v2.1.2 0068f9 on a PC with Win 7 (Pro).
Back in late January I posted a message, #5852, on ws...@groups.io about a
15-second
discrepancy I'd observed between the times of FT8 decodes displayed in the Band
activity
window and the times recorded in the ALL.TXT file. The full
11 matches
Mail list logo
