Were you operating at the time?
That message is not a failure...it shows an audio catchup due to delayed audio
input which is suspicious as normally you shouldn't see that happen. So the
question is if the wave file got saved for that time period.
Each file name has the date/time encoded in it. Need to see a directory of the
files around that time and I hope you have File/Save All turned on, right?
Would like to see 054430 and 054445 and 054500 if you have it.
If you were just listening at the time the last file is either 054430 or
054445. If it's 054430 then your audio stream completely stopped. If it's
054445 then something else is going on.
#1 On your audio devices in the sound control panel....do either of them have a
green checkmark on them?#2 Have you reinstalled your USB devices?#3 Check your
event viewer and see if there are any messages around that time.
On Sunday, July 7, 2019, 03:55:20 AM CDT, Hasan al-Basri
<[email protected]> wrote:
OK, Mike; it failed at 054430 last night:
054430 -9 -0.1 1767 ~ EA4LU WA2VCQ EL87
40.463 dataSink1 33/50, k=114048, dT=3ms, catchup
Test Run Stared (timestamp of first saved file) on:
07/05/2019 @ 0956
the last decode I have in save file is timestamped:
07/07/2019 0200
Curiously,there is a big gap between it and 2nd to last save file:
07/07/2019 0044
I don't know why the last saved file is an hour and 16 minutes after the 2nd to
last....I guess it could be that 40m was very quiet at that time, but I'm
skeptical.
Let me know if you need any of the saved files and if so, which ones.
Note;
Failure was identical to all others. Decoding stopped, now Blue Decode light
does not come on.
Audio Thermometer is normal , sigs show on waterfall.
Here is a question:
If this is a single catchup eror, why doesn't X just reset itself and resume on
the next sequence? ...and why would it require reboot to get X working again?
I tried shutting down and restarting, same issue, which is what I noticed b4,
once it fails, only a reboot restores decoding.
73, N0AN
On Sat, Jul 6, 2019 at 10:32 PM Black Michael <[email protected]> wrote:
You can run a 2nd copy of WSJT-X (perhaps the other version that had problems?)
and see if it locks up.
Just add the -r option and pick a name
wsjtx -r test
de Mike W9MDB
On Saturday, July 6, 2019, 04:57:44 PM CDT, Hasan al-Basri
<[email protected]> wrote:
31 hours and counting since I installed the debug version you sent me the link
to. No errors. Will report more tomorrow morning.I can't imagine that this
install somehow fixed the issue?73, N0ANHasan
On Sat, Jul 6, 2019 at 2:38 PM Black Michael via wsjt-devel
<[email protected]> wrote:
What web browser do you use? There aren't a lot of these report so it doesn't
seem like this is a common problem otherwise we'd hear more about it5.
There has to be something in common.
So what does your audio path look like? Rig, sound card, USB Hub?, PC model.
de Mike W9MDB
On Saturday, July 6, 2019, 02:32:27 PM CDT, Rick Drexel <[email protected]>
wrote:
Your observations match those I have seen for about a year. I've tried to
find a common set of circumstances that always cause the failure but have had
no luck. I use WSJT-X in FT8 receive mode and PSKREPORTER to check band
performance over a long time period. After a random amount of time, WSJT-X
come to a halt. Specifically the Wide Graph Display and the Band Activity
Display stop updating. The UTC in the Wide Graph Display no longer matches the
UTC in the bottom left portion of the Main window. There is no correlation
between the activity on the band and the time it takes to hang. Rarely does it
not hang.
As a software developer this has all the hallmarks of a race condition failure.
Two (or more) threads update a shared resource without using a LOCK, UPDATE,
UNLOCK sequence. During a thread context swap one of the threads reads the
value, loses control to another thread that updates the value, then the first
thread gets scheduled and writes back its stale value. The result is undefined
behavior.
Most of the time there is no conflict. Even under a heavy load. Then it fails
unexpectedly. This makes it extremely difficult to debug.
To recover I have to exit out of WSJT-X and restart it.
This might not be the root cause but I would put it high on my list of the
usual suspects.
73, Rick
WK1P
From: Peter Putnam <[email protected]>
Sent: Wednesday, July 3, 2019 3:06 PM
To: [email protected]
Subject: [wsjt-devel] WSJT Audio Input Loss Greetings,
I have been using WSJT-X quite successfully for several years during
June VHF Contests. I experienced a failure of the WSJT program to accept
received audio input after several hours of proper operation during the
recent Field Day exercise.
I'll provide a brief outline and reply with more detail, should it be
needed.
My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The
WSJT-X software version is 2.0.1 7ddcb7.
My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX"
program that interfaces various applications that wish to receive the
audio stream. WSJT accepts the stream and displays results on the Wide
Graph and a small audio signal-strength window. Activity proceeded
normally for the first three hours of Field Day, until both the Wide
Graph and the audio signal-strength stopped showing any incoming audio.
I can't offer any help on what might have caused the problem. It was
abrupt and seemingly unrelated to any other system actions. I am unable
to reproduce the problem.
Several operators spent several hours speculating about what a solution
might be. Program restarts and computer re-boots (time-tested favorite
of generations) changed nothing. The only useful clue was that the DAX
audio output stream was present and could be re-directed to Fldigi, but
not to WSJT-X.
I was able to restore operation for a brief period by stopping WSJT,
renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour.
Repeating the procedure provided operation for the rest of Field Day.
The two .ini files that were renamed are available for your inspection,
along with the one that continued to function.
Any suggestions you can offer to prevent a recurrence would be greatly
appreciated.
Regards,
Peter
NI6E
_______________________________________________
wsjt-devel mailing list
[email protected]
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7Cc8a88765c47b45e54e0208d6ffea13fc%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636977778175354267&sdata=QIhhN8eBXU7WkgMKIK4WOGh%2BO2Zt6d3mRyQ5qFFV%2FGM%3D&reserved=0
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
