Re: [wsjt-devel] WSJT Audio Input Loss

[Rick Drexel]

Bill,

Disabling the USB power down on timeout was a good idea but no luck in solving 
the issue.

I don't use a screen saver because I sometimes run my C++ code for days.

Windows System for Linux (WSL) built HamLib but not WSJT-X.   I'm going to try 
to spend some time getting it to build wsjtx.

73, Rick, WK1P



From: Bill Somerville 
Sent: Monday, July 8, 2019 6:39 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT Audio Input Loss

On 08/07/2019 21:57, Rick Drexel wrote:
I started up WSJT-X on 10 meters this morning and expected to find it running 
when I got back home.  After all, there was no activity and therefore nothing 
to decode.  Nope, Wide Graph was frozen just as if I'd been monitoring a 
contest.  WSJT-X was the only app running all day.  I started it at 1000 UTC 
and it quit around 1135 UTC.  It failed after 1.5 hours.  Another random data 
point.  Which doesn't rule out the Race Condition possibility given the 4 
core/8 thread CPU it's running on.

Just curious.  How does WSJT-X make use of an Internet browser???

Hi Rick,

have you disabled power saving options on your USB hubs? Some monitor drivers 
cause issues with audio streams when they go into screen save mode. WSJT-X 
doesn't use any web browser although if you request the online help to open it 
will tell the operating system to open the relevant URL however it feels it 
should, which is normally by passing it to the default web browser, open the 
application if necessary.

73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Bill Somerville]

On 08/07/2019 21:57, Rick Drexel wrote:
I started up WSJT-X on 10 meters this morning and expected to find it 
running when I got back home.  After all, there was no activity and 
therefore nothing to decode.  Nope, Wide Graph was frozen just as if 
I'd been monitoring a contest.  WSJT-X was the only app running all 
day.  I started it at 1000 UTC and it quit around 1135 UTC.  It failed 
after 1.5 hours.  Another random data point.  Which doesn't rule out 
the Race Condition possibility given the 4 core/8 thread CPU it's 
running on.


Just curious.  How does WSJT-X make use of an Internet browser???


Hi Rick,

have you disabled power saving options on your USB hubs? Some monitor 
drivers cause issues with audio streams when they go into screen save 
mode. WSJT-X doesn't use any web browser although if you request the 
online help to open it will tell the operating system to open the 
relevant URL however it feels it should, which is normally by passing it 
to the default web browser, open the application if necessary.


73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Rick Drexel]

Band conditions being what they are,  I started up WSJT-X on 10 meters this 
morning and expected to find it running when I got back home.  After all, there 
was no activity and therefore nothing to decode.  Nope, Wide Graph was frozen 
just as if I'd been monitoring a contest.  WSJT-X was the only app running all 
day.  I started it at 1000 UTC and it quit around 1135 UTC.  It failed after 
1.5 hours.  Another random data point.  Which doesn't rule out the Race 
Condition possibility given the 4 core/8 thread CPU it's running on.

Just curious.  How does WSJT-X make use of an Internet browser???

Rick



From: Black Michael 
Sent: Saturday, July 6, 2019 5:57 PM
To: WSJT software development; pe...@ni6e.com; Rick Drexel
Subject: Re: [wsjt-devel] WSJT Audio Input Loss

We've heard a few people say IE has caused audio problems.

But...for the main testwhat happens if you run no browser at all?  And how 
often does it fail?

de Mike W9MDB





On Saturday, July 6, 2019, 04:48:26 PM CDT, Rick Drexel  wrote:


The rig is an Icom IC-7100 connected by a USB cable directly to a Windows 10 
64-bit desktop machine with 32 GB RAM. No sound card needed but I do have to 
check Settings to make sure WSJT-X Audio Tab hasn’t changed after a forced 
restart.

I use Firefox or IE to open PskReporter to see what’s been reported by WSJT-X 
during the monitoring period.

Rick WK1P




From: Black Michael via wsjt-devel 
Sent: Saturday, July 6, 2019 3:35:43 PM
To: pe...@ni6e.com; WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] WSJT Audio Input Loss

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  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 
Sent: Wednesday, July 3, 2019 3:06 PM
To: wsjt-devel@lists.sourceforge.net
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

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

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 paneldo 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 
 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 
lastI 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  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 
 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 
 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  
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 
Sent: Wednesday, July 3, 2019 3:06 PM
To: wsjt-devel@lists.sourceforge.net
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 

Re: [wsjt-devel] WSJT Audio Input Loss

[Hasan al-Basri]

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 lastI 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  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 <
> hbasri.schie...@gmail.com> 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, N0AN
> Hasan
>
>
> On Sat, Jul 6, 2019 at 2:38 PM Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> 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 
> 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 
> *Sent:* Wednesday, July 3, 2019 3:06 PM
> *To:* wsjt-devel@lists.sourceforge.net
> *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 

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

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 
 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 
 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  
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 
Sent: Wednesday, July 3, 2019 3:06 PM
To: wsjt-devel@lists.sourceforge.net
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
wsjt-devel@lists.sourceforge.net
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cc8a88765c47b45e54e0208d6ffea13fc%7C84df9e7fe9f640afb435%7C1%7C0%7C63698175354267sdata=QIhhN8eBXU7WkgMKIK4WOGh%2BO2Zt6d3mRyQ5qFFV%2FGM%3Dreserved=0
___
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

  ___
wsjt-devel mailing list

Re: [wsjt-devel] WSJT Audio Input Loss

[Rick Drexel]

The rig is an Icom IC-7100 connected by a USB cable directly to a Windows 10 
64-bit desktop machine with 32 GB RAM. No sound card needed but I do have to 
check Settings to make sure WSJT-X Audio Tab hasn’t changed after a forced 
restart.

I use Firefox or IE to open PskReporter to see what’s been reported by WSJT-X 
during the monitoring period.

Rick WK1P




From: Black Michael via wsjt-devel 
Sent: Saturday, July 6, 2019 3:35:43 PM
To: pe...@ni6e.com; WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] WSJT Audio Input Loss

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  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 
Sent: Wednesday, July 3, 2019 3:06 PM
To: wsjt-devel@lists.sourceforge.net
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
wsjt-devel@lists.sourceforge.net

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cc8a88765c47b45e54e0208d6ffea13fc%7C84df9e7fe9f640afb435%7C1%7C0%7C63698175354267sdata=QIhhN8eBXU7WkgMKIK4WOGh%2BO2Zt6d3mRyQ5qFFV%2FGM%3Dreserved=0<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel=02%7C01%7C%7C028b11a517d4493b190808d702496ee4%7C84df9e7fe9f640afb435%7C1%7C0%7C636980386726425860=6R6u7cKiy5Rvb2kB4AM3H0Kqd5bTbc8AM0DazKU%2B5KI%3D=0>

___
wsjt-de

Re: [wsjt-devel] WSJT Audio Input Loss

[Hasan al-Basri]

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, N0AN
Hasan


On Sat, Jul 6, 2019 at 2:38 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> 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 
> 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 
> *Sent:* Wednesday, July 3, 2019 3:06 PM
> *To:* wsjt-devel@lists.sourceforge.net
> *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
> wsjt-devel@lists.sourceforge.net
>
>
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cc8a88765c47b45e54e0208d6ffea13fc%7C84df9e7fe9f640afb435%7C1%7C0%7C63698175354267sdata=QIhhN8eBXU7WkgMKIK4WOGh%2BO2Zt6d3mRyQ5qFFV%2FGM%3Dreserved=0
> 
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

We've heard a few people say IE has caused audio problems.
But...for the main testwhat happens if you run no browser at all?  And how 
often does it fail?
de Mike W9MDB


 

On Saturday, July 6, 2019, 04:48:26 PM CDT, Rick Drexel  
wrote:  
 
 The rig is an Icom IC-7100 connected by a USB cable directly to a Windows 10 
64-bit desktop machine with 32 GB RAM. No sound card needed but I do have to 
check Settings to make sure WSJT-X Audio Tab hasn’t changed after a forced 
restart.  
I use Firefox or IE to open PskReporter to see what’s been reported by WSJT-X 
during the monitoring period.  
Rick WK1P 


From: Black Michael via wsjt-devel 
Sent: Saturday, July 6, 2019 3:35:43 PM
To: pe...@ni6e.com; WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] WSJT Audio Input Loss 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  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 
Sent: Wednesday, July 3, 2019 3:06 PM
To: wsjt-devel@lists.sourceforge.net
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
wsjt-devel@lists.sourceforge.net
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cc8a88765c47b45e54e0208d6ffea13fc%7C84df9e7fe9f640afb435%7C1%7C0%7C63698175354267sdata=QIhhN8eBXU7WkgMKIK4WOGh%2BO2Zt6d3mRyQ5qFFV%2FGM%3Dreserved=0
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/lis

