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 observations
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] FT8 Decode lockup observations
( 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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
