Hi Bill,

OK, I now understand what you're reporting.  Version 1.6.1 r5910 is 
quite a while back, code-revision wise.

I tried to reproduce your effect with the current revision, r6041.  I do 
see a small difference that depends on Rx freq: maybe one or two 
additional decoding seconds, with a total of around 15 decodes.

I can't tell you the exact reason for this dependence, without 
additional work.  I don't see it as especially important -- but would 
like to understand why it's apparently "working harder" when Rx Freq is 
high.  I'll look into it further, when time permits.

        -- 73, Joe, K1JT

On 11/2/2015 6:10 PM, Bill Barrett wrote:
> Hi Joe-
>
> My observation is that the total time to decode the received signals is
> influenced by the setting of the RX frequency.
> IE if setting the RX @ 300 Hz all decoding [65&  9] proceeds rapidly.
> if setting the RX to 2K or above the JT9 prints are delayed significantly.
> My computer is a 4Ghz CPU with 8 Ex units.
> Hope this helps.
>
> Bill W2PKY
>
> On Mon, Nov 2, 2015 at 4:27 PM, Joe Taylor<j...@princeton.edu>  wrote:
>
>> Hi Bill,
>>
>> I'm not sure that I understand your point.  In JT9+JT65 mode, JT9
>> decoding is attempted only at frequencies above the "blue line" marker,
>> set by the "JT65 nnnn JT9" spinner control.  Decoding is always started
>> first at the selected Rx frequency and mode, so the decode you care most
>> about -- presumably the station you're trying to work -- comes out first
>> among all those in its mode.  If you have a slow computer (or for some
>> other reason) some decodes come out after the top of the minute, it's
>> not a big concern.
>>
>> Have I mis-understood what was bothering you?
>>
>>          -- 73, Joe, K1JT
>>
>> On 11/2/2015 4:08 PM, Bill Barrett wrote:
>>> Hello JT Developers-
>>>
>>> Running 1.6.1 5910, noticed when mode is set to JT65 + 9
>>> and the RX frequency is greater than 1500 the JT9 decoding takes a long
>>> time.
>>> If the RX is above 2000 and there are a few JT9 prints the last one could
>>> come at second 59.
>>>
>>> Regularly decode signals -26 -27 -28.
>>>
>>> 73, Bill W2PKY
>>>
>>>
>>> On Mon, Nov 2, 2015 at 3:28 PM, Joe Taylor<j...@princeton.edu>   wrote:
>>>
>>>> Hi all,
>>>>
>>>> Here's an amusing screen shot.
>>>>
>>>> WSJT-X was running with 2-pass decoding enabled for JT65.  Note the two
>>>> decodes of WB9OTX at Freq = 1856 Hz.  Evidently he changed his Tx
>> message
>>>> from "HA3LI WBtOTX -21" to "HA3LI WBtOTX 73" in mid-transmission.  The
>>>> decoder gets the "73" message in its first pass, and the "-21" message
>> in
>>>> the second pass.
>>>>
>>>>           -- Joe, K1JT
>>>>
>>>>
>>>>
>> ------------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> wsjt-devel mailing list
>>>> wsjt-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>>
>>>>
>>>
>>>
>>>
>>>
>> ------------------------------------------------------------------------------
>>>
>>>
>>>
>>> _______________________________________________
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to