I took a look at the pskpost entries.
There are 3 places where this occurs and only one of the three has any
protection against early posts.
I'm thinking what's best is to have a m_bandStart and m_bandEnd that gets set
on audio recording start/end.That way you check those two to ensure that the
band doesn't change during the recording period in the WAV file and if it it
has, then don't post to pskreporter.
Does that sound reasonable? That would be in lieu of the one tr_period check
in the code now.
de Mike W9MDB
From: Bill Somerville <[email protected]>
To: [email protected]
Sent: Saturday, July 15, 2017 9:30 AM
Subject: Re: [wsjt-devel] FT8 Bad Spots
On 15/07/2017 15:20, Black Michael via wsjt-devel wrote:
Hopefully Bill can answer this as do believe he wrote it. I've never examined
the pskreporter flow.
Hi Mike, I didn't write it but have updated parts of it. I believe there is
some protection from sending spots after a band change where decodes might be
for either old or new band. There may be a hard coded minute somewhere that
needs to be the T/R period. I am busy with other issues at present but I can
look at it later.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
