> On Jan 21, 2019, at 13:19, Paul Kube wrote:
>
> yes; but letting auto seq run works just fine most of the time. Toggling
> Enable off only to toggle it on at the beginning of the next cycle is very
> often superfluous.
Don’t forget - it is fine to start several seconds late in the sequenc
s unnecessary, unhelpful or not a
> good idea, simply offering a pragmatic workaround that gives most of the
> user benefit with none of the development costs.
>
> 73
> Gary ZL2iFB
>
>
>
> *From:* Paul Kube
> *Sent:* 18 January 2019 11:05
> *To:* WSJT software devel
This is actually fixable. WSJT-X (in FT8 mode) depends on 50 data frames from
the sound card. If it doesn't get 50 it doesn't record the wav file. You
can't miss more than about 600ms of audio
This could be changed to always record the WAV file at the end of the transmit
period for the mode i
> On Jan 17, 2019, at 15:04, Paul Kube wrote:
>
> Which might be easier than modifying the decode code to handle starting late
> in a cycle, I don't know.
I’ve tested and know that you can miss the first 5 seconds of an incoming
transmission and still decode it fine if they have a decent s
: WSJT software development
Subject: Re: [wsjt-devel] Short Tx inhibits decode...
Gary and Gary,
But I want to stop transmitting near the start of a cycle, and still see
decodes from that cycle. As you point out, deselecting Enable doesn't do that.
The problem arises when I don&#
r pragmatic tips in the FT8 Operating Guide
> <http://www.g4ifb.com/FT8_Hinson_tips_for_HF_DXers.pdf>.
>
>
>
> 73,
>
> Gary ZL2iFB
>
>
>
>
>
> *From:* WB5JJJ
> *Sent:* 18 January 2019 10:12
> *To:* WSJT software development
> *Subject:* Re: [wsjt
the FT8 Operating Guide
<http://www.g4ifb.com/FT8_Hinson_tips_for_HF_DXers.pdf> .
73,
Gary ZL2iFB
From: WB5JJJ
Sent: 18 January 2019 10:12
To: WSJT software development
Subject: Re: [wsjt-devel] Short Tx inhibits decode...
I've noticed that as well. Been this w
> On Jan 17, 2019, at 13:57, Paul Kube wrote:
>
> For example, say I'm CQing on even cycles. After a couple, I decide I want to
> stop CQing if I don't get any replies, so I hit Halt Tx as soon as I see the
> list of decodes from a just-finished odd cycle. Maybe I am transmitting for a
> sec
I've noticed that as well. Been this way for many versions back. Once the
Tx cycle has been initiated (i.e. odd or even Tx has started), and if you
then click Halt Tx, the radio will go to receive, the WF will show the
signals, but none are decoded for the aborted Tx cycle. At the start of
the n
