Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

[Hasan al-Basri]

Laurie,

How about this then:

taskkill /IM /T jtalert.exe

That is supposed to not forcefully terminate but issue a WM_CLOSE followed
by telling any Child Process started by the JTA program to also close.

Is that safe? Or what is the proper command line to tell JTALERT.EXE to
close "properly" ?

Once I have that, I can put it in the batch file and JTA will close
gracefully and it can be restarted a few minutes later.

Hasan


On Tue, Jul 30, 2019 at 4:41 PM Hasan al-Basri 
wrote:

> Ok, I'll look at another way to close it.
> Tnx tip, 73, N0AN
> Hasan
>
>
> On Tue, Jul 30, 2019 at 3:53 PM Laurie, VK3AMA <_vk3a...@vkdxer.net>
> wrote:
>
>>
>> On 31/07/2019 2:03 am, Hasan al-Basri wrote:
>>
>> Put this in a batch file: (use notepad to create)
>>
>> taskkill /F /IM jtalert.exe
>>
>>
>> NO, don't do this!
>>
>> Force killing the JTAlert process, rather than a managed shutdown, *doesn't
>> close any of the JTAlert plugin processes or the Decodes History process*,
>> they are all still left running becoming zombie processes.
>>
>> Force killing JTAlert significantly increases the risk of corruption of
>> the config.sqlite database file and the decodes database.
>>
>> de Laurie VK3AMA
>>
>> ___
>> 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] Loss of Decoding in WSJT-X with Audio Still Present

[Hasan al-Basri]

Ok, I'll look at another way to close it.
Tnx tip, 73, N0AN
Hasan


On Tue, Jul 30, 2019 at 3:53 PM Laurie, VK3AMA <_vk3a...@vkdxer.net> wrote:

>
> On 31/07/2019 2:03 am, Hasan al-Basri wrote:
>
> Put this in a batch file: (use notepad to create)
>
> taskkill /F /IM jtalert.exe
>
>
> NO, don't do this!
>
> Force killing the JTAlert process, rather than a managed shutdown, *doesn't
> close any of the JTAlert plugin processes or the Decodes History process*,
> they are all still left running becoming zombie processes.
>
> Force killing JTAlert significantly increases the risk of corruption of
> the config.sqlite database file and the decodes database.
>
> de Laurie VK3AMA
>
> ___
> 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] Loss of Decoding in WSJT-X with Audio Still Present

[Laurie, VK3AMA]

On 31/07/2019 2:03 am, Hasan al-Basri wrote:

Put this in a batch file: (use notepad to create)

taskkill /F /IM jtalert.exe


NO, don't do this!

Force killing the JTAlert process, rather than a managed shutdown, 
*doesn't close any of the JTAlert plugin processes or the Decodes 
History process*, they are all still left running becoming zombie processes.


Force killing JTAlert significantly increases the risk of corruption of 
the config.sqlite database file and the decodes database.


de Laurie VK3AMA

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

Re: [wsjt-devel] Moving WSJT-X from Debian 9 to 10

[Bill Somerville]

On 30/07/2019 20:21, Paul Bramscher wrote:
But I've got a general question with ~/.local/share/WSJT-X.  What are 
the minimally useful files to copy over, to preserve settings and 
logs?  The entire directory (except the contents of 'save') -- or is 
there a smaller subset?


Hi Paul,

I would transfer the whole directory and it's contents. You will also 
want to copy the settings file which is in ~/.config/ .It will not 
amount to a great deal of space. If you have a lot of saved .WAV files 
you might deleted them with the "Menu->File->Delete all *.wav and *.c2 
files in SaveDir" button before archiving the log files directory.


I don't understand why you would not simply backup and restore to the 
new system your entire /home directory, what do you hope to gain by 
scrapping all user files?


73
Bill
G4WJS.



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

[wsjt-devel] Moving WSJT-X from Debian 9 to 10

[Paul Bramscher]

I'll soon be upgrading my Debian 9.x to 10.0 Buster.  And while it's possible 
to perform an in-place upgrade I usually take the opportunity to replace the 
hard drive and do a fresh install entirely.  I've been compiling WSJT-X for 
awhile now and have had no problems doing so.


But I've got a general question with ~/.local/share/WSJT-X.  What are the 
minimally useful files to copy over, to preserve settings and logs?  The entire 
directory (except the contents of 'save') -- or is there a smaller subset?


73, KD0KZE / Paul
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT4 or MFSK mode

[Claude Frantz]

On 7/30/19 5:57 PM, Jesús Gutiérrez Rodríguez wrote:

Hi Jesús and all,

I am receiving confirmations via eQSL of qsos in FT4 mode, but they 
indicate that the working mode is MFSK (FT4) or only MFSK.


In a vote, 14 voting members of the ADIF development group have approved 
the proposal, resulting in the version 3.1.0 of the ADIF specification. 
There were no vote against the proposal. According to this 3.1.0 spec, 
FT4 is to be coded "MODE=MFSK SUBMODE=FT4".


I'm surprised that there were no vote against the proposal, because many 
expressed opinions did not adhere to this "MODE=MFSK SUBMODE=FT4" 
decision. In contrast, FT8 is a mode without defined submodes: 
"MODE=FT8". This may be surprising to many hams.


Best wishes,
Claude (DJ0OT)


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

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

[Hasan al-Basri]

Since I'm replacing this AMD computer with an Intel Core I5 in a short
while, I don't want to invest a ton of time chasing down this problem if it
only affects me and a couple others. It will go away when I change
computers, as I have this same combo running on another machine with no
issues.

In the mean time, here is the work-around I've set up:

Put this in a batch file: (use notepad to create)

taskkill /F /IM jtalert.exe

Mine is called jta_kill.bat
Save to desktop

Use Microsoft Scheduler to Create a Task to Run this program (a.k.a. Batch
File in this case) every day at 1:15 a.m.  (which will stop JTAlert)

Use Microsoft Scheduler to Create another Task in which you tell it run
jtalert.exe with the argument /wsjtx every day at 1:18 a.m. (which will
start JTAlert 3 min after the above kill)

Here is a YouTube video on how to do it, but I used the written
instructions that were below the video:

https://www.youtube.com/watch?v=h1Cc29ZMpr0

This video shows how to create the batch file and use it in Windows
Scheduler to Stop a program. Just create a 2nd scheduled task after this
and have it start JTAlert.exe with the /wsjtx argument.

