HI Bill,

That doesn't sound good -- hope I haven't screwed something up. (It wouldn't be the first time.)

I will try to see if I can reproduce the problem. In the meantime, if you can make a *.wav recording that illustrates the problem, please send it to me.

        -- Joe, K1JT

On 1/11/2014 12:33 PM, Bill Somerville wrote:
On 11/01/2014 17:29, Bill Somerville wrote:
Hi All,
Hi Again,

I have recently merged the changes up to r3632 into my working space
and during testing I am seeing JT9 signals decoded as JT65. Is anyone
else seeing this or have I messed up something locally here.
Looking at it more carefully it looks like a JT65 signal is being
reported on the wrong DF when I double click to decode again:

1724 -1 0.2 956 # VA3MJR KA8G RRR

1724 -7 0.2 1207 # CQ KF5REP EM02

1724 -1 0.8 1387 # KD5JHE K2QL FN22

1724 -2 0.1 1829 # KR4LU N8KDX EM98

1724 -25 0.8 2025 # KD5JHE K2QL FN22

1724 -15 0.2 2212 # N0GR OX3IO RRR

1724 -10 -3.6 3240 # N0GR OX3IO RRR

1724 -10 -3.6 3240 # N0GR OX3IO RRR

1724 -10 -3.6 3240 # N0GR OX3IO RRR

1724 -10 -3.6 3240 # N0GR OX3IO RRR

1724 -10 -3.6 3240 # N0GR OX3IO RRR

1724 -10 -3.6 3240 # N0GR OX3IO RRR



73
Bill
G4WJS.
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel




_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel

Reply via email to