Re: [wsjt-devel] possible bugs in WSJT-X 1.9.0-rc3
While I'm not running the same hardware, and running win 10, I've had the same two things happen to me several times. In addition I've had Halt Tx not halt. tnx 73 Dwight NS9I On 4/5/2018 1:37 AM, Scott Davis wrote: Hi. I just joined this list. I'm enjoying using FT8 on HF bands. Many thanks to Joe Taylor and Steve Franke. I'd like to report what I think is buggy behavior in the FT8 auto-sequencing state machine. In future I hope to contribute to development of this very cool software. Environment My radio is a Flex 6300. My computer is a MacBook Pro running macOS 10.12.6. I'm using VMware Fusion Pro 8.5.10 to run a Windows 8.1 VM, which is up-to-date with "important" patches. I'm using SmartSDR 1.11.12 and WSJT-X 1.9.0-rc3. Example 1 In the following QSO, I responded to his CQ but didn't hear back right away and disabled transmission. A minute later I received a -19 signal report from him (A) and double-clicked on it. The software sent a -20 signal report to him (B). I think it should have sent R-20, with an R. (Nonetheless, the QSO proceeded to a successful conclusion.) 015730 -20 -0.2 1378 ~ CQ N0GOS DN70 015747 Tx 2258 ~ N0GOS W6SDD DN70 015815 Tx 2258 ~ N0GOS W6SDD DN70 ... 015930 -20 -0.2 1377 ~ W6SDD N0GOS -19 <<-- (A) 015946 Tx 2258 ~ N0GOS W6SDD -20 <<-- (B) 020015 Tx 2258 ~ N0GOS W6SDD -20 020030 -22 -0.3 1377 ~ W6SDD N0GOS R-22 020046 Tx 2258 ~ N0GOS W6SDD RRR 020100 -20 -0.3 1377 ~ W6SDD N0GOS 73 020115 Tx 2258 ~ N0GOS W6SDD 73 Example 2 This next QSO proceeded normally up to the point where he sent RRR and I sent 73. I have the software configured to disable transmission once I have sent 73. A minute later he sent RRR again (C). I double-clicked on it. The software sent him an R-18 signal report (D). I think it should have sent 73. I selected 73 from the list of messages and the software sent 73 on my next turn. 041145 -17 0.4 1433 ~ CQ KK4EUN EM60 041201 Tx 2228 ~ KK4EUN W6SDD DN70 041215 -15 0.4 1433 ~ W6SDD KK4EUN -23 041230 Tx 2228 ~ KK4EUN W6SDD R-15 041245 -20 0.4 1433 ~ W6SDD KK4EUN RRR 041300 Tx 2228 ~ KK4EUN W6SDD 73 041315 -10 0.4 1423 ~ F8NHF KE8EF R-04 041415 -7 0.4 1423 ~ F8NHF KE8EF 73 041415 -18 0.3 1433 ~ W6SDD KK4EUN RRR <<-- (C) 041432 Tx 2228 ~ KK4EUN W6SDD R-18 <<-- (D) 041500 Tx 2228 ~ KK4EUN W6SDD 73 I hope this is helpful. Best regards, Scott Davis W6SDD -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] possible bugs in WSJT-X 1.9.0-rc3
Hi. I just joined this list. I'm enjoying using FT8 on HF bands. Many thanks to Joe Taylor and Steve Franke. I'd like to report what I think is buggy behavior in the FT8 auto-sequencing state machine. In future I hope to contribute to development of this very cool software. Environment My radio is a Flex 6300. My computer is a MacBook Pro running macOS 10.12.6. I'm using VMware Fusion Pro 8.5.10 to run a Windows 8.1 VM, which is up-to-date with "important" patches. I'm using SmartSDR 1.11.12 and WSJT-X 1.9.0-rc3. Example 1 In the following QSO, I responded to his CQ but didn't hear back right away and disabled transmission. A minute later I received a -19 signal report from him (A) and double-clicked on it. The software sent a -20 signal report to him (B). I think it should have sent R-20, with an R. (Nonetheless, the QSO proceeded to a successful conclusion.) 015730 -20 -0.2 1378 ~ CQ N0GOS DN70 015747 Tx 2258 ~ N0GOS W6SDD DN70 015815 Tx 2258 ~ N0GOS W6SDD DN70 ... 015930 -20 -0.2 1377 ~ W6SDD N0GOS -19 <<-- (A) 015946 Tx 2258 ~ N0GOS W6SDD -20 <<-- (B) 020015 Tx 2258 ~ N0GOS W6SDD -20 020030 -22 -0.3 1377 ~ W6SDD N0GOS R-22 020046 Tx 2258 ~ N0GOS W6SDD RRR 020100 -20 -0.3 1377 ~ W6SDD N0GOS 73 020115 Tx 2258 ~ N0GOS W6SDD 73 Example 2 This next QSO proceeded normally up to the point where he sent RRR and I sent 73. I have the software configured to disable transmission once I have sent 73. A minute later he sent RRR again (C). I double-clicked on it. The software sent him an R-18 signal report (D). I think it should have sent 73. I selected 73 from the list of messages and the software sent 73 on my next turn. 041145 -17 0.4 1433 ~ CQ KK4EUN EM60 041201 Tx 2228 ~ KK4EUN W6SDD DN70 041215 -15 0.4 1433 ~ W6SDD KK4EUN -23 041230 Tx 2228 ~ KK4EUN W6SDD R-15 041245 -20 0.4 1433 ~ W6SDD KK4EUN RRR 041300 Tx 2228 ~ KK4EUN W6SDD 73 041315 -10 0.4 1423 ~ F8NHF KE8EF R-04 041415 -7 0.4 1423 ~ F8NHF KE8EF 73 041415 -18 0.3 1433 ~ W6SDD KK4EUN RRR <<-- (C) 041432 Tx 2228 ~ KK4EUN W6SDD R-18 <<-- (D) 041500 Tx 2228 ~ KK4EUN W6SDD 73 I hope this is helpful. Best regards, Scott Davis W6SDD -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] possible bugs
I've never heard of the reason why it was ever connected in the first place.Only thing I can think of is somebody wanted the meter to reflect what the waterfall was doing which is of dubious use now that the Flatten option is a much better solution. And it really did not affect the "input dB reading". When it was hooked up it affected the "waterfall Db level". de Mike W9MDB From: Neil Zampella To: wsjt-devel@lists.sourceforge.net Sent: Tuesday, July 11, 2017 8:49 PM Subject: Re: [wsjt-devel] possible bugs OK Bill .. but why did it affect the input dB reading ? Just curious. On 7/11/2017 5:32 PM, Bill Somerville wrote: > On 11/07/2017 22:24, Neil Zampella wrote: >> the slider is no longer a 'digital gain' that affects sound input, it >> only affect the graph. > > Hi Neil, > > it never has been a digital gain control for anything but the > waterfall and 2D spectrum graph. That is why it has been disconnected > from the input level indicator. > > 73 > Bill > G4WJS. > > > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] possible bugs
OK Bill .. but why did it affect the input dB reading ? Just curious. On 7/11/2017 5:32 PM, Bill Somerville wrote: On 11/07/2017 22:24, Neil Zampella wrote: the slider is no longer a 'digital gain' that affects sound input, it only affect the graph. Hi Neil, it never has been a digital gain control for anything but the waterfall and 2D spectrum graph. That is why it has been disconnected from the input level indicator. 73 Bill G4WJS. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Possible bugs v2
Hi again, I see my error with the slider, it do say "digital gain graph windows" I assume it was same as its been few years with wsjt-x 1.7. As it change level display dB level, in the past. I need to learn better of new features on 1.8.rc1. Too excited to get on the band with it, so rtfm was obvious thing to being ignored. I'll read the manual and my absence from here is the marker all is good ;o) Thanks of the comments Good night from cold rainy Helsinki. : Jari / OH2FQV -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] possible bugs
On 11/07/2017 22:24, Neil Zampella wrote: the slider is no longer a 'digital gain' that affects sound input, it only affect the graph. Hi Neil, it never has been a digital gain control for anything but the waterfall and 2D spectrum graph. That is why it has been disconnected from the input level indicator. 73 Bill G4WJS. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] possible bugs
Jari, the slider is no longer a 'digital gain' that affects sound input, it only affect the graph. Input adjustment is either through your OS sound mixer, or physically from your rig. If you put your mouse over the slider it will give the 'tool tip' about this. I've got a KX3, and adjust the sound input using the AF knob. Neil, KN3ILZ On 7/11/2017 4:59 PM, Jari A wrote: Hello, I'm new here, so apologies if I cause extra havoc. WSJT-X 1.8.0-rc1 Windows 7 pro 64 bits I think I seen few anomalies: Digital gain does not change input level, bar remain green and at 62dB level, even no input signal. Second thing I note is TX5. If I do CQ and wish to mark TX 5 after report, autoseq jumps to TX4, no matter what. After sequence has started, if I'm quick I can press send now button to get my 73 out. If I manage to type ( opponent station who replied to me) call RRTU73 to TX5 field, it changes to call call 73 format. Dunno if these are worth for anything, but atleast I enbarrase myself at very first message to this list :o) Very best regards, : Jari / OH2FQV -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] possible bugs
I just went through this with another user and he had to take out some very noisy cards from his desktop.With no input signal you should see pretty much no signal. The input level has no control anymore from WSJT-X...it never did control the recording level...only the waterfall level. It was very misleading to those setting audio like you. You need to change your recording device to 0dB gain...then adjust your audio on the rig input in analog space to 30dB to maybe 50dB or so on the WSJT-X meter. de Mike W9MDB From: Jari A To: wsjt-devel@lists.sourceforge.net Sent: Tuesday, July 11, 2017 4:01 PM Subject: [wsjt-devel] possible bugs Hello, I'm new here, so apologies if I cause extra havoc. WSJT-X 1.8.0-rc1 Windows 7 pro 64 bits I think I seen few anomalies: Digital gain does not change input level, bar remain green and at 62dB level, even no input signal. Second thing I note is TX5. If I do CQ and wish to mark TX 5 after report, autoseq jumps to TX4, no matter what. After sequence has started, if I'm quick I can press send now button to get my 73 out. If I manage to type ( opponent station who replied to me) call RRTU73 to TX5 field, it changes to call call 73 format. Dunno if these are worth for anything, but atleast I enbarrase myself at very first message to this list :o) Very best regards, : Jari / OH2FQV -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] possible bugs
Hello, I'm new here, so apologies if I cause extra havoc. WSJT-X 1.8.0-rc1 Windows 7 pro 64 bits I think I seen few anomalies: Digital gain does not change input level, bar remain green and at 62dB level, even no input signal. Second thing I note is TX5. If I do CQ and wish to mark TX 5 after report, autoseq jumps to TX4, no matter what. After sequence has started, if I'm quick I can press send now button to get my 73 out. If I manage to type ( opponent station who replied to me) call RRTU73 to TX5 field, it changes to call call 73 format. Dunno if these are worth for anything, but atleast I enbarrase myself at very first message to this list :o) Very best regards, : Jari / OH2FQV -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