There is a mistake in the written instructions:
Type "taskill /f /im "*filename*.exe"

Should read: taskkill /F /IM jtalert.exe

No need for the quotes and he forgot a "K" in taskkill

I can't believe how simple it was! While it doesn't solve the mystery, it
covers up the problem as long as X doesn't keep decoding for 24 hours. If
it does hang, it will get fixed at the next run of Scheduler.

73, N0AN

Hasan


On Tue, Jul 30, 2019 at 8:32 AM Black Michael  wrote:

> When it happens again do the WWV recording with Audacity and note the time
> you shut down JTAlert in the recording time indication.
> It has to be doing something to the sound recording --
>
> Having both the Audacity and WAV files would be of use.
>
>
> On Tuesday, July 30, 2019, 08:21:29 AM CDT, Hasan al-Basri <
> hbasri.schie...@gmail.com> wrote:
>
>
> Hi Mike
>
> Never. The monitor (Hi-Sense TV) is on until I go to bed, then I turn the
> TV off. Ever since I found out that there was a JTA > X interaction that
> was causing the problem, I have looked carefully in the morning when I come
> down to the shack to see if X is still decoding...and it is, except on
> those occasions every 2 days or so, when it isn't. This is NOT correlated
> with the monitor going on or off. I have looked at that issue carefully.
>
> *Further this has been going on long before I started using the HDMI TV's
> audio for JTA. I changed it to see if it would solve the issue you and I
> have been discussing (for over a month now).*
>
> I finally made some reliable, reproducible progress. JTA and X are
> interacting in such a way that decoding in X stops and can easily be
> restored by doing nothing more than closing JTA. period.
>
> I can then restart JTA and go for days. Then it will happen again, and the
> solution is the same.
> 73, N0AN
> Hasan
>
>
> On Tue, Jul 30, 2019 at 8:09 AM Black Michael  wrote:
>
> Does your monitor go to sleep?  JTAlert should only be hooking up to the
> playback device so not sure how it could affect recording.  Possible that
> the JTAlert package does passively hook up to recording...that would
> explain why a restart might have an effect on recordingperhaps changing
> the sample rate?
>
> One thing that might be of interest is, when decoding stops, switch the
> rig to WWV and record the WWV signal.  Then restart JTAlert and note the
> time it stops an starts and we can look at the WAV file to see what changes.
>
> Recording with Audacity would be nice.
>
> Mike
>
>
>
> On Tuesday, July 30, 2019, 08:04:14 AM CDT, Hasan al-Basri <
> hbasri.schie...@gmail.com> wrote:
>
>
> Totally different sound cards. JTA uses my HDMI monitor seen as an Nvidia,
> X uses my USB sound dongle. I've changed dongles, ...no difference. I've
> chased the sound card potential issue from several angles...that's not it.
>
> ...and Windows system uses the internal sound card of the computer.
>
> Hasan
>
>
> On Tue, Jul 30, 2019 at 7:43 AM Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> What do you have for the soundcard setting in JTAlert and WSJT-X?
>
>
>
>
> On Tuesday, July 30, 2019, 07:30:17 AM CDT, Hasan al-Basri <
> hbasri.schie...@gmail.com> wrote:
>
>
> Uwe,
> I just changed both those settings you recommended. Now, I'll have to
> wait, up to a couple days to see if it accomplished anything.
>
> Unfortunately the onset of the problem is random, and can take 2 or 3 days
> or only a few hours. Curing it is easy. I'll report back as I'm watching
> it. For sure will post first failure, if your idea did not work. Thanks for
> the suggestion.
> 73, N0AN
> Hasan
>
>
> On Tue, Jul 30, 2019 at 5:52 AM DG2YCB, Uwe  wrote:
>
> Hi Hasan,
>
>
>
> An interesting observation!  What if you uncheck the boxed “Color Band
> Activity…” and/or “Highlight Band Activity…”? Is the error still there or
> is it 

[wsjt-devel] FT4 or MFSK mode

[Jesús Gutiérrez Rodríguez]

I am receiving confirmations via eQSL of qsos in FT4 mode, but they
indicate that the working mode is MFSK (FT4) or only MFSK.
In the Log40M guard book, the qsos are listed as FT4 in mode.
I have reviewed the instructions of FT4, FT8 on the WSJT-X website and
cannot find references to MFSK or MFSK (FT4) mode.

I appreciate a clarification
Cordially,
Jesus, EA1YR
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] SUGGESTION: Display or not, confirmed QSOs

[Gene Marsh via wsjt-devel]

Joe (and the team),

First, the last (new) rev of WSJT-X is WAY FASTER to decode a busy band.  THANK 
YOU!

My suggestion: Because I made thousands of FT8 contacts (especially on 20m, 30m 
and 40m), a huge amount of the CQ decodes on a busy band are GREEN (confirmed 
QSO for call/band/etc). Even if I check CQ Only, I have 2 pages of CQs.  

Can you change (maybe in settings, or a check box on the main screen) to  
filter out decodes for confirmed calls? Only for CQs.  Easy to do - you have 
the logic for parsing.

If I missed it, and the program has this logic, please explain how and reply to 
me with a “DOH!”

;)

73 de W8NET Miles / “Gene”
Secretary, Portage County Amateur Radio Service (PCARS)
3905 Century Club - Master #47
DV2/W8NET in the Philippines
Licensed since 1974___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Loggin causeing no decode

[Al]

( wsjt-x 2.1.0(32 or 64), JtAlert 2.14.1, DXKeeper 15.0.0, wint10 1903 )

There appears to be an interaction of wsjt, JTAlert and DXKeeper that 
causes WSJT(ft4/8) to miss a decode cycle after a contact is logger. 
JTAlert is configured to log contacts to DXK rather than WSJT direct to DXK.


1) Tune in band with signals to decode, observe decodes
2) enter a call in WSJT DX call
3) during a decode cycle, force logging the call, observe call logged to DXK
4) observe next cycle of wsjt is NOT decoded, signals preset in 
waterfall, but no .wav file is recorded.


If logging to DXK is turned off in JTA, WSJT decodes will continue 
following a log operation.


Might be related to Hasan's loss of decode..

AL, K0VM

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

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

[Black Michael via wsjt-devel]

When it happens again do the WWV recording with Audacity and note the time you 
shut down JTAlert in the recording time indication.It has to be doing something 
to the sound recording -- 
Having both the Audacity and WAV files would be of use. 