Re: [wsjt-devel] WSJT Audio Input Loss

[VE3FBZ]

Yeah, in the old days of data bases we used to call that ac”deadly embrace”


 Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca 




> On Jul 6, 2019, at 14:54, Rick Drexel  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 
> Sent: Wednesday, July 3, 2019 3:06 PM
> To: wsjt-devel@lists.sourceforge.net
> 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
> wsjt-devel@lists.sourceforge.net
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cc8a88765c47b45e54e0208d6ffea13fc%7C84df9e7fe9f640afb435%7C1%7C0%7C63698175354267sdata=QIhhN8eBXU7WkgMKIK4WOGh%2BO2Zt6d3mRyQ5qFFV%2FGM%3Dreserved=0
> ___
> 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] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

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  
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 
Sent: Wednesday, July 3, 2019 3:06 PM
To: wsjt-devel@lists.sourceforge.net
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
wsjt-devel@lists.sourceforge.net
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cc8a88765c47b45e54e0208d6ffea13fc%7C84df9e7fe9f640afb435%7C1%7C0%7C63698175354267sdata=QIhhN8eBXU7WkgMKIK4WOGh%2BO2Zt6d3mRyQ5qFFV%2FGM%3Dreserved=0
___
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] WSJT Audio Input Loss

[Rick Drexel]

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 
Sent: Wednesday, July 3, 2019 3:06 PM
To: wsjt-devel@lists.sourceforge.net
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
wsjt-devel@lists.sourceforge.net
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cc8a88765c47b45e54e0208d6ffea13fc%7C84df9e7fe9f640afb435%7C1%7C0%7C63698175354267sdata=QIhhN8eBXU7WkgMKIK4WOGh%2BO2Zt6d3mRyQ5qFFV%2FGM%3Dreserved=0
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Claude Frantz]

On 7/6/19 5:59 AM, Black Michael via wsjt-devel wrote:

If you're not seeing dropout messages with the dropout debug version 
than your audio stream has completely stopped.

The dropouts are only checked when the audio packets are flowing.
You should be seeing a few messages at startup about dataSink1 like this 
to ensure you're running the dropout version.

Inline image


What is the reason why your PNG image has a ".jpg" suffix ?

Best wishes,
Claude (DJ0OT)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

If you're not seeing dropout messages with the dropout debug version than your 
audio stream has completely stopped.The dropouts are only checked when the 
audio packets are flowing.You should be seeing a few messages at startup about 
dataSink1 like this to ensure you're running the dropout version.

I would suggest uinstalling audio drivers, reboot, and reinstall.
de Mike W9MDB
 

On Friday, July 5, 2019, 08:49:10 PM CDT, Tod Farrell WE5TR 
 wrote:  
 
 Note: I screwed up and have no audio save to go with the notes. In the debug 
version were there other logs I can grab for you? 

Started this process around 14:00 UTC (all times in filenames and photos 
attached are UTC)
moved all audio files to give clean directory
rebooted
downloadeed debug app
set shortcuts for different rig names
ran time sync
made qso as test (10m)
14:15 UTC walking away
When I came by the PC on occasions i saw no decode (blue) or decode results had 
occured. When i stopped the test I grabbed the screenshot "190705 2355 gap..." 
which shows a gap from 163345 to 180515. During a few of these gaps i stood and 
watched task manager and the other WSJT-X instance looking for any issues. I 
couldnt identify anything. Note: During the gaps when I was observing i did see 
audio still in DAX which is what feeds the WSJT-X.
Today with this version, the decodes started again with no user intervention. 
The Flex SDR waterfall showed activity in the band. 

However, while I have the ALL files and the screenshots. I just now while 
typing this up see that I have no audio save files. (that is an oh crap moment)
screenshots attached. Filenames have date_time and situational description
73,Tod
WE5TR

On Fri, Jul 5, 2019 at 2:58 PM Hasan al-Basri  wrote:

INstalled and running Mike. Will watch for it...when it fails, it stays failed, 
so all I have to do is watch the Save directory last decode having started just 
now. Probably wont show until tomorrow. It'w working fine now, but it does for 
hours before the first freak out.73, N0ANHasan

On Fri, Jul 5, 2019 at 9:53 AM Hasan al-Basri  wrote:

Ok, I'll check it out. 

Downloading now, then will install right over the top of my existing 2.01Tnx73, 
N0AN
Hasan

On Fri, Jul 5, 2019 at 7:46 AM Black Michael  wrote:

This is version 2.0.1 with dropout debugging.If the decode light is not 
flashing then it sounds like you may have audio dropouts occurring.This version 
will show you when it fails with messages in the band activity window about 
"dropout".  You'll see a few messages on startup which is normal as the audio 
catches up.
https://www.dropbox.com/s/isxwjybws1i8u6f/wsjtx-2.0.1-win32-dropouts.exe?dl=1

de Mike W9MDB 

On Friday, July 5, 2019, 04:45:38 AM CDT, Hasan al-Basri 
 wrote:  
 
 Ok Mike, it decoded for > 24 hours but then stopped early this morning just 
before I got to the shack. 
Started 07/03/2019 @ 1723Stopped 07/05/2019 @ 0407 Both local
These are the file saved dates. Again, I had to reboot a few minutes ago to get 
it to start saving files/decoding again.
The rig was unattended from about 6 p.m. last  night until 4:19 a.m. when I 
came down to see if it was still decoding...I noticed it had stopped decoding 
12 minutes b4 I got down here.
Another symptom: When it stops decoding incoming signals, the Blue Decode light 
does NOT flash at the end of a sequence, ...even though the thermometer and the 
waterfall show sigs for the full sequence.
Any other suggestions?73, N0ANHasan

On Thu, Jul 4, 2019 at 5:35 AM Hasan al-Basri  wrote:

Ok, I'll check it out. Time is perfect and always is, I'm GPS locked to it.

When I got down here this morning it was still decoding full fill of JTAlert. 
...but it's only been 12 hours. (I did the remove driver, unplug it and let 
Win10 reinstall it at a reboot) . That's where I am now in my test.) 
Save none was checked, I just checked Save All, will provide if needed.
Here's hoping...
73, N0ANHasan

On Wed, Jul 3, 2019 at 10:37 PM Black Michael  wrote:

We seem to be hearing problems with a few people on both 2.0.1 and 2.1.0-rc7.  
2.0.1 has been out for a long time and if this was common I'd think we would 
have heard a lot more reports of the problem.Upgrading to 2.1.0-rc7 and back to 
2.0.1 should (and I emphasize should) just revert completely back to 2.0.1 
thought there is a bug with FT4 in that case.
The common thread probably is Windows updatesor time is off.  Check 
http://time.is to ensure you're time is reported as "Exact".
If you see waterfall activity but no decodes on of three things is likely 
happening.
#1 Time is off#2 WAV files are not being recorded.  Ensure Save/All is checked 
and see if WAV files are showing up in the Save folder.  One user found using 
Remote Desktop that audio files weren't being saved.  TeamViewer worked 
though.#3 Audio corrupted.  If WAV files are showing up but not decoding and 
your time is correct then send in a few audio files so we can look at them.

de Mike W9MDB

 

On Wednesday, July 

Re: [wsjt-devel] WSJT Audio Input Loss

[Hasan al-Basri]

Not an issue, I monitor CPU at all times, and keep in mind, once it stops
decoding, even one time, it never resumes without a reboot.
73, N0AN
Hasan


On Fri, Jul 5, 2019 at 10:14 AM Roy Gould  wrote:

