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 <mdblac...@yahoo.com> 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 recording....perhaps 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 <dg2...@gmx.de> 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
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to