On Tuesday, July 30, 2019, 08:21:29 AM CDT, Hasan al-Basri 
 wrote:  
 
 Hi Mike
Never. The monitor (Hi-Sense TV) is on until I go to bed, then I turn the TV 
off. Ever since I found out that there was a JTA > X interaction that was 
causing the problem, I have looked carefully in the morning when I come down to 
the shack to see if X is still decoding...and it is, except on those occasions 
every 2 days or so, when it isn't. This is NOT correlated with the monitor 
going on or off. I have looked at that issue carefully.
Further this has been going on long before I started using the HDMI TV's audio 
for JTA. I changed it to see if it would solve the issue you and I have been 
discussing (for over a month now).
I finally made some reliable, reproducible progress. JTA and X are interacting 
in such a way that decoding in X stops and can easily be restored by doing 
nothing more than closing JTA. period.
I can then restart JTA and go for days. Then it will happen again, and the 
solution is the same. 73, N0ANHasan

On Tue, Jul 30, 2019 at 8:09 AM Black Michael  wrote:

Does your monitor go to sleep?  JTAlert should only be hooking up to the 
playback device so not sure how it could affect recording.  Possible that the 
JTAlert package does passively hook up to recording...that would explain why a 
restart might have an effect on recordingperhaps changing the sample rate?
One thing that might be of interest is, when decoding stops, switch the rig to 
WWV and record the WWV signal.  Then restart JTAlert and note the time it stops 
an starts and we can look at the WAV file to see what changes.
Recording with Audacity would be nice.
Mike
 

On Tuesday, July 30, 2019, 08:04:14 AM CDT, Hasan al-Basri 
 wrote:  
 
 Totally different sound cards. JTA uses my HDMI monitor seen as an Nvidia, X 
uses my USB sound dongle. I've changed dongles, ...no difference. I've chased 
the sound card potential issue from several angles...that's not it.
...and Windows system uses the internal sound card of the computer.
Hasan

On Tue, Jul 30, 2019 at 7:43 AM Black Michael via wsjt-devel 
 wrote:

What do you have for the soundcard setting in JTAlert and WSJT-X?

 

On Tuesday, July 30, 2019, 07:30:17 AM CDT, Hasan al-Basri 
 wrote:  
 
 Uwe,I just changed both those settings you recommended. Now, I'll have to 
wait, up to a couple days to see if it accomplished anything.
Unfortunately the onset of the problem is random, and can take 2 or 3 days or 
only a few hours. Curing it is easy. I'll report back as I'm watching it. For 
sure will post first failure, if your idea did not work. Thanks for the 
suggestion. 73, N0ANHasan

On Tue, Jul 30, 2019 at 5:52 AM DG2YCB, Uwe  wrote:


Hi Hasan,

 

An interesting observation!  What if you uncheck the boxed “Color Band 
Activity…” and/or “Highlight Band Activity…”? Is the error still there or is it 
gone?

 



 

 

I had in the past also some (other) troubles with JTAlert, but it turned out 
that some files on my computer must have been corrupted. Uninstalled JTAlert 
completely, removed all remaining files manually and the reinstalled JTAlert 
again, and all the errors were gone. Maybe also worth to try… 

 

73 de Uwe, DG2YCB 

 

Von: Hasan al-Basri [mailto:hbasri.schie...@gmail.com] 
Gesendet: Dienstag, 30. Juli 2019 12:33
An: WSJT software development
Betreff: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

 

First of all, no, the cause is not clock error.

 

I have found the "proximate" cause, however, after weeks of hunting. I worked 
with W9MDB and tested/considered many potential causes. I even  thought I had 
found it several times. In all those cases there was a confounding variable, 
which I have now isolated. I have found the cure, just not the cause, hence I'm 
posting this info here.

 

  I have been fighting this problem for weeks, and finally found a reproducible 
 set of actions that cures the problem, immediately every time! (until it 
recurs and then the same steps solve it)

 

