Re: [wsjt-devel] DT

Hi Michael, WSJT-X v2.3.0 RC1 has some corrections to defects in Tx start time. Also audio buffers sizes have been increased which may add some latency. 73 Bill G4WJS. On 20/10/2020 13:32, Black Michael via wsjt-devel wrote: Side-by-side here - 2.2.2 on the left and 2.3.0rc1 on the right show

Re: [wsjt-devel] DT

TS590S Alan G0TLK, sent from my mobile device On 20 October 2020 13:37:24 Bill Somerville wrote: Hi Alan, same question for you, what is your Rx please? 73 Bill G4WJS. On 20/10/2020 13:20, Alan Groups wrote: Hi, just tested 2.3.0 RC1 for this: Running Meinberg NTP, time.is reporting exact (+

Re: [wsjt-devel] DT

Hi Alan, same question for you, what is your Rx please? 73 Bill G4WJS. On 20/10/2020 13:20, Alan Groups wrote: Hi, just tested 2.3.0 RC1 for this: * Running Meinberg NTP, time.is reporting exact (+/- 0.01s) * Looking at 7MHz FT8 Rx - by eye most DT numbers seem to be in the 0.3 to 0.

Re: [wsjt-devel] DT

Hi, just tested 2.3.0 RC1 for this: * Running Meinberg NTP, time.is reporting exact (+/- 0.01s) * Looking at 7MHz FT8 Rx - by eye most DT numbers seem to be in the 0.3 to 0.4 range with quite a few outliers at even greater offsets including +1's * On 14MHz FT4 (no FT4 signals on 7MHz!) m

Re: [wsjt-devel] DT

On 09/10/2020 20:51, Bobby Chandler wrote: Has anyone noticed the DT being off by .3 to .4 on FT8 on the 2.2.0-rc1 version, even when time.is shows exact? It is OK on FT4 and V2.2.2, always within about .1. Seems maybe a delay in the processing that was not there in earlier versions. Bobby/N

Re: [wsjt-devel] DT

After checking, and double-checking my time sync, it does seem like I see a lot of 0.3 0.4 DT's in FT8 with 2.3.0-rc1. 73 de KM8V On Fri, Oct 9, 2020 at 4:04 PM Bobby Chandler wrote: > Has anyone noticed the DT being off by .3 to .4 on FT8 on the 2.2.0-rc1 > version, even when time.is shows exa

[wsjt-devel] DT

Has anyone noticed the DT being off by .3 to .4 on FT8 on the 2.2.0-rc1 version, even when time.is shows exact? It is OK on FT4 and V2.2.2, always within about .1. Seems maybe a delay in the processing that was not there in earlier versions. Bobby/N4AU -- Bobby Chandler bob...@bellsouth.net

Re: [wsjt-devel] dT

Anyone else have any ideas? Maybe someone familiar with the framework used? From: K2DBK-WSJT Sent: Saturday, June 29, 2019 12:11 PM To: 'WSJT software development' Subject: Re: [wsjt-devel] dT Hi Sergio, I’m not quite sure what you are suggesting. The issue is really just

Re: [wsjt-devel] dT

Yes UT9LI Sent: Saturday, June 29, 2019 6:00 AM To: WSJT software development Subject: [wsjt-devel] dT Setting the dT parameter obviously gives results: in Log ((call)) have dT close to the level ((0)). The problem disappears !? 29 июня 2019, 01:09:42, от K2DBK-WSJT

Re: [wsjt-devel] DT, exactly what does it mean?

Mike, do you have a patch to fix the no decodes for the -dt?   Bobby E Chandler bob...@bellsouth.net     n...@arrl.net On Wed, 12/5/18, Black Michael via wsjt-devel wrote: Subject: Re: [wsjt-devel] DT, exactly what does it mean? To: wsjt-devel

Re: [wsjt-devel] DT, exactly what does it mean?

ct: Re: [wsjt-devel] DT, exactly what does it mean? On 05/12/2018 18:42, Bobby Chandler wrote: It would be good if there is a way to easily put a tick box on the main page, maybe near the up/down arrows to shift up or down 60 cycles for transmit (same as SHIFT>F12 or 11). I used this several

Re: [wsjt-devel] DT, exactly what does it mean?

He's talking about a button, one for +60 and one for -60 de Mike W9MDB On Wednesday, December 5, 2018, 12:50:55 PM CST, Bill Somerville wrote: On 05/12/2018 18:42, Bobby Chandler wrote: It would be good if there is a way to easily put a tick box on the main page, maybe near th

Re: [wsjt-devel] DT, exactly what does it mean?

On 05/12/2018 18:42, Bobby Chandler wrote: It would be good if there is a way to easily put a tick box on the main page, maybe near the up/down arrows to shift up or down 60 cycles for transmit (same as SHIFT>F12 or 11). I used this several times in the contest. Hi Bobby, I don't understand yo

Re: [wsjt-devel] DT, exactly what does it mean?

018 4:25 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] DT, exactly what does it mean? On 04/12/2018 22:11, David Fisher wrote: I see “DT” values that range from about 0.0 to about 0.5 in my system. Does this mean that, on average, my system clock is a little slow, o

Re: [wsjt-devel] DT, exactly what does it mean?

2:25:51 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] DT, exactly what does it mean? On 04/12/2018 22:11, David Fisher wrote: I see “DT” values that range from about 0.0 to about 0.5 in my system. Does this mean that, on average, my system clock is a little slow, or a little

Re: [wsjt-devel] DT, exactly what does it mean?

On 04/12/2018 22:11, David Fisher wrote: I see “DT” values that range from about 0.0 to about 0.5 in my system.   Does this mean that, on average, my system clock is a little slow, or a little fast? I’ve searched the documentation.  It explains that the column of numbers show the difference

[wsjt-devel] DT, exactly what does it mean?

I see “DT” values that range from about 0.0 to about 0.5 in my system. Does this mean that, on average, my system clock is a little slow, or a little fast? I’ve searched the documentation. It explains that the column of numbers show the difference between the signal and the system’s time, but

Re: [wsjt-devel] DT Observation

Interesting. Back in the "old days" of JT65, if the DT's I saw were approximately zero mean, I figured that meant my clock was about right. During the FT8 RU, I never saw any negative DT decodes, and I worried that my clock was fast, in spite of checking it before the contest. Maybe some clock nudg

[wsjt-devel] DT Observation

My setup: Using FT8 V2CR5 on an Optiplex 9010 running Win7 Pro During the RU I observed WF signals where they were obviously calling me but they didn't decode. I observed the same to day while running stations on 7.074. Today I was not in RU mode. I saw a post that mentioned that DT may be an iss

Re: [wsjt-devel] dt offset of 0.2s

On 26/11/2015 14:23, Steven Franke wrote: By the way, with reference to your speculation yesterday that we might have inserted a fudge factor to account for delays — at present there are*no* fudge factors inserted in the dt-estimation process that I am aware of. My statement was based on a fa

Re: [wsjt-devel] dt offset of 0.2s

Hi Steve, Thanks for finding and fixing the mysterious half-symbol offset! -- Joe On 11/26/2015 8:53 AM, Steven Franke wrote: > Hi Joe, > > Sleep is a wonderful thing. I found the problem right away this morning. The > first pulse generated by jt65sim (which is a sync pulse) *was* a run

Re: [wsjt-devel] dt offset of 0.2s

Thanks Bill. I see that INT would have worked. By the way, with reference to your speculation yesterday that we might have inserted a fudge factor to account for delays — at present there are *no* fudge factors inserted in the dt-estimation process that I am aware of. I went on a crusade a whi

Re: [wsjt-devel] dt offset of 0.2s

On 26/11/2015 13:53, Steven Franke wrote: > I found the problem right away this morning. Hi Steve, D'oh! I stared at that line with the NINT(i/sps)+1 for ages knowing the problem had to be there somehow! Actually in this case INT(i/sps)+1 is probably all that is required as we are dealing with

Re: [wsjt-devel] dt offset of 0.2s

Hi Joe, Sleep is a wonderful thing. I found the problem right away this morning. The first pulse generated by jt65sim (which is a sync pulse) *was* a runt. It was half as long as it should have been — essentially, the wave form was starting promptly at 1.0s into the file, but it was starting ha

Re: [wsjt-devel] DT values in JT65

> On a related matter: I note that the diaplayed DT values are lower by > 0.2 s than what I think they should be, based on the test files > generated by jt65sim. Right now, I don't know where this 0.2 s offset > is coming from. (It looks like half a symbol, maybe?) I don’t know where it’s com

Re: [wsjt-devel] DT values in JT65

On 25/11/2015 18:53, Michael Black wrote: > So...given an accurate clock shouldn't 0 be the common result instead > of 0.1? Propagation shouldn't bump it up to 0.1, should it? > And are you saying negative offsets are due to propagation since > positive are only due to clock errors? Positive DT

Re: [wsjt-devel] DT values in JT65

So...given an accurate clock shouldn't 0 be the common result instead of 0.1? Propagation shouldn't bump it up to 0.1, should it? And are you saying negative offsets are due to propagation since positive are only due to clock errors? 73 Mike W9MDB

Re: [wsjt-devel] DT values in JT65

On 25/11/2015 18:33, Michael Black wrote: > Don't know if this helps but here's a histogram from my ALL.TXT file > that shows 0.1 as the common offset. This is 1M entries...an > interesting lack of 0.8 dts...hmmm...there's only one in my file. How > is DT rounded? 0.1 sounds like would includ

Re: [wsjt-devel] DT values in JT65

Don't know if this helps but here's a histogram from my ALL.TXT file that shows 0.1 as the common offset. This is 1M entries...an interesting lack of 0.8 dts...hmmm...there's only one in my file. How is DT rounded? 0.1 sounds like would include all the delay in getting the signal started and the

Re: [wsjt-devel] DT values in JT65

Hi Bill, As you noted, these latencies won't cancel out -- they'll be cumulative. One reason why I don't see this as a very big issue is that whatever these latencies (and additional ones from the receiver itself) may be, they are *very* unlikely to be as large as the uncertainty we have alw

Re: [wsjt-devel] DT values in JT65

On 25/11/2015 17:46, Bill Somerville wrote: > Perhaps it is as simple as the latencies cancelling out Scratching my head here, surely all latencies should be additive and only add delay so I think the above is not correct. 73 Bill G4WJS. --

Re: [wsjt-devel] DT values in JT65

On 25/11/2015 17:37, Joe Taylor wrote: > However, in your audio loop back test you also have a latency on both > audio output and audio input channels. Possibly these amount to as much > as 0.2 s ? Understood, but it was suspicious that I get exactly 0.0 unless we have fudge factors in place some

Re: [wsjt-devel] DT values in JT65

Hi Bill, On 11/25/2015 11:56 AM, Bill Somerville wrote: > On 25/11/2015 16:47, Joe Taylor wrote: >> On a related matter: I note that the diaplayed DT values are lower by >> 0.2 s than what I think they should be, based on the test files >> generated by jt65sim. Right now, I don't know where this

Re: [wsjt-devel] DT values in JT65

On 25/11/2015 16:47, Joe Taylor wrote: > On a related matter: I note that the diaplayed DT values are lower by > 0.2 s than what I think they should be, based on the test files > generated by jt65sim. Right now, I don't know where this 0.2 s offset > is coming from. (It looks like half a symbol,

[wsjt-devel] DT values in JT65

Hi Steve and all, I've committed some changes that increase the range of acceptable DT values in JT65 mode to -2 to +5 s. This should fix the occasional garbage decodes I've been seeing on strong signals with DT < -1.1 s -- I think they are the "circular shift, off-by-one-symbol" cases you me

Re: [wsjt-devel] DT offset in user settings

;  >> >>Date: Wed, 06 May 2015 19:55:06 +0100 >>From: Bill Somerville < g4...@classdesign.com > >>Subject: Re: [wsjt-devel] DT offset in user settings >>To: wsjt-devel@lists.sourceforge.net >>Message-ID: < 554a638a.2090...@classdesign.com > >>Content-Typ

Re: [wsjt-devel] DT offset in user settings

On Wed,5/6/2015 11:55 AM, Bill Somerville wrote: > One possible source of audio latency is any re-sampling done by the > operating system, this can be eliminated by ensuring that the default > sample for the sound card is 48 kHz. Older versions of MS Windows like > XP and Vista are particularly

Re: [wsjt-devel] DT offset in user settings

t; >Subject: Re: [wsjt-devel] DT offset in user settings >To: wsjt-devel@lists.sourceforge.net >Message-ID: < 554a638a.2090...@classdesign.com > >Content-Type: text/plain; charset="utf-8" > >On 06/05/2015 15:22, ? ? wrote: >> >> Dear Sirs: >Hi I

Re: [wsjt-devel] DT offset in user settings

On 06/05/2015 15:22, Игорь Ч wrote: Dear Sirs: Hi Igor, I have just found with Asus Xonar U7 USB sound card DT is by approximately 0.3 greater than with USB Sound Blaster: Sound Blaster: 1300 -4 0.6 1327 # AK1P GM4SQM -15 1300 -8 0.1 1782 # IC8DAK UN7GBY MN83 1301 -3 0.3 1414 # R9MR DH1

[wsjt-devel] DT offset in user settings

Dear Sirs: I have just found with  Asus Xonar U7 USB sound  card DT is by approximately 0.3 greater than with USB Sound Blaster: Sound Blaster: 1300 -4 0.6 1327 # AK1P GM4SQM -15 1300 -8 0.1 1782 # IC8DAK UN7GBY MN83 1301 -3 0.3 1414 # R9MR DH1BBH -19 1301 -1 0.6 1780 # UN7GBY IC8DAK -11 --