> I have had the problem of the Decode button not coming on after the end of
> a receive interval. In my case I found the problem to be that the computer
> was being overloaded by high CPU usage of a web browser. This occurred with
> Edge, Chrome, or Firefox. This high CPU usage was seen by Task Manager. The
> solution was to close the web browser.  What does Task Manager reveal in
> your case?
>
> On Fri, Jul 5, 2019 at 8:59 AM Hasan al-Basri 
> wrote:
>
>> Ok, I'll check it out.
>>
>> Downloading now, then will install right over the top of my existing 2.01
>> Tnx
>> 73, N0AN
>>
>> Hasan
>>
>>
>> On Fri, Jul 5, 2019 at 7:46 AM Black Michael  wrote:
>>
>>> This is version 2.0.1 with dropout debugging.
>>> If the decode light is not flashing then it sounds like you may have
>>> audio dropouts occurring.
>>> This version will show you when it fails with messages in the band
>>> activity window about "dropout".  You'll see a few messages on startup
>>> which is normal as the audio catches up.
>>>
>>>
>>> https://www.dropbox.com/s/isxwjybws1i8u6f/wsjtx-2.0.1-win32-dropouts.exe?dl=1
>>>
>>> de Mike W9MDB
>>>
>>>
>>> On Friday, July 5, 2019, 04:45:38 AM CDT, Hasan al-Basri <
>>> hbasri.schie...@gmail.com> wrote:
>>>
>>>
>>> Ok Mike, it decoded for > 24 hours but then stopped early this morning
>>> just before I got to the shack.
>>>
>>> Started 07/03/2019 @ 1723
>>> Stopped 07/05/2019 @ 0407 Both local
>>>
>>> These are the file saved dates. Again, I had to reboot a few minutes ago
>>> to get it to start saving files/decoding again.
>>>
>>> The rig was unattended from about 6 p.m. last  night until 4:19 a.m.
>>> when I came down to see if it was still decoding...I noticed it had stopped
>>> decoding 12 minutes b4 I got down here.
>>>
>>> Another symptom: When it stops decoding incoming signals, the Blue
>>> Decode light does NOT flash at the end of a sequence, ...even though the
>>> thermometer and the waterfall show sigs for the full sequence.
>>>
>>> Any other suggestions?
>>> 73, N0AN
>>> Hasan
>>>
>>>
>>> On Thu, Jul 4, 2019 at 5:35 AM Hasan al-Basri 
>>> wrote:
>>>
>>> Ok, I'll check it out. Time is perfect and always is, I'm GPS locked to
>>> it.
>>>
>>> When I got down here this morning it was still decoding full fill of
>>> JTAlert. ...but it's only been 12 hours. (I did the remove driver, unplug
>>> it and let Win10 reinstall it at a reboot) . That's where I am now in my
>>> test.)
>>>
>>> Save none was checked, I just checked Save All, will provide if needed.
>>>
>>> Here's hoping...
>>>
>>> 73, N0AN
>>> Hasan
>>>
>>>
>>> On Wed, Jul 3, 2019 at 10:37 PM Black Michael 
>>> wrote:
>>>
>>> We seem to be hearing problems with a few people on both 2.0.1 and
>>> 2.1.0-rc7.
>>> 2.0.1 has been out for a long time and if this was common I'd think we
>>> would have heard a lot more reports of the problem.
>>> Upgrading to 2.1.0-rc7 and back to 2.0.1 should (and I emphasize should)
>>> just revert completely back to 2.0.1 thought there is a bug with FT4 in
>>> that case.
>>>
>>> The common thread probably is Windows updatesor time is off.  Check
>>> http://time.is to ensure you're time is reported as "Exact".
>>>
>>> If you see waterfall activity but no decodes on of three things is
>>> likely happening.
>>>
>>> #1 Time is off
>>> #2 WAV files are not being recorded.  Ensure Save/All is checked and see
>>> if WAV files are showing up in the Save folder.  One user found using
>>> Remote Desktop that audio files weren't being saved.  TeamViewer worked
>>> though.
>>> #3 Audio corrupted.  If WAV files are showing up but not decoding and
>>> your time is correct then send in a few audio files so we can look at them.
>>>
>>> de Mike W9MDB
>>>
>>>
>>>
>>>
>>> On Wednesday, July 3, 2019, 10:27:56 PM CDT, Tod Farrell WE5TR <
>>> we5t...@gmail.com> wrote:
>>>
>>>
>>> Similar issue here on 2.0.1, win10, and flex6700 after a long operating
>>> session or even a long monitoring session. I.e. I’ll leave the shack
>>> powered up monitoring a band while I’m at work or elsewhere in the house.
>>>
>>> When I come back sometimes the waterfall is showing activity, dT is
>>> good, time.is is good, but no decodes.
>>> Other times it’s that clicking transit or tune causes no generated audio
>>> to the DAX  software which has a meter that shows me no incoming audio is
>>> present from WSJT-X.
>>>
>>> Typically corrected with a WSJT-X restart
>>>
>>> --
>>> 73
>>>
>>> TodWE5TR
>>> While mobile
>>>
>>> On Jul 3, 2019, at 16:52, Hasan al-Basri 
>>> wrote:
>>>
>>> Hi Mike,
>>> No transmitting at all. RF Chokes all over the place. No issues running
>>> KW out on any band 6m through 80m. (if I have just rebooted the computer).
>>> Once it has run for several hours. it will stop decoding, whether I have
>>> transmitted or not, no 

Re: [wsjt-devel] WSJT Audio Input Loss

[Roy Gould]

I have had the problem of the Decode button not coming on after the end of
a receive interval. In my case I found the problem to be that the computer
was being overloaded by high CPU usage of a web browser. This occurred with
Edge, Chrome, or Firefox. This high CPU usage was seen by Task Manager. The
solution was to close the web browser.  What does Task Manager reveal in
your case?

On Fri, Jul 5, 2019 at 8:59 AM Hasan al-Basri 
wrote:

> Ok, I'll check it out.
>
> Downloading now, then will install right over the top of my existing 2.01
> Tnx
> 73, N0AN
>
> Hasan
>
>
> On Fri, Jul 5, 2019 at 7:46 AM Black Michael  wrote:
>
>> This is version 2.0.1 with dropout debugging.
>> If the decode light is not flashing then it sounds like you may have
>> audio dropouts occurring.
>> This version will show you when it fails with messages in the band
>> activity window about "dropout".  You'll see a few messages on startup
>> which is normal as the audio catches up.
>>
>>
>> https://www.dropbox.com/s/isxwjybws1i8u6f/wsjtx-2.0.1-win32-dropouts.exe?dl=1
>>
>> de Mike W9MDB
>>
>>
>> On Friday, July 5, 2019, 04:45:38 AM CDT, Hasan al-Basri <
>> hbasri.schie...@gmail.com> wrote:
>>
>>
>> Ok Mike, it decoded for > 24 hours but then stopped early this morning
>> just before I got to the shack.
>>
>> Started 07/03/2019 @ 1723
>> Stopped 07/05/2019 @ 0407 Both local
>>
>> These are the file saved dates. Again, I had to reboot a few minutes ago
>> to get it to start saving files/decoding again.
>>
>> The rig was unattended from about 6 p.m. last  night until 4:19 a.m. when
>> I came down to see if it was still decoding...I noticed it had stopped
>> decoding 12 minutes b4 I got down here.
>>
>> Another symptom: When it stops decoding incoming signals, the Blue Decode
>> light does NOT flash at the end of a sequence, ...even though the
>> thermometer and the waterfall show sigs for the full sequence.
>>
>> Any other suggestions?
>> 73, N0AN
>> Hasan
>>
>>
>> On Thu, Jul 4, 2019 at 5:35 AM Hasan al-Basri 
>> wrote:
>>
>> Ok, I'll check it out. Time is perfect and always is, I'm GPS locked to
>> it.
>>
>> When I got down here this morning it was still decoding full fill of
>> JTAlert. ...but it's only been 12 hours. (I did the remove driver, unplug
>> it and let Win10 reinstall it at a reboot) . That's where I am now in my
>> test.)
>>
>> Save none was checked, I just checked Save All, will provide if needed.
>>
>> Here's hoping...
>>
>> 73, N0AN
>> Hasan
>>
>>
>> On Wed, Jul 3, 2019 at 10:37 PM Black Michael 
>> wrote:
>>
>> We seem to be hearing problems with a few people on both 2.0.1 and
>> 2.1.0-rc7.
>> 2.0.1 has been out for a long time and if this was common I'd think we
>> would have heard a lot more reports of the problem.
>> Upgrading to 2.1.0-rc7 and back to 2.0.1 should (and I emphasize should)
>> just revert completely back to 2.0.1 thought there is a bug with FT4 in
>> that case.
>>
>> The common thread probably is Windows updatesor time is off.  Check
>> http://time.is to ensure you're time is reported as "Exact".
>>
>> If you see waterfall activity but no decodes on of three things is likely
>> happening.
>>
>> #1 Time is off
>> #2 WAV files are not being recorded.  Ensure Save/All is checked and see
>> if WAV files are showing up in the Save folder.  One user found using
>> Remote Desktop that audio files weren't being saved.  TeamViewer worked
>> though.
>> #3 Audio corrupted.  If WAV files are showing up but not decoding and
>> your time is correct then send in a few audio files so we can look at them.
>>
>> de Mike W9MDB
>>
>>
>>
>>
>> On Wednesday, July 3, 2019, 10:27:56 PM CDT, Tod Farrell WE5TR <
>> we5t...@gmail.com> wrote:
>>
>>
>> Similar issue here on 2.0.1, win10, and flex6700 after a long operating
>> session or even a long monitoring session. I.e. I’ll leave the shack
>> powered up monitoring a band while I’m at work or elsewhere in the house.
>>
>> When I come back sometimes the waterfall is showing activity, dT is good,
>> time.is is good, but no decodes.
>> Other times it’s that clicking transit or tune causes no generated audio
>> to the DAX  software which has a meter that shows me no incoming audio is
>> present from WSJT-X.
>>
>> Typically corrected with a WSJT-X restart
>>
>> --
>> 73
>>
>> TodWE5TR
>> While mobile
>>
>> On Jul 3, 2019, at 16:52, Hasan al-Basri 
>> wrote:
>>
>> Hi Mike,
>> No transmitting at all. RF Chokes all over the place. No issues running
>> KW out on any band 6m through 80m. (if I have just rebooted the computer).
>> Once it has run for several hours. it will stop decoding, whether I have
>> transmitted or not, no matter qrp or qro. I monitor 24x7 , go days without
>> tx'ing...it still goes deaf.
>>
>> IOW, it's not a USB RFI problem.
>>
>> All power settings for USB have been set to never sleep.
>>
>> I"m baffled, like I said, it acts like a memory leak and I don't think
>> it's a coincidence that it showed up the very first time after installing
>> and 

