|
From: Bill S. <g4...@cl...> - 2020-07-13 09:14:32
|
On 13/07/2020 02:48, David Bean (KC2WUF) via wsjt-devel wrote: > I haven't yet figured out what sequence is causing what I am seeing, > but there are times when the new FT8 decoding for a new time sequence > will timestamp the decodes with the previous decoding timestamp. > During Field Day this was fine as I was often transmitting during the > between timestamp and the decodes would fall in the same even/odd > sequence. > > It is during normal operation where I notice that I end up calling a > station on the same even/odd sequence and we can't work each other. > The only thing I have noticed about this issue is that if my > RxFreqency station doesn't decode early, it may be the only station > that decodes with the correct timestamp as the last decoded signal > while all the rest will be placed with the previous decode timestamp. > I have noticed a greater number of ops calling while the station they > are calling is also transmitting. > > I'm not sure how to get data to look at without trying to film the > session although it doesn't always happen. > > I am running Windows 10 Home on a AMD A6-7310 2.00 GHz Laptop with 8GB > RAM. > > I originally tried to write this post after Field Day and then again > July 7th, but I still am having problems seeing this issue crop up > again. Just wanted to post this in case others have noticed same. > > 73 David KC2WUF David, when reporting issues it is essential that you state which version of WSJT-X you are using. 73 Bill G4WJS. |