Re: [wsjt-devel] WSJT-X 2.2.2 GA Release: crash with wspr / band hopping
On 22/06/2020 19:40, Bill Somerville wrote: On 22/06/2020 19:21, roland.hartm...@web.de wrote: Hi Joe, have updated from 2.2.1 to 2.2.2. System: Win-10 x64 Installation with de-installation and afterwards installation. On WSPR I get a crash with this error message. Seems when the frequency should be changed via Band Hopping option: Hi Roland, there were some changes in the code that runs the user_hardware application, clearly I have screwed up somewhere. Thanks for the issue report, I will sort it out, I'll see if there is a workaround as well. 73 Bill G4WJS. Hi Roland and all, I can confirm this is a defect in WSJT-X v2.2.2. There is no practical workaround so I can only suggest reverting to WSJT-X v2.2.1 if you intend to user WSPR automatic band hopping. The issue will be fixed in the next release, sorry for the inconvenience. Note that this issue only affects WSPR automatic band-hopping, if you don't use that then there is no problem. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Not displaying decode
On 23/06/2020 02:11, Chris Sullivan wrote: Windows-10 V2.2.0 I had been idly listening to 6m FT8 and saw that a strong station is not being displayed in the band activity window even though JT-Alert is displaying the call. So the 'blank line' between periods displays but no decodes appear in-between, which I've never seen before. The station in question was the only one visible on the waterfall. It might also be relevant that it had been worked before, according to JT-Alert. Nothing else unusual to report. When I closed WSJT-X and restarted, it started to behave normally. I have attached a snapshot although I don't know if it will get through. While writing this, I saw 11 successful decodes from the same station then it started doing it again (five times, but now the station has faded out). Chris VE3NRT Chris, that station decodes with DT values of +0.2 s and -1.9 s over an interval of 1 minute, one of you probably has a problem with clock accuracy. Make sure you don't have two time adjustment applications running simultaneously. If you are running Meinberg NTP or one of the lesser time sync applications you must ensure that the Window Internet Time sync facility is switched off. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.2.2 GA Release: crash with wspr / band hopping
Il 22/06/20 16:06, John Nelson via wsjt-devel ha scritto: > Bill, > > I confirm this happens on a Mac as well with v2.2.2 > > — John G4KLA > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel Curious of this report and despite I almost never use WSPR, I wanted to verify the issue and it happens on Linux as well. But I have to say that all my "user_hardware nnn" files are empty and that WSJT-X is crashing, or better quitting, only by clicking on the "OK button" of the Subprocess error message if I do not click on it the applications keeps running normally. -- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Not displaying decode
Windows-10 V2.2.0 I had been idly listening to 6m FT8 and saw that a strong station is not being displayed in the band activity window even though JT-Alert is displaying the call. So the 'blank line' between periods displays but no decodes appear in-between, which I've never seen before. The station in question was the only one visible on the waterfall. It might also be relevant that it had been worked before, according to JT-Alert. Nothing else unusual to report. When I closed WSJT-X and restarted, it started to behave normally. I have attached a snapshot although I don't know if it will get through. While writing this, I saw 11 successful decodes from the same station then it started doing it again (five times, but now the station has faded out). Chris VE3NRT ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.2.2 GA Release: crash with wspr / band hopping
Bill, I confirm this happens on a Mac as well with v2.2.2 — John G4KLA smime.p7s Description: S/MIME cryptographic signature ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.2.2 GA Release: crash with wspr / band hopping
On 22/06/2020 19:21, roland.hartm...@web.de wrote: Hi Joe, have updated from 2.2.1 to 2.2.2. System: Win-10 x64 Installation with de-installation and afterwards installation. On WSPR I get a crash with this error message. Seems when the frequency should be changed via Band Hopping option: Hi Roland, there were some changes in the code that runs the user_hardware application, clearly I have screwed up somewhere. Thanks for the issue report, I will sort it out, I'll see if there is a workaround as well. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] WSJT-X 2.2.2 GA Release: crash with wspr / band hopping
Hi Joe, have updated from 2.2.1 to 2.2.2. System: Win-10 x64 Installation with de-installation and afterwards installation. On WSPR I get a crash with this error message. Seems when the frequency should be changed via Band Hopping option: Manual change of the frequency is working without error. Is happened only with activated Band Hopping option. My understanding is, that the soft check for the (normally optional) user file for frequency check. First Try of workaround: Created a file 'user_hardware.bat' with content '@exit 0'. No difference, crash with same message. Next step: Renaming of 'user_hardware.bat' to 'user_hardware' (without extension). No it crash with this message: I went back to version 2.2.1 . 73 Roland, DK4RH ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] FT8 Decode lockup observations
Bill, As stated in my post, replaying .wav files that where saved during when the original failure occurred does NOT cause the failure to recur. Also note that while WSJT-X is in the fault mode, ALT-Z only clears the indicator until the next time the decoder is supposed to run (~ 12 sec ). And then the decode indicator stays on again. AL, K0VM On 6/21/2020 10:28 AM, Bill Somerville wrote: On 21/06/2020 16:10, Al wrote: ( WSJT-X 2.2.1, Win 10 ) From time to time, usually while monitoring 6m over night, I get a a Decode lockup. The Decode button is ON continuously, wide graph is still running, wav files still being saved and no decodes are displayed in the band activity window. Seems more frequent with 2.2.1 than 2.1.2. Stopping and restarting WSJT will clear the issue. Replaying .wav files for the time when the lock up occurred does not induce a lockup. When the lock up occurs, an 'Erase Band activity' will result in a brief pause in the highlight button being ON ( i.e. at about 12 seconds into the cycle, the button toggles off for about 1 second, and then back on until the next 12 second epoch. ) If I issue a ALT-Z at the beginning of a cycle, the decode indicator goes off until the next 12 sec epoch and then stays on. If I pause decodes by turning off the monitor, issue a ALT-Z and playback a .wav file, the decode indicator comes on immediately and stays on. ( Even with .wav files that playback correctly after WSJT has been restarted. ) Once locked up, changing the decode depth has no effect on recovery attempts. If you have addition debugging trials. AL, K0VM Hi Al, if you can provide a .WAV file or minimal sequence of .WAV files that can reproduce this issue when playing them back in WSJT-X, then please provide them. The FT8 decoder can be "unfrozen" by hitting the Alt+Z key when this as yet undiagnosed issue occurs. See "Menu->Help->Shortcut keys" for a reminder. 73 Bill G4WJS. ___ 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
Re: [wsjt-devel] FT8 Decode lockup observation
Hi Bill – Already tried using Option+letter instead of Alt+letter …. No luck. The Ctrl+letter and Shift+letter keyboard shortcuts work on the Mac keyboard with a Mac Mini … none of the Option+letter (aka Alt+letter) work in 2.2.1 as far as I can see. -Tony On 22/06/2020 11:16, Tony wrote: > > Hi Bill ? > > I was interested in keeping the Alt-Z shortcut in mind that you > mentioned to Al. ?I have found on WSJT-X 2.2.1 that most shortcuts > work on my MacMini (with a Mac keyboard), but no matter what I try I > can not get any of the ?Alt? shortcuts to work.? Mac keyboards have > the ?Alt/Option? key.? Are ?Alt? shortcuts supported for the Mac?? Is > there some other keyboard trick on the Mac to get the ?Alt? > shortcuts?? I?m guessing these shortcuts were originally designed for > a PC environment.? (Set-up here is Mac-Mini to a FT-991.) > > Thanks, > > Tony ? AE0AU > Hi Tony, Alt+letter should be invoked by Option+letter, and Ctrl+letter should be invoked by Command+letter on Mac keyboards. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] WSJT-X 2.2.2 GA Release
WSJT-X 2.2.2 is a bug-fix release, mainly to incorporate the new RAC section PE (Prince Edward Island) into the FT8/FT4/MSK144 Contest Mode messages for ARRL Field Day. Several minor fixes and additions are described at the top of the Release Notes here: http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt Upgrading from earlier versions of WSJT-X should be seamless. There is no need to uninstall a previous version or move any files. Links to installation packages for Windows, Linux, and Macintosh are available here: http://physics.princeton.edu/pulsar/k1jt/wsjtx.html You can also download the packages from our SourceForge site: https://sourceforge.net/projects/wsjt/files/ It may take a short time for the SourceForge site to be updated. WSJT-X is licensed under the terms of Version 3 of the GNU General Public License (GPL). Development of this software is a cooperative project to which many amateur radio operators have contributed. If you use our code, please have the courtesy to let us know about it. If you find bugs or make improvements to the code, please report them to us in a timely fashion. Follow instructions in the WSJT-X User Guide here: http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0.html#SUPPORT We hope you will enjoy using WSJT-X Version 2.2.2. -- 73 from Joe, K1JT, Steve, K9AN, and Bill, G4WJS, for the entire WSJT Development Group ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] FT8 Decode lockup observation
On 22/06/2020 11:16, Tony wrote: Hi Bill – I was interested in keeping the Alt-Z shortcut in mind that you mentioned to Al. I have found on WSJT-X 2.2.1 that most shortcuts work on my MacMini (with a Mac keyboard), but no matter what I try I can not get any of the “Alt” shortcuts to work. Mac keyboards have the “Alt/Option” key. Are “Alt” shortcuts supported for the Mac? Is there some other keyboard trick on the Mac to get the “Alt” shortcuts? I’m guessing these shortcuts were originally designed for a PC environment. (Set-up here is Mac-Mini to a FT-991.) Thanks, Tony – AE0AU Hi Tony, Alt+letter should be invoked by Option+letter, and Ctrl+letter should be invoked by Command+letter on Mac keyboards. 73 Bill G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] FT8 Decode lockup observation
Hi Bill – I was interested in keeping the Alt-Z shortcut in mind that you mentioned to Al. I have found on WSJT-X 2.2.1 that most shortcuts work on my MacMini (with a Mac keyboard), but no matter what I try I can not get any of the “Alt” shortcuts to work. Mac keyboards have the “Alt/Option” key. Are “Alt” shortcuts supported for the Mac? Is there some other keyboard trick on the Mac to get the “Alt” shortcuts? I’m guessing these shortcuts were originally designed for a PC environment. (Set-up here is Mac-Mini to a FT-991.) Thanks, Tony – AE0AU Message: 1 Date: Sun, 21 Jun 2020 10:10:30 -0500 From: Al To: WSJT software development Subject: [wsjt-devel] FT8 Decode lockup observations Message-ID: Content-Type: text/plain; charset="utf-8"; Format="flowed" ( WSJT-X 2.2.1, Win 10 ) From time to? time, usually while monitoring 6m over night, I get a a Decode lockup.? The Decode button is ON continuously, wide graph is still running, wav files still being saved and no decodes are displayed in the band activity window. Seems more frequent with 2.2.1 than 2.1.2. Stopping and restarting WSJT will clear the issue. Replaying .wav files for the time when the lock up occurred does not induce a lockup. When the lock up occurs, an 'Erase Band activity' will result in a brief pause in the highlight button being ON ( i.e. at about 12 seconds into the cycle, the button toggles off for about 1 second, and then back on until the next 12 second epoch. ) If I issue a ALT-Z at the beginning of a cycle, the decode indicator goes off until the next 12 sec epoch and then stays on. If I pause decodes by turning off the monitor, issue a ALT-Z and playback a .wav? file, the decode indicator comes on immediately and stays on.? ( Even with .wav files that playback correctly after WSJT has been restarted. ) Once locked up, changing the decode depth has no effect on recovery attempts. If you have addition debugging trials. AL, K0VM -- next part -- An HTML attachment was scrubbed... -- Message: 2 Date: Sun, 21 Jun 2020 16:28:18 +0100 From: Bill Somerville To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] FT8 Decode lockup observations Message-ID: <2019f1d6-034a-9ea7-e69a-3f3deb1ef...@classdesign.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" On 21/06/2020 16:10, Al wrote: > ( WSJT-X 2.2.1, Win 10 ) > > From time to? time, usually while monitoring 6m over night, I get a a > Decode lockup.? The Decode button is ON continuously, wide graph is > still running, wav files still being saved and no decodes are > displayed in the band activity window. Seems more frequent with 2.2.1 > than 2.1.2. > > Stopping and restarting WSJT will clear the issue. Replaying .wav > files for the time when the lock up occurred does not induce a lockup. > > When the lock up occurs, an 'Erase Band activity' will result in a > brief pause in the highlight button being ON ( i.e. at about 12 > seconds into the cycle, the button toggles off for about 1 second, and > then back on until the next 12 second epoch. ) > If I issue a ALT-Z at the beginning of a cycle, the decode indicator > goes off until the next 12 sec epoch and then stays on.? If I pause > decodes by turning off the monitor, issue a ALT-Z and playback a .wav? > file, the decode indicator comes on immediately and stays on.? ( Even > with .wav files that playback correctly after WSJT has been restarted. ) > > Once locked up, changing the decode depth has no effect on recovery > attempts. > > If you have addition debugging trials. > > AL, K0VM Hi Al, if you can provide a .WAV file or minimal sequence of .WAV files that can reproduce this issue when playing them back in WSJT-X, then please provide them. The FT8 decoder can be "unfrozen" by hitting the Alt+Z key when this as yet undiagnosed issue occurs. See "Menu->Help->Shortcut keys" for a reminder. 73 Bill G4WJS. -- next part -- ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