Re: [wsjt-devel] WSJT Audio Input Loss

[Hasan al-Basri]

INstalled and running Mike. Will watch for it...when it fails, it stays
failed, so all I have to do is watch the Save directory last decode having
started just now. Probably wont show until tomorrow. It'w working fine now,
but it does for hours before the first freak out.
73, N0AN
Hasan


On Fri, Jul 5, 2019 at 9:53 AM Hasan al-Basri 
wrote:

> Ok, I'll check it out.
>
> Downloading now, then will install right over the top of my existing 2.01
> Tnx
> 73, N0AN
>
> Hasan
>
>
> On Fri, Jul 5, 2019 at 7:46 AM Black Michael  wrote:
>
>> This is version 2.0.1 with dropout debugging.
>> If the decode light is not flashing then it sounds like you may have
>> audio dropouts occurring.
>> This version will show you when it fails with messages in the band
>> activity window about "dropout".  You'll see a few messages on startup
>> which is normal as the audio catches up.
>>
>>
>> https://www.dropbox.com/s/isxwjybws1i8u6f/wsjtx-2.0.1-win32-dropouts.exe?dl=1
>>
>> de Mike W9MDB
>>
>>
>> On Friday, July 5, 2019, 04:45:38 AM CDT, Hasan al-Basri <
>> hbasri.schie...@gmail.com> wrote:
>>
>>
>> Ok Mike, it decoded for > 24 hours but then stopped early this morning
>> just before I got to the shack.
>>
>> Started 07/03/2019 @ 1723
>> Stopped 07/05/2019 @ 0407 Both local
>>
>> These are the file saved dates. Again, I had to reboot a few minutes ago
>> to get it to start saving files/decoding again.
>>
>> The rig was unattended from about 6 p.m. last  night until 4:19 a.m. when
>> I came down to see if it was still decoding...I noticed it had stopped
>> decoding 12 minutes b4 I got down here.
>>
>> Another symptom: When it stops decoding incoming signals, the Blue Decode
>> light does NOT flash at the end of a sequence, ...even though the
>> thermometer and the waterfall show sigs for the full sequence.
>>
>> Any other suggestions?
>> 73, N0AN
>> Hasan
>>
>>
>> On Thu, Jul 4, 2019 at 5:35 AM Hasan al-Basri 
>> wrote:
>>
>> Ok, I'll check it out. Time is perfect and always is, I'm GPS locked to
>> it.
>>
>> When I got down here this morning it was still decoding full fill of
>> JTAlert. ...but it's only been 12 hours. (I did the remove driver, unplug
>> it and let Win10 reinstall it at a reboot) . That's where I am now in my
>> test.)
>>
>> Save none was checked, I just checked Save All, will provide if needed.
>>
>> Here's hoping...
>>
>> 73, N0AN
>> Hasan
>>
>>
>> On Wed, Jul 3, 2019 at 10:37 PM Black Michael 
>> wrote:
>>
>> We seem to be hearing problems with a few people on both 2.0.1 and
>> 2.1.0-rc7.
>> 2.0.1 has been out for a long time and if this was common I'd think we
>> would have heard a lot more reports of the problem.
>> Upgrading to 2.1.0-rc7 and back to 2.0.1 should (and I emphasize should)
>> just revert completely back to 2.0.1 thought there is a bug with FT4 in
>> that case.
>>
>> The common thread probably is Windows updatesor time is off.  Check
>> http://time.is to ensure you're time is reported as "Exact".
>>
>> If you see waterfall activity but no decodes on of three things is likely
>> happening.
>>
>> #1 Time is off
>> #2 WAV files are not being recorded.  Ensure Save/All is checked and see
>> if WAV files are showing up in the Save folder.  One user found using
>> Remote Desktop that audio files weren't being saved.  TeamViewer worked
>> though.
>> #3 Audio corrupted.  If WAV files are showing up but not decoding and
>> your time is correct then send in a few audio files so we can look at them.
>>
>> de Mike W9MDB
>>
>>
>>
>>
>> On Wednesday, July 3, 2019, 10:27:56 PM CDT, Tod Farrell WE5TR <
>> we5t...@gmail.com> wrote:
>>
>>
>> Similar issue here on 2.0.1, win10, and flex6700 after a long operating
>> session or even a long monitoring session. I.e. I’ll leave the shack
>> powered up monitoring a band while I’m at work or elsewhere in the house.
>>
>> When I come back sometimes the waterfall is showing activity, dT is good,
>> time.is is good, but no decodes.
>> Other times it’s that clicking transit or tune causes no generated audio
>> to the DAX  software which has a meter that shows me no incoming audio is
>> present from WSJT-X.
>>
>> Typically corrected with a WSJT-X restart
>>
>> --
>> 73
>>
>> TodWE5TR
>> While mobile
>>
>> On Jul 3, 2019, at 16:52, Hasan al-Basri 
>> wrote:
>>
>> Hi Mike,
>> No transmitting at all. RF Chokes all over the place. No issues running
>> KW out on any band 6m through 80m. (if I have just rebooted the computer).
>> Once it has run for several hours. it will stop decoding, whether I have
>> transmitted or not, no matter qrp or qro. I monitor 24x7 , go days without
>> tx'ing...it still goes deaf.
>>
>> IOW, it's not a USB RFI problem.
>>
>> All power settings for USB have been set to never sleep.
>>
>> I"m baffled, like I said, it acts like a memory leak and I don't think
>> it's a coincidence that it showed up the very first time after installing
>> and running RC7 64 bit.
>>
>> The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change
>> a 

Re: [wsjt-devel] WSJT Audio Input Loss

[Hasan al-Basri]

Ok, I'll check it out.

Downloading now, then will install right over the top of my existing 2.01
Tnx
73, N0AN

Hasan


On Fri, Jul 5, 2019 at 7:46 AM Black Michael  wrote:

