Hi Mike,
W9MDB wrote:
> What is the latest in the minute that JT9 can start and be successfully
> decoded?
>
> I seem to be able to enable up to 25 seconds or so but it seems others can't
> decode.
There is no trivial answer to your question.
I set a hard-wired limit so that the program will not start transmitting
more than 24 s (about 50% of a the Tx duration) into a Tx minute. There
is only a small chance for successful decode of a transmission started
any later.
For an empirical test, I just did a several runs on our sample file
.../save/samples/130610_2343.wav. Normally it produces 8 decodes of JT9
signals.
With the first 22% (11 s) of the data killed, all 8 signals still decode.
With the first 44% (22 s) of data killed, 6 signals still decode. (The
missing ones are two of the weakest three, with SNR -16 and -22 dB,
respectively.
With the first 66% of the data killed there were no decodes.
-- Joe, K1JT
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
