I haven't had this happen in quite a while now.  But I've been keeping up
with the latest rev and am now on r5881.

Mike W9MDB

On Sun, Sep 27, 2015 at 3:20 AM, Dave Halbakken <dhalbak...@gmail.com>
wrote:

> Hello Mike or anyone else,
>
> Did you ever solve the Windows 10 problem you describe in the message
> below?
> I have the same thing happening quite randomly, and your
> change-the-soundcard fix makes things work again for me, too. I have turned
> off all sleep and power shutdown things related to my USB soundcard, so I
> don't think that is the issue. And, if it were the issue, the problem would
> be more predictable. WSJT-X worked fine under Windows 7 before the upgrade.
>
> Dave HS0ZLG WA0PND
>
>
> [wsjt-devel] Decoding stopped
> From: Michael Black <mdblack98@ya...> - 2014-12-01 13:25:59
>
> I'm running Windows 10, WSJT-X 1.5 r4693, and the hamlib integration fork
> rev 3477.  I have been keeping up with WSJT-X 1.5 changes pretty much daily
> with few exceptions.
> Also potentially relevant I'm using a signalink USB and an OMNI VII with my
> own omnivii.c driver.
>
> I always leave my system running overnight.
>
> For the first time ever came in this morning and there were no decodes on
> 40M for about the last 6 hours and the waterfall was not progressing.
>
> Everything on WSJT-X was operational.  Turning Monitor on/off had no
> effect.
> Went into File/Radio/Settings and did a "Test CAT" and it came back
> green...still no decoding though...so serial I/O to the Omni appears OK and
> not the problem.
> What fixed it was going into File/Settings/Radio and changing the Input
> over
> to my sound card and decoding started again.  Then back again to the
> Signalink and all is well.
>
> I've never had this happened before.  I just started using the hamlib
> integration fork but it doesn't appear to me that it was the problem or my
> Omni driver since the Signalink USB shouldn't be related to that.
>
> I've not tried debugging a running instance yet.  I assume it's just
> running
> gdb to attach to the process and then setting a break point on the decoding
> invocation to then trace why it's not progressing?
>
> Mike W9MDB
>
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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