> This is version 2.0.1 with dropout debugging.
> If the decode light is not flashing then it sounds like you may have audio
> dropouts occurring.
> This version will show you when it fails with messages in the band
> activity window about "dropout".  You'll see a few messages on startup
> which is normal as the audio catches up.
>
>
> https://www.dropbox.com/s/isxwjybws1i8u6f/wsjtx-2.0.1-win32-dropouts.exe?dl=1
>
> de Mike W9MDB
>
>
> On Friday, July 5, 2019, 04:45:38 AM CDT, Hasan al-Basri <
> hbasri.schie...@gmail.com> wrote:
>
>
> Ok Mike, it decoded for > 24 hours but then stopped early this morning
> just before I got to the shack.
>
> Started 07/03/2019 @ 1723
> Stopped 07/05/2019 @ 0407 Both local
>
> These are the file saved dates. Again, I had to reboot a few minutes ago
> to get it to start saving files/decoding again.
>
> The rig was unattended from about 6 p.m. last  night until 4:19 a.m. when
> I came down to see if it was still decoding...I noticed it had stopped
> decoding 12 minutes b4 I got down here.
>
> Another symptom: When it stops decoding incoming signals, the Blue Decode
> light does NOT flash at the end of a sequence, ...even though the
> thermometer and the waterfall show sigs for the full sequence.
>
> Any other suggestions?
> 73, N0AN
> Hasan
>
>
> On Thu, Jul 4, 2019 at 5:35 AM Hasan al-Basri 
> wrote:
>
> Ok, I'll check it out. Time is perfect and always is, I'm GPS locked to it.
>
> When I got down here this morning it was still decoding full fill of
> JTAlert. ...but it's only been 12 hours. (I did the remove driver, unplug
> it and let Win10 reinstall it at a reboot) . That's where I am now in my
> test.)
>
> Save none was checked, I just checked Save All, will provide if needed.
>
> Here's hoping...
>
> 73, N0AN
> Hasan
>
>
> On Wed, Jul 3, 2019 at 10:37 PM Black Michael  wrote:
>
> We seem to be hearing problems with a few people on both 2.0.1 and
> 2.1.0-rc7.
> 2.0.1 has been out for a long time and if this was common I'd think we
> would have heard a lot more reports of the problem.
> Upgrading to 2.1.0-rc7 and back to 2.0.1 should (and I emphasize should)
> just revert completely back to 2.0.1 thought there is a bug with FT4 in
> that case.
>
> The common thread probably is Windows updatesor time is off.  Check
> http://time.is to ensure you're time is reported as "Exact".
>
> If you see waterfall activity but no decodes on of three things is likely
> happening.
>
> #1 Time is off
> #2 WAV files are not being recorded.  Ensure Save/All is checked and see
> if WAV files are showing up in the Save folder.  One user found using
> Remote Desktop that audio files weren't being saved.  TeamViewer worked
> though.
> #3 Audio corrupted.  If WAV files are showing up but not decoding and your
> time is correct then send in a few audio files so we can look at them.
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, July 3, 2019, 10:27:56 PM CDT, Tod Farrell WE5TR <
> we5t...@gmail.com> wrote:
>
>
> Similar issue here on 2.0.1, win10, and flex6700 after a long operating
> session or even a long monitoring session. I.e. I’ll leave the shack
> powered up monitoring a band while I’m at work or elsewhere in the house.
>
> When I come back sometimes the waterfall is showing activity, dT is good,
> time.is is good, but no decodes.
> Other times it’s that clicking transit or tune causes no generated audio
> to the DAX  software which has a meter that shows me no incoming audio is
> present from WSJT-X.
>
> Typically corrected with a WSJT-X restart
>
> --
> 73
>
> TodWE5TR
> While mobile
>
> On Jul 3, 2019, at 16:52, Hasan al-Basri 
> wrote:
>
> Hi Mike,
> No transmitting at all. RF Chokes all over the place. No issues running KW
> out on any band 6m through 80m. (if I have just rebooted the computer).
> Once it has run for several hours. it will stop decoding, whether I have
> transmitted or not, no matter qrp or qro. I monitor 24x7 , go days without
> tx'ing...it still goes deaf.
>
> IOW, it's not a USB RFI problem.
>
> All power settings for USB have been set to never sleep.
>
> I"m baffled, like I said, it acts like a memory leak and I don't think
> it's a coincidence that it showed up the very first time after installing
> and running RC7 64 bit.
>
> The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change a
> thing in my setup or operating habits. Now I have to reboot every day or it
> just stops decoding, even having uninstalled RC7 64 bit and returned to
> 2.01 Gen Release.
>
> Audio level is perfect, waterfall shows signals...no decode.
> Reboot...decodes resume. No other program shows any symptoms like this at
> all on the same computer. WSJT-X is running on its own USB Sound Dongle for
> both RX and TXand has been for over a year.
>
> Any further ideas are most welcome (TS-590sg, 

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

This is version 2.0.1 with dropout debugging.If the decode light is not 
flashing then it sounds like you may have audio dropouts occurring.This version 
will show you when it fails with messages in the band activity window about 
"dropout".  You'll see a few messages on startup which is normal as the audio 
catches up.
https://www.dropbox.com/s/isxwjybws1i8u6f/wsjtx-2.0.1-win32-dropouts.exe?dl=1

de Mike W9MDB 

On Friday, July 5, 2019, 04:45:38 AM CDT, Hasan al-Basri 
 wrote:  
 
 Ok Mike, it decoded for > 24 hours but then stopped early this morning just 
before I got to the shack. 
Started 07/03/2019 @ 1723Stopped 07/05/2019 @ 0407 Both local
These are the file saved dates. Again, I had to reboot a few minutes ago to get 
it to start saving files/decoding again.
The rig was unattended from about 6 p.m. last  night until 4:19 a.m. when I 
came down to see if it was still decoding...I noticed it had stopped decoding 
12 minutes b4 I got down here.
Another symptom: When it stops decoding incoming signals, the Blue Decode light 
does NOT flash at the end of a sequence, ...even though the thermometer and the 
waterfall show sigs for the full sequence.
Any other suggestions?73, N0ANHasan

On Thu, Jul 4, 2019 at 5:35 AM Hasan al-Basri  wrote:

Ok, I'll check it out. Time is perfect and always is, I'm GPS locked to it.

When I got down here this morning it was still decoding full fill of JTAlert. 
...but it's only been 12 hours. (I did the remove driver, unplug it and let 
Win10 reinstall it at a reboot) . That's where I am now in my test.) 
Save none was checked, I just checked Save All, will provide if needed.
Here's hoping...
73, N0ANHasan

On Wed, Jul 3, 2019 at 10:37 PM Black Michael  wrote:

We seem to be hearing problems with a few people on both 2.0.1 and 2.1.0-rc7.  
2.0.1 has been out for a long time and if this was common I'd think we would 
have heard a lot more reports of the problem.Upgrading to 2.1.0-rc7 and back to 
2.0.1 should (and I emphasize should) just revert completely back to 2.0.1 
thought there is a bug with FT4 in that case.
The common thread probably is Windows updatesor time is off.  Check 
http://time.is to ensure you're time is reported as "Exact".
If you see waterfall activity but no decodes on of three things is likely 
happening.
#1 Time is off#2 WAV files are not being recorded.  Ensure Save/All is checked 
and see if WAV files are showing up in the Save folder.  One user found using 
Remote Desktop that audio files weren't being saved.  TeamViewer worked 
though.#3 Audio corrupted.  If WAV files are showing up but not decoding and 
your time is correct then send in a few audio files so we can look at them.

de Mike W9MDB

 

On Wednesday, July 3, 2019, 10:27:56 PM CDT, Tod Farrell WE5TR 
 wrote:  
 
 Similar issue here on 2.0.1, win10, and flex6700 after a long operating 
session or even a long monitoring session. I.e. I’ll leave the shack powered up 
monitoring a band while I’m at work or elsewhere in the house. 
When I come back sometimes the waterfall is showing activity, dT is good, 
time.is is good, but no decodes.Other times it’s that clicking transit or tune 
causes no generated audio to the DAX  software which has a meter that shows me 
no incoming audio is present from WSJT-X.
Typically corrected with a WSJT-X restart 
--73
Tod    WE5TRWhile mobile
On Jul 3, 2019, at 16:52, Hasan al-Basri  wrote:


Hi Mike,No transmitting at all. RF Chokes all over the place. No issues running 
KW out on any band 6m through 80m. (if I have just rebooted the computer). Once 
it has run for several hours. it will stop decoding, whether I have transmitted 
or not, no matter qrp or qro. I monitor 24x7 , go days without tx'ing...it 
still goes deaf.
IOW, it's not a USB RFI problem. 
All power settings for USB have been set to never sleep. 
I"m baffled, like I said, it acts like a memory leak and I don't think it's a 
coincidence that it showed up the very first time after installing and running 
RC7 64 bit. 
The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change a 
thing in my setup or operating habits. Now I have to reboot every day or it 
just stops decoding, even having uninstalled RC7 64 bit and returned to 2.01 
Gen Release.
Audio level is perfect, waterfall shows signals...no decode. Reboot...decodes 
resume. No other program shows any symptoms like this at all on the same 
computer. WSJT-X is running on its own USB Sound Dongle for both RX and 
TXand has been for over a year. Any further ideas are most welcome 
(TS-590sg, running from headphone jack for rx audio) Audio sounds perfect to 
the ear. Levels are right...Most peculiar!
73, N0ANHasan

On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel 
 wrote:

Failing audio or rig connections are most always due to RFI or USB ports going 
to sleep.If RFI low power transmissions can be tested and if they work but high 
power does not then it's RFI.The USB ports going to sleep can be 

Re: [wsjt-devel] WSJT Audio Input Loss

[Hasan al-Basri]