In this discussion X means the 64 bit 2.01 version of WSJT-X, and JTA means 
JTAlert. (earlier versions of both programs act the same way, since installing 
the first 64 bit version of X. That may have been a coincidence, (64 bit 
install), but what follows is not!

 

I have observed 100%  correlation  between the problem and running both 
programs involved listed below. I am not assigning cause, but some sort of 
interaction between the two programs has got to be the cause, as doing what I 
describe below restores decoding in X every time.

 

What doesn't work:

Stopping X with button.

Closing X and restarting it.

Closing other running programs like Chrome, SDRC, etc

 

What has cured it every time:

 

 Shut 

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

[Hasan al-Basri]

Hi Mike

Never. The monitor (Hi-Sense TV) is on until I go to bed, then I turn the
TV off. Ever since I found out that there was a JTA > X interaction that
was causing the problem, I have looked carefully in the morning when I come
down to the shack to see if X is still decoding...and it is, except on
those occasions every 2 days or so, when it isn't. This is NOT correlated
with the monitor going on or off. I have looked at that issue carefully.

*Further this has been going on long before I started using the HDMI TV's
audio for JTA. I changed it to see if it would solve the issue you and I
have been discussing (for over a month now).*

I finally made some reliable, reproducible progress. JTA and X are
interacting in such a way that decoding in X stops and can easily be
restored by doing nothing more than closing JTA. period.

I can then restart JTA and go for days. Then it will happen again, and the
solution is the same.
73, N0AN
Hasan


On Tue, Jul 30, 2019 at 8:09 AM Black Michael  wrote:

> Does your monitor go to sleep?  JTAlert should only be hooking up to the
> playback device so not sure how it could affect recording.  Possible that
> the JTAlert package does passively hook up to recording...that would
> explain why a restart might have an effect on recordingperhaps changing
> the sample rate?
>
> One thing that might be of interest is, when decoding stops, switch the
> rig to WWV and record the WWV signal.  Then restart JTAlert and note the
> time it stops an starts and we can look at the WAV file to see what changes.
>
> Recording with Audacity would be nice.
>
> Mike
>
>
>
> On Tuesday, July 30, 2019, 08:04:14 AM CDT, Hasan al-Basri <
> hbasri.schie...@gmail.com> wrote:
>
>
> Totally different sound cards. JTA uses my HDMI monitor seen as an Nvidia,
> X uses my USB sound dongle. I've changed dongles, ...no difference. I've
> chased the sound card potential issue from several angles...that's not it.
>
> ...and Windows system uses the internal sound card of the computer.
>
> Hasan
>
>
> On Tue, Jul 30, 2019 at 7:43 AM Black Michael via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> What do you have for the soundcard setting in JTAlert and WSJT-X?
>
>
>
>
> On Tuesday, July 30, 2019, 07:30:17 AM CDT, Hasan al-Basri <
> hbasri.schie...@gmail.com> wrote:
>
>
> Uwe,
> I just changed both those settings you recommended. Now, I'll have to
> wait, up to a couple days to see if it accomplished anything.
>
> Unfortunately the onset of the problem is random, and can take 2 or 3 days
> or only a few hours. Curing it is easy. I'll report back as I'm watching
> it. For sure will post first failure, if your idea did not work. Thanks for
> the suggestion.
> 73, N0AN
> Hasan
>
>
> On Tue, Jul 30, 2019 at 5:52 AM DG2YCB, Uwe  wrote:
>
> Hi Hasan,
>
>
>
> An interesting observation!  What if you uncheck the boxed “Color Band
> Activity…” and/or “Highlight Band Activity…”? Is the error still there or
> is it gone?
>
>
>
>
>
>
>
> I had in the past also some (other) troubles with JTAlert, but it turned
> out that some files on my computer must have been corrupted. Uninstalled
> JTAlert completely, removed all remaining files manually and the
> reinstalled JTAlert again, and all the errors were gone. Maybe also worth
> to try…
>
>
>
> 73 de Uwe, DG2YCB
>
>
>
> *Von:* Hasan al-Basri [mailto:hbasri.schie...@gmail.com]
> *Gesendet:* Dienstag, 30. Juli 2019 12:33
> *An:* WSJT software development
> *Betreff:* [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still
> Present
>
>
>
> First of all, no, the cause is not clock error.
>
>
>
> I have found the "proximate" cause, however, after weeks of hunting. I
> worked with W9MDB and tested/considered many potential causes. I even
> thought I had found it several times. In all those cases there was a
> confounding variable, which I have now isolated. I have found the cure,
> just not the cause, hence I'm posting this info here.
>
>
>
>   I have been fighting this problem for weeks, and finally found a
> *reproducible*  set of actions that cures the problem, immediately every
> time! (until it recurs and then the same steps solve it)
>
>
>
> In this discussion X means the 64 bit 2.01 version of WSJT-X, and JTA
> means JTAlert. (earlier versions of both programs act the same way, since
> installing the first 64 bit version of X. That may have been a coincidence,
> (64 bit install), but what follows is not!
>
>
>
> *I have observed 100%  correlation  between the problem and running both
> programs involved listed below.* I am *not* assigning cause, but some
> sort of interaction between the two programs has got to be the cause, as 
> *doing
> what I describe below restores decoding in X every time.*
>
>
>
> What doesn't work:
>
> Stopping X with button.
>
> Closing X and restarting it.
>
> Closing other running programs like Chrome, SDRC, etc
>
>
>
> What has cured it every time:
>
>
>
> * Shut down JTAlert*.
>
>
>
> Proof:
>
>
>
> *Every time I found X not 

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

[Black Michael via wsjt-devel]

Does your monitor go to sleep?  JTAlert should only be hooking up to the 
playback device so not sure how it could affect recording.  Possible that the 
JTAlert package does passively hook up to recording...that would explain why a 
restart might have an effect on recordingperhaps changing the sample rate?
One thing that might be of interest is, when decoding stops, switch the rig to 
WWV and record the WWV signal.  Then restart JTAlert and note the time it stops 
an starts and we can look at the WAV file to see what changes.
Recording with Audacity would be nice.
Mike
 

On Tuesday, July 30, 2019, 08:04:14 AM CDT, Hasan al-Basri 
 wrote:  
 
 Totally different sound cards. JTA uses my HDMI monitor seen as an Nvidia, X 
uses my USB sound dongle. I've changed dongles, ...no difference. I've chased 
the sound card potential issue from several angles...that's not it.
...and Windows system uses the internal sound card of the computer.
Hasan

On Tue, Jul 30, 2019 at 7:43 AM Black Michael via wsjt-devel 
 wrote:

What do you have for the soundcard setting in JTAlert and WSJT-X?

 

On Tuesday, July 30, 2019, 07:30:17 AM CDT, Hasan al-Basri 
 wrote:  
 
 Uwe,I just changed both those settings you recommended. Now, I'll have to 
wait, up to a couple days to see if it accomplished anything.
Unfortunately the onset of the problem is random, and can take 2 or 3 days or 
only a few hours. Curing it is easy. I'll report back as I'm watching it. For 
sure will post first failure, if your idea did not work. Thanks for the 
suggestion. 73, N0ANHasan

On Tue, Jul 30, 2019 at 5:52 AM DG2YCB, Uwe  wrote:


Hi Hasan,

 

An interesting observation!  What if you uncheck the boxed “Color Band 
Activity…” and/or “Highlight Band Activity…”? Is the error still there or is it 
gone?

 



 

 

I had in the past also some (other) troubles with JTAlert, but it turned out 
that some files on my computer must have been corrupted. Uninstalled JTAlert 
completely, removed all remaining files manually and the reinstalled JTAlert 
again, and all the errors were gone. Maybe also worth to try… 

 

73 de Uwe, DG2YCB 

 

Von: Hasan al-Basri [mailto:hbasri.schie...@gmail.com] 
Gesendet: Dienstag, 30. Juli 2019 12:33
An: WSJT software development
Betreff: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

 

First of all, no, the cause is not clock error.

 

I have found the "proximate" cause, however, after weeks of hunting. I worked 
with W9MDB and tested/considered many potential causes. I even  thought I had 
found it several times. In all those cases there was a confounding variable, 
which I have now isolated. I have found the cure, just not the cause, hence I'm 
posting this info here.

 

  I have been fighting this problem for weeks, and finally found a reproducible 
 set of actions that cures the problem, immediately every time! (until it 
recurs and then the same steps solve it)

 

In this discussion X means the 64 bit 2.01 version of WSJT-X, and JTA means 
JTAlert. (earlier versions of both programs act the same way, since installing 
the first 64 bit version of X. That may have been a coincidence, (64 bit 
install), but what follows is not!

 

I have observed 100%  correlation  between the problem and running both 
programs involved listed below. I am not assigning cause, but some sort of 
interaction between the two programs has got to be the cause, as doing what I 
describe below restores decoding in X every time.

 

What doesn't work:

Stopping X with button.

Closing X and restarting it.

Closing other running programs like Chrome, SDRC, etc

 

What has cured it every time:

 

 Shut down JTAlert. 

 

Proof:

 

Every time I found X not decoding, but audio was still showing on the 
thermometer and also showing on the waterfall: 

 

I closed JTA and immediately on the very next sequence, X began decoding again. 
(On its own, I did no intervention with X at all)  I could then restart JTA and 
X would continue to decode for hours, if not days (2 or 3 max). When it 
eventually stopped decoding again, a simple closing of JTA restored X decoding 
at the next sequence.

 

So, the stoppages are random, going no more than a few days, but the cure is 
not!

 

This has worked EVERY time since discovering the correlation between X and JTA!

 

Prior to this, the only cure was to reboot the computer.

 

If you are having this problem, and also run JTA, try my solution.

 

I have no idea what the cause might be, but this correlation should give  the 
development team an idea where to look.

 

Win10 Home, 64 bit, AMD Quad Core

 

Also, this does not happen on every computer I have running copies of X and 
JTA. Not every one of them is using JTA. 

 

73, N0AN

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

___
wsjt-devel mailing list

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

[Hasan al-Basri]

Bobby,
That has always been my setting. (not checked)
tnx, 73, N0AN
Hasan


On Tue, Jul 30, 2019 at 8:03 AM Bobby Chandler  wrote:

> Hasan,
>
> Try this:
>
> On wsjtx go to settings, General. Make sure 'Start new period decodes at
> top' is not ticked.
>
> Bobby/N4AU
> On 7/30/2019 7:26 AM, Hasan al-Basri wrote:
>
> Uwe,
> I just changed both those settings you recommended. Now, I'll have to
> wait, up to a couple days to see if it accomplished anything.
>
> Unfortunately the onset of the problem is random, and can take 2 or 3 days
> or only a few hours. Curing it is easy. I'll report back as I'm watching
> it. For sure will post first failure, if your idea did not work. Thanks for
> the suggestion.
> 73, N0AN
> Hasan
>
>
> On Tue, Jul 30, 2019 at 5:52 AM DG2YCB, Uwe  wrote:
>
>> Hi Hasan,
>>
>>
>>
>> An interesting observation!  What if you uncheck the boxed “Color Band
>> Activity…” and/or “Highlight Band Activity…”? Is the error still there or
>> is it gone?
>>
>>
>>
>>
>>
>>
>>
>> I had in the past also some (other) troubles with JTAlert, but it turned
>> out that some files on my computer must have been corrupted. Uninstalled
>> JTAlert completely, removed all remaining files manually and the
>> reinstalled JTAlert again, and all the errors were gone. Maybe also worth
>> to try…
>>
>>
>>
>> 73 de Uwe, DG2YCB
>>
>>
>>
>> *Von:* Hasan al-Basri [mailto:hbasri.schie...@gmail.com]
>> *Gesendet:* Dienstag, 30. Juli 2019 12:33
>> *An:* WSJT software development
>> *Betreff:* [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still
>> Present
>>
>>
>>
>> First of all, no, the cause is not clock error.
>>
>>
>>
>> I have found the "proximate" cause, however, after weeks of hunting. I
>> worked with W9MDB and tested/considered many potential causes. I even
>> thought I had found it several times. In all those cases there was a
>> confounding variable, which I have now isolated. I have found the cure,
>> just not the cause, hence I'm posting this info here.
>>
>>
>>
>>   I have been fighting this problem for weeks, and finally found a
>> *reproducible*  set of actions that cures the problem, immediately every
>> time! (until it recurs and then the same steps solve it)
>>
>>
>>
>> In this discussion X means the 64 bit 2.01 version of WSJT-X, and JTA
>> means JTAlert. (earlier versions of both programs act the same way, since
>> installing the first 64 bit version of X. That may have been a coincidence,
>> (64 bit install), but what follows is not!
>>
>>
>>
>> *I have observed 100%  correlation  between the problem and running both
>> programs involved listed below.* I am *not* assigning cause, but some
>> sort of interaction between the two programs has got to be the cause, as 
>> *doing
>> what I describe below restores decoding in X every time.*
>>
>>
>>
>> What doesn't work:
>>
>> Stopping X with button.
>>
>> Closing X and restarting it.
>>
>> Closing other running programs like Chrome, SDRC, etc
>>
>>
>>
>> What has cured it every time:
>>
>>
>>
>> * Shut down JTAlert*.
>>
>>
>>
>> Proof:
>>
>>
>>
>> *Every time I found X not decoding, but audio was still showing on the
>> thermometer and also showing on the waterfall*:
>>
>>
>>
>> *I closed JTA and immediately on the very next sequence, X began decoding
>> again*. (On its own, I did no intervention with X at all)  *I could then
>> restart JTA and X would continue to decode for hours, if not days (2 or 3
>> max).* When it eventually stopped decoding again, a simple closing of
>> JTA restored X decoding at the next sequence.
>>
>>
>>
>> So, the stoppages are random, going no more than a few days, *but the
>> cure is not*!
>>
>>
>>
>> This has worked EVERY time since discovering the correlation between X
>> and JTA!
>>
>>
>>
>> Prior to this, the only cure was to reboot the computer.
>>
>>
>>
>> If you are having this problem, and also run JTA, try my solution.
>>
>>
>>
>> I have no idea what the cause might be, but this correlation should give
>> the development team an idea where to look.
>>
>>
>>
>> Win10 Home, 64 bit, AMD Quad Core
>>
>>
>>
>> Also, this does not happen on every computer I have running copies of X
>> and JTA. Not every one of them is using JTA.
>>
>>
>>
>> 73, N0AN
>>
>> Hasan
>> ___
>> 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
>
> --
> Bobby chandlerbob...@bellsouth.net
>n...@arrl.net
>
> ___
> 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] Loss of Decoding in WSJT-X with Audio Still Present

[Hasan al-Basri]

Totally different sound cards. JTA uses my HDMI monitor seen as an Nvidia,
X uses my USB sound dongle. I've changed dongles, ...no difference. I've
chased the sound card potential issue from several angles...that's not it.

...and Windows system uses the internal sound card of the computer.

Hasan


On Tue, Jul 30, 2019 at 7:43 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> What do you have for the soundcard setting in JTAlert and WSJT-X?
>
>
>
>
> On Tuesday, July 30, 2019, 07:30:17 AM CDT, Hasan al-Basri <
> hbasri.schie...@gmail.com> wrote:
>
>
> Uwe,
> I just changed both those settings you recommended. Now, I'll have to
> wait, up to a couple days to see if it accomplished anything.
>
> Unfortunately the onset of the problem is random, and can take 2 or 3 days
> or only a few hours. Curing it is easy. I'll report back as I'm watching
> it. For sure will post first failure, if your idea did not work. Thanks for
> the suggestion.
> 73, N0AN
> Hasan
>
>
> On Tue, Jul 30, 2019 at 5:52 AM DG2YCB, Uwe  wrote:
>
> Hi Hasan,
>
>
>
> An interesting observation!  What if you uncheck the boxed “Color Band
> Activity…” and/or “Highlight Band Activity…”? Is the error still there or
> is it gone?
>
>
>
>
>
>
>
> I had in the past also some (other) troubles with JTAlert, but it turned
> out that some files on my computer must have been corrupted. Uninstalled
> JTAlert completely, removed all remaining files manually and the
> reinstalled JTAlert again, and all the errors were gone. Maybe also worth
> to try…
>
>
>
> 73 de Uwe, DG2YCB
>
>
>
> *Von:* Hasan al-Basri [mailto:hbasri.schie...@gmail.com]
> *Gesendet:* Dienstag, 30. Juli 2019 12:33
> *An:* WSJT software development
> *Betreff:* [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still
> Present
>
>
>
> First of all, no, the cause is not clock error.
>
>
>
> I have found the "proximate" cause, however, after weeks of hunting. I
> worked with W9MDB and tested/considered many potential causes. I even
> thought I had found it several times. In all those cases there was a
> confounding variable, which I have now isolated. I have found the cure,
> just not the cause, hence I'm posting this info here.
>
>
>
>   I have been fighting this problem for weeks, and finally found a
> *reproducible*  set of actions that cures the problem, immediately every
> time! (until it recurs and then the same steps solve it)
>
>
>
> In this discussion X means the 64 bit 2.01 version of WSJT-X, and JTA
> means JTAlert. (earlier versions of both programs act the same way, since
> installing the first 64 bit version of X. That may have been a coincidence,
> (64 bit install), but what follows is not!
>
>
>
> *I have observed 100%  correlation  between the problem and running both
> programs involved listed below.* I am *not* assigning cause, but some
> sort of interaction between the two programs has got to be the cause, as 
> *doing
> what I describe below restores decoding in X every time.*
>
>
>
> What doesn't work:
>
> Stopping X with button.
>
> Closing X and restarting it.
>
> Closing other running programs like Chrome, SDRC, etc
>
>
>
> What has cured it every time:
>
>
>
> * Shut down JTAlert*.
>
>
>
> Proof:
>
>
>
> *Every time I found X not decoding, but audio was still showing on the
> thermometer and also showing on the waterfall*:
>
>
>
> *I closed JTA and immediately on the very next sequence, X began decoding
> again*. (On its own, I did no intervention with X at all)  *I could then
> restart JTA and X would continue to decode for hours, if not days (2 or 3
> max).* When it eventually stopped decoding again, a simple closing of JTA
> restored X decoding at the next sequence.
>
>
>
> So, the stoppages are random, going no more than a few days, *but the
> cure is not*!
>
>
>
> This has worked EVERY time since discovering the correlation between X and
> JTA!
>
>
>
> Prior to this, the only cure was to reboot the computer.
>
>
>
> If you are having this problem, and also run JTA, try my solution.
>
>
>
> I have no idea what the cause might be, but this correlation should give
> the development team an idea where to look.
>
>
>
> Win10 Home, 64 bit, AMD Quad Core
>
>
>
> Also, this does not happen on every computer I have running copies of X
> and JTA. Not every one of them is using JTA.
>
>
>
> 73, N0AN
>
> Hasan
> ___
> 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

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

[Bobby Chandler]

  
  
Hasan,
Try this:
On wsjtx go to settings, General. Make sure
'Start new period decodes at top' is not ticked.
Bobby/N4AU

On 7/30/2019 7:26 AM, Hasan al-Basri
  wrote:


  
  
Uwe,
I just
  changed both those settings you recommended. Now, I'll have to
  wait, up to a couple days to see if it accomplished anything.


Unfortunately
  the onset of the problem is random, and can take 2 or 3 days
  or only a few hours. Curing it is easy. I'll report back as
  I'm watching it. For sure will post first failure, if your
  idea did not work. Thanks for the suggestion. 
73, N0AN

  

  
Hasan
  

  


  
  
  
On Tue, Jul 30, 2019 at 5:52
  AM DG2YCB, Uwe  wrote:


  

  Hi Hasan,
   
  An interesting observation!  What if you
  uncheck the boxed “Color Band Activity…” and/or
  “Highlight Band Activity…”? Is the error still there
  or is it gone?
   
  
   
   
  I had in the past also some (other)
  troubles with JTAlert, but it turned out that some
  files on my computer must have been corrupted.
  Uninstalled JTAlert completely, removed all remaining
  files manually and the reinstalled JTAlert again, and
  all the errors were gone. Maybe also worth to try… 
   
  73
  de Uwe, DG2YCB 
   
  Von:
  Hasan al-Basri [mailto:hbasri.schie...@gmail.com]
  
  Gesendet: Dienstag, 30. Juli 2019 12:33
  An: WSJT software development
  Betreff: [wsjt-devel] Loss of Decoding in
  WSJT-X with Audio Still Present
   
  

  First
  of all, no, the cause is not clock error.


   


  I
  have found the "proximate" cause, however, after
  weeks of hunting. I worked with W9MDB and
  tested/considered many potential causes. I even 
  thought I had found it several times. In all those
  cases there was a confounding variable, which I
  have now isolated. I have found the cure, just not
  the cause, hence I'm posting this info here.


   


    I
  have been fighting this problem for weeks, and
  finally found a reproducible  set of
  actions that cures the problem, immediately every
  time! (until it recurs and then the same steps
  solve it)
  
 
  
  
In
this discussion X means the 64 bit 2.01 version
of WSJT-X, and JTA means JTAlert. (earlier
versions of both programs act the same way,
since installing the first 64 bit version of X.
That may have been a coincidence, (64 bit
install), but what follows is not!

   


  I have observed 100% 
correlation  between the problem and running
both programs involved listed below. I am not
  assigning cause, but some sort of interaction
  between the two programs has got to be the
  cause, as doing what I describe below
restores decoding in X every time.


   


  What
  doesn't work:


  Stopping
  X with button.


  Closing
  X and restarting it.


  Closing
  other running programs like Chrome, SDRC, etc


   


 

Re: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

[Black Michael via wsjt-devel]

What do you have for the soundcard setting in JTAlert and WSJT-X?

 

On Tuesday, July 30, 2019, 07:30:17 AM CDT, Hasan al-Basri 
 wrote:  
 
 Uwe,I just changed both those settings you recommended. Now, I'll have to 
wait, up to a couple days to see if it accomplished anything.
Unfortunately the onset of the problem is random, and can take 2 or 3 days or 
only a few hours. Curing it is easy. I'll report back as I'm watching it. For 
sure will post first failure, if your idea did not work. Thanks for the 
suggestion. 73, N0ANHasan

On Tue, Jul 30, 2019 at 5:52 AM DG2YCB, Uwe  wrote:


Hi Hasan,

 

An interesting observation!  What if you uncheck the boxed “Color Band 
Activity…” and/or “Highlight Band Activity…”? Is the error still there or is it 
gone?

 



 

 

I had in the past also some (other) troubles with JTAlert, but it turned out 
that some files on my computer must have been corrupted. Uninstalled JTAlert 
completely, removed all remaining files manually and the reinstalled JTAlert 
again, and all the errors were gone. Maybe also worth to try… 

 

73 de Uwe, DG2YCB 

 

Von: Hasan al-Basri [mailto:hbasri.schie...@gmail.com] 
Gesendet: Dienstag, 30. Juli 2019 12:33
An: WSJT software development
Betreff: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

 

First of all, no, the cause is not clock error.

 

I have found the "proximate" cause, however, after weeks of hunting. I worked 
with W9MDB and tested/considered many potential causes. I even  thought I had 
found it several times. In all those cases there was a confounding variable, 
which I have now isolated. I have found the cure, just not the cause, hence I'm 
posting this info here.

 

  I have been fighting this problem for weeks, and finally found a reproducible 
 set of actions that cures the problem, immediately every time! (until it 
recurs and then the same steps solve it)

 

In this discussion X means the 64 bit 2.01 version of WSJT-X, and JTA means 
JTAlert. (earlier versions of both programs act the same way, since installing 
the first 64 bit version of X. That may have been a coincidence, (64 bit 
install), but what follows is not!

 

I have observed 100%  correlation  between the problem and running both 
programs involved listed below. I am not assigning cause, but some sort of 
interaction between the two programs has got to be the cause, as doing what I 
describe below restores decoding in X every time.

 

What doesn't work:

Stopping X with button.

Closing X and restarting it.

Closing other running programs like Chrome, SDRC, etc

 

What has cured it every time:

 

 Shut down JTAlert. 

 

Proof:

 

Every time I found X not decoding, but audio was still showing on the 
thermometer and also showing on the waterfall: 

 

I closed JTA and immediately on the very next sequence, X began decoding again. 
(On its own, I did no intervention with X at all)  I could then restart JTA and 
X would continue to decode for hours, if not days (2 or 3 max). When it 
eventually stopped decoding again, a simple closing of JTA restored X decoding 
at the next sequence.

 

So, the stoppages are random, going no more than a few days, but the cure is 
not!

 

This has worked EVERY time since discovering the correlation between X and JTA!

 

Prior to this, the only cure was to reboot the computer.

 

If you are having this problem, and also run JTA, try my solution.

 

I have no idea what the cause might be, but this correlation should give  the 
development team an idea where to look.

 

Win10 Home, 64 bit, AMD Quad Core

 

Also, this does not happen on every computer I have running copies of X and 
JTA. Not every one of them is using JTA. 

 

73, N0AN

Hasan
___
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] Loss of Decoding in WSJT-X with Audio Still Present

[Hasan al-Basri]

Uwe,
I just changed both those settings you recommended. Now, I'll have to wait,
up to a couple days to see if it accomplished anything.

Unfortunately the onset of the problem is random, and can take 2 or 3 days
or only a few hours. Curing it is easy. I'll report back as I'm watching
it. For sure will post first failure, if your idea did not work. Thanks for
the suggestion.
73, N0AN
Hasan


On Tue, Jul 30, 2019 at 5:52 AM DG2YCB, Uwe  wrote:

> Hi Hasan,
>
>
>
> An interesting observation!  What if you uncheck the boxed “Color Band
> Activity…” and/or “Highlight Band Activity…”? Is the error still there or
> is it gone?
>
>
>
>
>
>
>
> I had in the past also some (other) troubles with JTAlert, but it turned
> out that some files on my computer must have been corrupted. Uninstalled
> JTAlert completely, removed all remaining files manually and the
> reinstalled JTAlert again, and all the errors were gone. Maybe also worth
> to try…
>
>
>
> 73 de Uwe, DG2YCB
>
>
>
> *Von:* Hasan al-Basri [mailto:hbasri.schie...@gmail.com]
> *Gesendet:* Dienstag, 30. Juli 2019 12:33
> *An:* WSJT software development
> *Betreff:* [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still
> Present
>
>
>
> First of all, no, the cause is not clock error.
>
>
>
> I have found the "proximate" cause, however, after weeks of hunting. I
> worked with W9MDB and tested/considered many potential causes. I even
> thought I had found it several times. In all those cases there was a
> confounding variable, which I have now isolated. I have found the cure,
> just not the cause, hence I'm posting this info here.
>
>
>
>   I have been fighting this problem for weeks, and finally found a
> *reproducible*  set of actions that cures the problem, immediately every
> time! (until it recurs and then the same steps solve it)
>
>
>
> In this discussion X means the 64 bit 2.01 version of WSJT-X, and JTA
> means JTAlert. (earlier versions of both programs act the same way, since
> installing the first 64 bit version of X. That may have been a coincidence,
> (64 bit install), but what follows is not!
>
>
>
> *I have observed 100%  correlation  between the problem and running both
> programs involved listed below.* I am *not* assigning cause, but some
> sort of interaction between the two programs has got to be the cause, as 
> *doing
> what I describe below restores decoding in X every time.*
>
>
>
> What doesn't work:
>
> Stopping X with button.
>
> Closing X and restarting it.
>
> Closing other running programs like Chrome, SDRC, etc
>
>
>
> What has cured it every time:
>
>
>
> * Shut down JTAlert*.
>
>
>
> Proof:
>
>
>
> *Every time I found X not decoding, but audio was still showing on the
> thermometer and also showing on the waterfall*:
>
>
>
> *I closed JTA and immediately on the very next sequence, X began decoding
> again*. (On its own, I did no intervention with X at all)  *I could then
> restart JTA and X would continue to decode for hours, if not days (2 or 3
> max).* When it eventually stopped decoding again, a simple closing of JTA
> restored X decoding at the next sequence.
>
>
>
> So, the stoppages are random, going no more than a few days, *but the
> cure is not*!
>
>
>
> This has worked EVERY time since discovering the correlation between X and
> JTA!
>
>
>
> Prior to this, the only cure was to reboot the computer.
>
>
>
> If you are having this problem, and also run JTA, try my solution.
>
>
>
> I have no idea what the cause might be, but this correlation should give
> the development team an idea where to look.
>
>
>
> Win10 Home, 64 bit, AMD Quad Core
>
>
>
> Also, this does not happen on every computer I have running copies of X
> and JTA. Not every one of them is using JTA.
>
>
>
> 73, N0AN
>
> Hasan
> ___
> 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] Loss of Decoding in WSJT-X with Audio Still Present

[DG2YCB, Uwe]

Hi Hasan,

 

An interesting observation!  What if you uncheck the boxed “Color Band 
Activity…” and/or “Highlight Band Activity…”? Is the error still there or is it 
gone?

 



 

 

I had in the past also some (other) troubles with JTAlert, but it turned out 
that some files on my computer must have been corrupted. Uninstalled JTAlert 
completely, removed all remaining files manually and the reinstalled JTAlert 
again, and all the errors were gone. Maybe also worth to try… 

 

73 de Uwe, DG2YCB 

 

Von: Hasan al-Basri [mailto:hbasri.schie...@gmail.com] 
Gesendet: Dienstag, 30. Juli 2019 12:33
An: WSJT software development
Betreff: [wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

 

First of all, no, the cause is not clock error.

 

I have found the "proximate" cause, however, after weeks of hunting. I worked 
with W9MDB and tested/considered many potential causes. I even  thought I had 
found it several times. In all those cases there was a confounding variable, 
which I have now isolated. I have found the cure, just not the cause, hence I'm 
posting this info here.

 

  I have been fighting this problem for weeks, and finally found a reproducible 
 set of actions that cures the problem, immediately every time! (until it 
recurs and then the same steps solve it)

 

In this discussion X means the 64 bit 2.01 version of WSJT-X, and JTA means 
JTAlert. (earlier versions of both programs act the same way, since installing 
the first 64 bit version of X. That may have been a coincidence, (64 bit 
install), but what follows is not!

 

I have observed 100%  correlation  between the problem and running both 
programs involved listed below. I am not assigning cause, but some sort of 
interaction between the two programs has got to be the cause, as doing what I 
describe below restores decoding in X every time.

 

What doesn't work:

Stopping X with button.

Closing X and restarting it.

Closing other running programs like Chrome, SDRC, etc

 

What has cured it every time:

 

 Shut down JTAlert. 

 

Proof:

 

Every time I found X not decoding, but audio was still showing on the 
thermometer and also showing on the waterfall: 

 

I closed JTA and immediately on the very next sequence, X began decoding again. 
(On its own, I did no intervention with X at all)  I could then restart JTA and 
X would continue to decode for hours, if not days (2 or 3 max). When it 
eventually stopped decoding again, a simple closing of JTA restored X decoding 
at the next sequence.

 

So, the stoppages are random, going no more than a few days, but the cure is 
not!

 

This has worked EVERY time since discovering the correlation between X and JTA!

 

Prior to this, the only cure was to reboot the computer.

 

If you are having this problem, and also run JTA, try my solution.

 

I have no idea what the cause might be, but this correlation should give  the 
development team an idea where to look.

 

Win10 Home, 64 bit, AMD Quad Core

 

Also, this does not happen on every computer I have running copies of X and 
JTA. Not every one of them is using JTA. 

 

73, N0AN

Hasan

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

[wsjt-devel] Loss of Decoding in WSJT-X with Audio Still Present

[Hasan al-Basri]

First of all, no, the cause is not clock error.

I have found the "proximate" cause, however, after weeks of hunting. I
worked with W9MDB and tested/considered many potential causes. I even
thought I had found it several times. In all those cases there was a
confounding variable, which I have now isolated. I have found the cure,
just not the cause, hence I'm posting this info here.

  I have been fighting this problem for weeks, and finally found a
*reproducible*  set of actions that cures the problem, immediately every
time! (until it recurs and then the same steps solve it)

In this discussion X means the 64 bit 2.01 version of WSJT-X, and JTA means
JTAlert. (earlier versions of both programs act the same way, since
installing the first 64 bit version of X. That may have been a coincidence,
(64 bit install), but what follows is not!

*I have observed 100%  correlation  between the problem and running both
programs involved listed below.* I am *not* assigning cause, but some sort
of interaction between the two programs has got to be the cause, as *doing
what I describe below restores decoding in X every time.*

What doesn't work:
Stopping X with button.
Closing X and restarting it.
Closing other running programs like Chrome, SDRC, etc

What has cured it every time:

* Shut down JTAlert*.

Proof:

*Every time I found X not decoding, but audio was still showing on the
thermometer and also showing on the waterfall*:

*I closed JTA and immediately on the very next sequence, X began decoding
again*. (On its own, I did no intervention with X at all)  *I could then
restart JTA and X would continue to decode for hours, if not days (2 or 3
max).* When it eventually stopped decoding again, a simple closing of JTA
restored X decoding at the next sequence.

So, the stoppages are random, going no more than a few days, *but the cure
is not*!

This has worked EVERY time since discovering the correlation between X and
JTA!

Prior to this, the only cure was to reboot the computer.

If you are having this problem, and also run JTA, try my solution.

I have no idea what the cause might be, but this correlation should give
the development team an idea where to look.

Win10 Home, 64 bit, AMD Quad Core

Also, this does not happen on every computer I have running copies of X and
JTA. Not every one of them is using JTA.

73, N0AN
Hasan
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel