Locked Transmit Delay after Double Click (WSJT-X 2.2.0-rc1)


Jeff, W8TB
 

Just an observation, when double-clicking on a callsign with 2.2.0-rc1, there is a noticeable delay before the rig goes in to transmit.  I switched back to the 2.1.2 version to test and compare and it is back to normal, which is nearly immediate. 

Rig: IC-7300, connected USB to i5 PC

 

Jeff

 


Joe
 

Tx starts when it's supposed to start: at the 15-second boundary.  

You are double-clicking well before that boundary, because the program is now displaying decodes earlier.

  -- 73, Joe, K1JT


DAVID MM0AMW
 

If you click on a callsign after the first decoding run at 11 seconds it will mean a wait of around 3 seconds before your transmission starts at the correct time.

73
David
MM0AMW

On Wednesday, 13 May 2020, 16:53:33 BST, Jeff, W8TB via groups.io <w8tb@...> wrote:


Just an observation, when double-clicking on a callsign with 2.2.0-rc1, there is a noticeable delay before the rig goes in to transmit.  I switched back to the 2.1.2 version to test and compare and it is back to normal, which is nearly immediate. 

Rig: IC-7300, connected USB to i5 PC

 

Jeff

 


Jeff, W8TB
 

Thank you! That makes perfect sense.  It just didn't dawn on me that the decodes would be so quick that I could be ahead of the curve for transmitting.  Excellent!


Dave (NK7Z)
 

Hi Jeff,

I see the first pass decode is being presented at around say :12 seconds into the clock cycle, not :14 seconds after the cycle starts. This is sooner than it was in the previous version, by a few seconds. This make it look like a few seconds delay has been added, when in reality the transmit cycle is being held until the next :00 point.

Could this be what you are seeing?

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 5/13/20 6:27 AM, Jeff, W8TB via groups.io wrote:
Just an observation, when double-clicking on a callsign with 2.2.0-rc1, there is a noticeable delay before the rig goes in to transmit.I switched back to the 2.1.2 version to test and compare and it is back to normal, which is nearly immediate.
Rig: IC-7300, connected USB to i5 PC
Jeff