Ok Mike, it decoded for > 24 hours but then stopped early this morning just
before I got to the shack.

Started 07/03/2019 @ 1723
Stopped 07/05/2019 @ 0407 Both local

These are the file saved dates. Again, I had to reboot a few minutes ago to
get it to start saving files/decoding again.

The rig was unattended from about 6 p.m. last  night until 4:19 a.m. when I
came down to see if it was still decoding...I noticed it had stopped
decoding 12 minutes b4 I got down here.

Another symptom: When it stops decoding incoming signals, the Blue Decode
light does NOT flash at the end of a sequence, ...even though the
thermometer and the waterfall show sigs for the full sequence.

Any other suggestions?
73, N0AN
Hasan


On Thu, Jul 4, 2019 at 5:35 AM Hasan al-Basri 
wrote:

> Ok, I'll check it out. Time is perfect and always is, I'm GPS locked to it.
>
> When I got down here this morning it was still decoding full fill of
> JTAlert. ...but it's only been 12 hours. (I did the remove driver, unplug
> it and let Win10 reinstall it at a reboot) . That's where I am now in my
> test.)
>
> Save none was checked, I just checked Save All, will provide if needed.
>
> Here's hoping...
>
> 73, N0AN
> Hasan
>
>
> On Wed, Jul 3, 2019 at 10:37 PM Black Michael  wrote:
>
>> We seem to be hearing problems with a few people on both 2.0.1 and
>> 2.1.0-rc7.
>> 2.0.1 has been out for a long time and if this was common I'd think we
>> would have heard a lot more reports of the problem.
>> Upgrading to 2.1.0-rc7 and back to 2.0.1 should (and I emphasize should)
>> just revert completely back to 2.0.1 thought there is a bug with FT4 in
>> that case.
>>
>> The common thread probably is Windows updatesor time is off.  Check
>> http://time.is to ensure you're time is reported as "Exact".
>>
>> If you see waterfall activity but no decodes on of three things is likely
>> happening.
>>
>> #1 Time is off
>> #2 WAV files are not being recorded.  Ensure Save/All is checked and see
>> if WAV files are showing up in the Save folder.  One user found using
>> Remote Desktop that audio files weren't being saved.  TeamViewer worked
>> though.
>> #3 Audio corrupted.  If WAV files are showing up but not decoding and
>> your time is correct then send in a few audio files so we can look at them.
>>
>> de Mike W9MDB
>>
>>
>>
>>
>> On Wednesday, July 3, 2019, 10:27:56 PM CDT, Tod Farrell WE5TR <
>> we5t...@gmail.com> wrote:
>>
>>
>> Similar issue here on 2.0.1, win10, and flex6700 after a long operating
>> session or even a long monitoring session. I.e. I’ll leave the shack
>> powered up monitoring a band while I’m at work or elsewhere in the house.
>>
>> When I come back sometimes the waterfall is showing activity, dT is good,
>> time.is is good, but no decodes.
>> Other times it’s that clicking transit or tune causes no generated audio
>> to the DAX  software which has a meter that shows me no incoming audio is
>> present from WSJT-X.
>>
>> Typically corrected with a WSJT-X restart
>>
>> --
>> 73
>>
>> TodWE5TR
>> While mobile
>>
>> On Jul 3, 2019, at 16:52, Hasan al-Basri 
>> wrote:
>>
>> Hi Mike,
>> No transmitting at all. RF Chokes all over the place. No issues running
>> KW out on any band 6m through 80m. (if I have just rebooted the computer).
>> Once it has run for several hours. it will stop decoding, whether I have
>> transmitted or not, no matter qrp or qro. I monitor 24x7 , go days without
>> tx'ing...it still goes deaf.
>>
>> IOW, it's not a USB RFI problem.
>>
>> All power settings for USB have been set to never sleep.
>>
>> I"m baffled, like I said, it acts like a memory leak and I don't think
>> it's a coincidence that it showed up the very first time after installing
>> and running RC7 64 bit.
>>
>> The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change
>> a thing in my setup or operating habits. Now I have to reboot every day or
>> it just stops decoding, even having uninstalled RC7 64 bit and returned to
>> 2.01 Gen Release.
>>
>> Audio level is perfect, waterfall shows signals...no decode.
>> Reboot...decodes resume. No other program shows any symptoms like this at
>> all on the same computer. WSJT-X is running on its own USB Sound Dongle for
>> both RX and TXand has been for over a year.
>>
>> Any further ideas are most welcome (TS-590sg, running from headphone jack
>> for rx audio) Audio sounds perfect to the ear. Levels are right...
>> Most peculiar!
>>
>> 73, N0AN
>> Hasan
>>
>>
>> On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel <
>> wsjt-devel@lists.sourceforge.net> wrote:
>>
>> Failing audio or rig connections are most always due to RFI or USB ports
>> going to sleep.
>> If RFI low power transmissions can be tested and if they work but high
>> power does not then it's RFI.
>> The USB ports going to sleep can be solved.
>> https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices
>>
>> de Mike W9MDB
>>
>>
>>
>>
>> On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com <

Re: [wsjt-devel] WSJT Audio Input Loss

[Hasan al-Basri]

Ok, I'll check it out. Time is perfect and always is, I'm GPS locked to it.

When I got down here this morning it was still decoding full fill of
JTAlert. ...but it's only been 12 hours. (I did the remove driver, unplug
it and let Win10 reinstall it at a reboot) . That's where I am now in my
test.)

Save none was checked, I just checked Save All, will provide if needed.

Here's hoping...

73, N0AN
Hasan


On Wed, Jul 3, 2019 at 10:37 PM Black Michael  wrote:

> We seem to be hearing problems with a few people on both 2.0.1 and
> 2.1.0-rc7.
> 2.0.1 has been out for a long time and if this was common I'd think we
> would have heard a lot more reports of the problem.
> Upgrading to 2.1.0-rc7 and back to 2.0.1 should (and I emphasize should)
> just revert completely back to 2.0.1 thought there is a bug with FT4 in
> that case.
>
> The common thread probably is Windows updatesor time is off.  Check
> http://time.is to ensure you're time is reported as "Exact".
>
> If you see waterfall activity but no decodes on of three things is likely
> happening.
>
> #1 Time is off
> #2 WAV files are not being recorded.  Ensure Save/All is checked and see
> if WAV files are showing up in the Save folder.  One user found using
> Remote Desktop that audio files weren't being saved.  TeamViewer worked
> though.
> #3 Audio corrupted.  If WAV files are showing up but not decoding and your
> time is correct then send in a few audio files so we can look at them.
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, July 3, 2019, 10:27:56 PM CDT, Tod Farrell WE5TR <
> we5t...@gmail.com> wrote:
>
>
> Similar issue here on 2.0.1, win10, and flex6700 after a long operating
> session or even a long monitoring session. I.e. I’ll leave the shack
> powered up monitoring a band while I’m at work or elsewhere in the house.
>
> When I come back sometimes the waterfall is showing activity, dT is good,
> time.is is good, but no decodes.
> Other times it’s that clicking transit or tune causes no generated audio
> to the DAX  software which has a meter that shows me no incoming audio is
> present from WSJT-X.
>
> Typically corrected with a WSJT-X restart
>
> --
> 73
>
> TodWE5TR
> While mobile
>
> On Jul 3, 2019, at 16:52, Hasan al-Basri 
> wrote:
>
> Hi Mike,
> No transmitting at all. RF Chokes all over the place. No issues running KW
> out on any band 6m through 80m. (if I have just rebooted the computer).
> Once it has run for several hours. it will stop decoding, whether I have
> transmitted or not, no matter qrp or qro. I monitor 24x7 , go days without
> tx'ing...it still goes deaf.
>
> IOW, it's not a USB RFI problem.
>
> All power settings for USB have been set to never sleep.
>
> I"m baffled, like I said, it acts like a memory leak and I don't think
> it's a coincidence that it showed up the very first time after installing
> and running RC7 64 bit.
>
> The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change a
> thing in my setup or operating habits. Now I have to reboot every day or it
> just stops decoding, even having uninstalled RC7 64 bit and returned to
> 2.01 Gen Release.
>
> Audio level is perfect, waterfall shows signals...no decode.
> Reboot...decodes resume. No other program shows any symptoms like this at
> all on the same computer. WSJT-X is running on its own USB Sound Dongle for
> both RX and TXand has been for over a year.
>
> Any further ideas are most welcome (TS-590sg, running from headphone jack
> for rx audio) Audio sounds perfect to the ear. Levels are right...
> Most peculiar!
>
> 73, N0AN
> Hasan
>
>
> On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Failing audio or rig connections are most always due to RFI or USB ports
> going to sleep.
> If RFI low power transmissions can be tested and if they work but high
> power does not then it's RFI.
> The USB ports going to sleep can be solved.
> https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com <
> rjai...@gmail.com> wrote:
>
>
> I’ve seen this with other radios. Definitely not a flex only issue.
>
> Ria
> N2RJ
>
> On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Peter,
>
> Flex has its own set of unique problems and fixes.  Suggest you post your
> question on the Flex forum page.  Good luck.
>
> Danny
> AH6FX/W4
>
> On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam 
> wrote:
>
>
> 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 

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

We seem to be hearing problems with a few people on both 2.0.1 and 2.1.0-rc7.  
2.0.1 has been out for a long time and if this was common I'd think we would 
have heard a lot more reports of the problem.Upgrading to 2.1.0-rc7 and back to 
2.0.1 should (and I emphasize should) just revert completely back to 2.0.1 
thought there is a bug with FT4 in that case.
The common thread probably is Windows updatesor time is off.  Check 
http://time.is to ensure you're time is reported as "Exact".
If you see waterfall activity but no decodes on of three things is likely 
happening.
#1 Time is off#2 WAV files are not being recorded.  Ensure Save/All is checked 
and see if WAV files are showing up in the Save folder.  One user found using 
Remote Desktop that audio files weren't being saved.  TeamViewer worked 
though.#3 Audio corrupted.  If WAV files are showing up but not decoding and 
your time is correct then send in a few audio files so we can look at them.

de Mike W9MDB

 

On Wednesday, July 3, 2019, 10:27:56 PM CDT, Tod Farrell WE5TR 
 wrote:  
 
 Similar issue here on 2.0.1, win10, and flex6700 after a long operating 
session or even a long monitoring session. I.e. I’ll leave the shack powered up 
monitoring a band while I’m at work or elsewhere in the house. 
When I come back sometimes the waterfall is showing activity, dT is good, 
time.is is good, but no decodes.Other times it’s that clicking transit or tune 
causes no generated audio to the DAX  software which has a meter that shows me 
no incoming audio is present from WSJT-X.
Typically corrected with a WSJT-X restart 
--73
Tod    WE5TRWhile mobile
On Jul 3, 2019, at 16:52, Hasan al-Basri  wrote:


Hi Mike,No transmitting at all. RF Chokes all over the place. No issues running 
KW out on any band 6m through 80m. (if I have just rebooted the computer). Once 
it has run for several hours. it will stop decoding, whether I have transmitted 
or not, no matter qrp or qro. I monitor 24x7 , go days without tx'ing...it 
still goes deaf.
IOW, it's not a USB RFI problem. 
All power settings for USB have been set to never sleep. 
I"m baffled, like I said, it acts like a memory leak and I don't think it's a 
coincidence that it showed up the very first time after installing and running 
RC7 64 bit. 
The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change a 
thing in my setup or operating habits. Now I have to reboot every day or it 
just stops decoding, even having uninstalled RC7 64 bit and returned to 2.01 
Gen Release.
Audio level is perfect, waterfall shows signals...no decode. Reboot...decodes 
resume. No other program shows any symptoms like this at all on the same 
computer. WSJT-X is running on its own USB Sound Dongle for both RX and 
TXand has been for over a year. Any further ideas are most welcome 
(TS-590sg, running from headphone jack for rx audio) Audio sounds perfect to 
the ear. Levels are right...Most peculiar!
73, N0ANHasan

On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel 
 wrote:

Failing audio or rig connections are most always due to RFI or USB ports going 
to sleep.If RFI low power transmissions can be tested and if they work but high 
power does not then it's RFI.The USB ports going to sleep can be 
solved.https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices

de Mike W9MDB

 

On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
 wrote:  
 
 I’ve seen this with other radios. Definitely not a flex only issue.
RiaN2RJ
On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel 
 wrote:

 Peter,
Flex has its own set of unique problems and fixes.  Suggest you post your 
question on the Flex forum page.  Good luck.

    Danny    AH6FX/W4

On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam  
wrote:  
 
 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 

Re: [wsjt-devel] WSJT Audio Input Loss

[Bill Richter]

You should be able to check the memory usage via Task Manager to determine 
whether or not it is a memory leak...



--
Thanks,
Bill

> On July 3, 2019 at 2:52 PM Hasan al-Basri  wrote:
> 
> 
> I"m baffled, like I said, it acts like a memory leak and I don't think 
> it's a coincidence that it showed up the very first time after installing and 
> running RC7 64 bit. 
> 
> 
> 73, N0AN
> Hasan
> 
> 
> On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel < 
> wsjt-devel@lists.sourceforge.net mailto:wsjt-devel@lists.sourceforge.net > 
> wrote:
> 
> > > Failing audio or rig connections are most always due to 
> RFI or USB ports going to sleep.
> > If RFI low power transmissions can be tested and if they work but 
> > high power does not then it's RFI.
> > The USB ports going to sleep can be solved.
> > 
> > https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices
> > 
> > de Mike W9MDB
> > 
> > 
> > 
> > 
> > On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
> > mailto:rjai...@gmail.com < rjai...@gmail.com mailto:rjai...@gmail.com > 
> > wrote:
> > 
> > 
> > I’ve seen this with other radios. Definitely not a flex only issue.
> > 
> > Ria
> > N2RJ
> > 
> > On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel < 
> > wsjt-devel@lists.sourceforge.net mailto:wsjt-devel@lists.sourceforge.net > 
> > wrote:
> > 
> > > > >  
> > > Peter,
> > > 
> > > Flex has its own set of unique problems and fixes.  Suggest 
> > > you post your question on the Flex forum page.  Good luck.
> > > 
> > > Danny
> > > AH6FX/W4
> > > 
> > > On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam < 
> > > pe...@ni6e.com mailto:pe...@ni6e.com > wrote:
> > > 
> > > 
> > > 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
> > > wsjt-devel@lists.sourceforge.net 
> > > mailto:wsjt-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> > > ___
> > > wsjt-devel mailing list
> > > wsjt-devel@lists.sourceforge.net 
> > > mailto:wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] WSJT Audio Input Loss

[Gary McDuffie]

> On Jul 3, 2019, at 15:52, Hasan al-Basri  wrote:
> 
> Any further ideas are most welcome (TS-590sg, running from headphone jack for 
> rx audio) Audio sounds perfect to the ear. Levels are right...
> Most peculiar!

Hasan - 

As you probably remember, when you uninstall and reinstall, the old user folder 
isn’t cleaned out.  If you haven’t done it, try uninstalling and then go rename 
the entire installation folder in your user folder.  Then reinstall in a new 
folder using the 32 bit version of rc7 and test it.  Hopefully, that will tell 
the story about whether it comes from the 64 bit rc7.

Of course, I didn’t have that problem, but I wasn’t all that impressed with rc7 
anyway, so I only had it up a few times to test JT4.  I haven’t brought it up 
again since shortly after it was put out there for testing.

Gary - AG0N

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

If a restart of WSJT-X does not recover than it sounds like your USB sound 
device is locking up.If that's true just unplugging it and plugging it back in 
would recover the audio (with a restart of WSJT-X too of course).
You may want to uninstall an reinstall your USB sound card.  WIndows updates 
for USB are know to mess things up.
Mike

P.S.According to my notes the transmit side of the 590SG needs this:
Menu 71 = 1Menu 72 = 2
Windows playback audio -20 to -25 dB with the ALC meter on the just bouncing a 
bit.
 

On Wednesday, July 3, 2019, 04:52:13 PM CDT, Hasan al-Basri 
 wrote:  
 
 Hi Mike,No transmitting at all. RF Chokes all over the place. No issues 
running KW out on any band 6m through 80m. (if I have just rebooted the 
computer). Once it has run for several hours. it will stop decoding, whether I 
have transmitted or not, no matter qrp or qro. I monitor 24x7 , go days without 
tx'ing...it still goes deaf.
IOW, it's not a USB RFI problem. 
All power settings for USB have been set to never sleep. 
I"m baffled, like I said, it acts like a memory leak and I don't think it's a 
coincidence that it showed up the very first time after installing and running 
RC7 64 bit. 
The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change a 
thing in my setup or operating habits. Now I have to reboot every day or it 
just stops decoding, even having uninstalled RC7 64 bit and returned to 2.01 
Gen Release.
Audio level is perfect, waterfall shows signals...no decode. Reboot...decodes 
resume. No other program shows any symptoms like this at all on the same 
computer. WSJT-X is running on its own USB Sound Dongle for both RX and 
TXand has been for over a year. Any further ideas are most welcome 
(TS-590sg, running from headphone jack for rx audio) Audio sounds perfect to 
the ear. Levels are right...Most peculiar!
73, N0ANHasan

On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel 
 wrote:

Failing audio or rig connections are most always due to RFI or USB ports going 
to sleep.If RFI low power transmissions can be tested and if they work but high 
power does not then it's RFI.The USB ports going to sleep can be 
solved.https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices

de Mike W9MDB

 

On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
 wrote:  
 
 I’ve seen this with other radios. Definitely not a flex only issue.
RiaN2RJ
On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel 
 wrote:

 Peter,
Flex has its own set of unique problems and fixes.  Suggest you post your 
question on the Flex forum page.  Good luck.

    Danny    AH6FX/W4

On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam  
wrote:  
 
 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
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

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] WSJT Audio Input Loss

[Bill Frantz]

On 7/3/19 at 2:52 PM, hbasri.schie...@gmail.com (Hasan al-Basri) wrote:


I"m baffled, like I said, it acts like a memory leak and I don't think it's
a coincidence that it showed up the very first time after installing and
running RC7 64 bit.


I don't know if this is relevant, but a while ago I got a 
warning from MacOS 10.14.5 that I was almost out of application 
memory and should quit some applications. I closed a bunch of 
tabs in Firefox, quit everything that I wasn't using (including 
wsjt-x) and didn't get the warning again.


I will note that wsjt-x needs to have the shared memory 
increased as part of the Macintosh install.


73 Bill AE6JV

---
Bill Frantz| Truth and love must prevail  | Periwinkle
(408)356-8506  | over lies and hate.  | 16345 
Englewood Ave
www.pwpconsult.com |   - Vaclav Havel | Los Gatos, 
CA 95032




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Hasan al-Basri]

I also followed the link from Mike and verified that I had already done
what he recommended...months and months ago.
It's not an RFI problem.

I've thought about uninstalling X and then going into the registry and
searching for anything related to WSJT-X and deleting it, along with any
left-over files like *.ini, etc

...but, that's a pretty drastic step for something that might be cured by
the general release or finding and replacing a corrupt file. I just don't
know what to find and what to replace   :-)

73, N0AN

Hasan


On Wed, Jul 3, 2019 at 4:53 PM Peter Putnam  wrote:

> No USB ports are involved in a Flex -> DAX -> WSJT setup. Audio is passed
> from one program to another in memory.
>
> One would not suspect RFI to be the culprit after three hours of steady
> operation at full power without an issue.
>
>
>
> On 7/3/2019 2:36 PM, Black Michael via wsjt-devel wrote:
>
> Failing audio or rig connections are most always due to RFI or USB ports
> going to sleep.
> If RFI low power transmissions can be tested and if they work but high
> power does not then it's RFI.
> The USB ports going to sleep can be solved.
> https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com
>   wrote:
>
>
> I’ve seen this with other radios. Definitely not a flex only issue.
>
> Ria
> N2RJ
>
> On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Peter,
>
> Flex has its own set of unique problems and fixes.  Suggest you post your
> question on the Flex forum page.  Good luck.
>
> Danny
> AH6FX/W4
>
> On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam 
> wrote:
>
>
> 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
> 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
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> 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] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

You're correct in that Flex is different in that respect.
I've heard of problems with the audio chain dropping out on Flex before.  Don't 
recall is there was a solution though.
I wonder if the ethernet might have gone to sleep and it burped on that?
de Mike W9MDB

 

On Wednesday, July 3, 2019, 04:50:27 PM CDT, Peter Putnam  
wrote:  
 
  No USB ports are involved in a Flex -> DAX -> WSJT setup. Audio is passed 
from one program to another in memory.
 
 One would not suspect RFI to be the culprit after three hours of steady 
operation at full power without an issue.
 
 
 
 On 7/3/2019 2:36 PM, Black Michael via wsjt-devel wrote:
  
 
  Failing audio or rig connections are most always due to RFI or USB ports 
going to sleep. If RFI low power transmissions can be tested and if they work 
but high power does not then it's RFI. The USB ports going to sleep can be 
solved. 
https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices
  
  de Mike W9MDB 
   

  
  On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
 wrote:  
  
  I’ve seen this with other radios. Definitely not a flex only issue.  
  Ria N2RJ 
   On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel 
 wrote:
  
   Peter, 
  Flex has its own set of unique problems and fixes.  Suggest you post your 
question on the Flex forum page.  Good luck.
  
      Danny     AH6FX/W4
  
On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam 
 wrote:  
  
   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
  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
 
  ___
 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
 
 ___
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] WSJT Audio Input Loss

[Hasan al-Basri]

Hi Mike,
No transmitting at all. RF Chokes all over the place. No issues running KW
out on any band 6m through 80m. (if I have just rebooted the computer).
Once it has run for several hours. it will stop decoding, whether I have
transmitted or not, no matter qrp or qro. I monitor 24x7 , go days without
tx'ing...it still goes deaf.

IOW, it's not a USB RFI problem.

All power settings for USB have been set to never sleep.

I"m baffled, like I said, it acts like a memory leak and I don't think it's
a coincidence that it showed up the very first time after installing and
running RC7 64 bit.

The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change a
thing in my setup or operating habits. Now I have to reboot every day or it
just stops decoding, even having uninstalled RC7 64 bit and returned to
2.01 Gen Release.

Audio level is perfect, waterfall shows signals...no decode.
Reboot...decodes resume. No other program shows any symptoms like this at
all on the same computer. WSJT-X is running on its own USB Sound Dongle for
both RX and TXand has been for over a year.

Any further ideas are most welcome (TS-590sg, running from headphone jack
for rx audio) Audio sounds perfect to the ear. Levels are right...
Most peculiar!

73, N0AN
Hasan


On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Failing audio or rig connections are most always due to RFI or USB ports
> going to sleep.
> If RFI low power transmissions can be tested and if they work but high
> power does not then it's RFI.
> The USB ports going to sleep can be solved.
> https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com <
> rjai...@gmail.com> wrote:
>
>
> I’ve seen this with other radios. Definitely not a flex only issue.
>
> Ria
> N2RJ
>
> On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Peter,
>
> Flex has its own set of unique problems and fixes.  Suggest you post your
> question on the Flex forum page.  Good luck.
>
> Danny
> AH6FX/W4
>
> On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam 
> wrote:
>
>
> 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
> 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
>
> ___
> 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
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Peter Putnam]

No USB ports are involved in a Flex -> DAX -> WSJT setup. Audio is 
passed from one program to another in memory.


One would not suspect RFI to be the culprit after three hours of steady 
operation at full power without an issue.




On 7/3/2019 2:36 PM, Black Michael via wsjt-devel wrote:
Failing audio or rig connections are most always due to RFI or USB 
ports going to sleep.
If RFI low power transmissions can be tested and if they work but high 
power does not then it's RFI.

The USB ports going to sleep can be solved.
https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices

de Mike W9MDB




On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
 wrote:



I’ve seen this with other radios. Definitely not a flex only issue.

Ria
N2RJ

On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel 
> wrote:


Peter,

Flex has its own set of unique problems and fixes.  Suggest you
post your question on the Flex forum page.  Good luck.

    Danny
    AH6FX/W4

On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam
mailto:pe...@ni6e.com>> wrote:


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
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

___
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


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

Failing audio or rig connections are most always due to RFI or USB ports going 
to sleep.If RFI low power transmissions can be tested and if they work but high 
power does not then it's RFI.The USB ports going to sleep can be 
solved.https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices

de Mike W9MDB

 

On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
 wrote:  
 
 I’ve seen this with other radios. Definitely not a flex only issue.
RiaN2RJ
On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel 
 wrote:

 Peter,
Flex has its own set of unique problems and fixes.  Suggest you post your 
question on the Flex forum page.  Good luck.

    Danny    AH6FX/W4

On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam  
wrote:  
 
 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
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

___
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] WSJT Audio Input Loss

[rjai...@gmail.com]

I’ve seen this with other radios. Definitely not a flex only issue.

Ria
N2RJ

On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Peter,
>
> Flex has its own set of unique problems and fixes.  Suggest you post your
> question on the Flex forum page.  Good luck.
>
> Danny
> AH6FX/W4
>
> On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam 
> wrote:
>
>
> 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
> 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
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[DX Jami via wsjt-devel]

 Peter,
Flex has its own set of unique problems and fixes.  Suggest you post your 
question on the Flex forum page.  Good luck.

    Danny    AH6FX/W4

On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam  
wrote:  
 
 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
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