Have you disabled USB selective suspend when on power?
That's in the advanced power settings.
Mike W9MDB

On Wed, Sep 30, 2015 at 3:00 AM, Dave Halbakken <dhalbak...@gmail.com>
wrote:

> Thanks for your comments, both Laurie and Bill. I am quite satisfied that
> one of the power settings available in Win 10 Control Panel is not the
> problem. I have scoured (several times) every device I can find that has a
> power setting and made sure that nothing gets turned off.
>
> That is not to say that there might be something else peculiar about what
> Win 10 is doing.
>
> Also, I have opened the control panel (which gets installed with the driver
> and which always has an icon sitting in the system tray) for my USB audio
> card almost immediately after experiencing the problem with WSJT-X and
> watched the input VU meter bouncing just above its lowest level, meaning
> that, it was seeing the output of my radio. That tells me that the USB port
> has not been shut down by the system.
>
> Bill, I understand your hesitance add a recovery feature for audio cards,
> but such a feature might be similar to the way some OS's display a
> notification that a network cable has been unplugged. As soon as you plug
> the network cable in again, the OS recovers gracefully and even grabs a new
> dynamic IP address if necessary with no further user intervention. Seems
> pretty simple from a user's standpoint, though I don’t know how difficult
> it
> might be to code in WSJT-X.
>
> I also understand your hesitance because only Mike and I have reported this
> problem, as far as I know. But there may be folks experiencing it without
> commenting.
>
> 73
>
> Dave HS0ZLG WA0PND
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 29 Sep 2015 11:46:35 +1000
> From: "Laurie, VK3AMA" <vk3ama.ham.a...@gmail.com>
> Subject: Re: [wsjt-devel] Decoding stopped
> To: WSJT software development <wsjt-devel@lists.sourceforge.net>
> Message-ID: <5609ed7b.30...@vkdxer.com>
> Content-Type: text/plain; charset="windows-1252"
>
> Dave,
>
> This suggests that you still have your USB port going to sleep. You need
> to check the Power Management settings of the USB soundcard and also the
> Power Management settings of the USP Root Hub to which the soundcard is
> connected.
>
> de Laurie VK3AMA
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 2
> Date: Tue, 29 Sep 2015 09:58:36 +0100
> From: Bill Somerville <g4...@classdesign.com>
> Subject: Re: [wsjt-devel] Decoding stopped
> To: wsjt-devel@lists.sourceforge.net
> Message-ID: <560a52bc.2040...@classdesign.com>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 29/09/2015 02:18, Dave Halbakken wrote:
> Hi Dave,
> > Thanks for your reply, Mike.
> >
> > I found that this problem can be reproduced by unplugging and re-plugging
> > the USB cable to my soundcard. To get WSJT-X fully working again you have
> > to
> > swap the soundcard settings away and back on both input and output audio.
> > Perhaps a dirty USB cable contact was the cause in my case.
> The symptoms you have described are best explained by a USB audio device
> disappearing for some reason. The most likely cause of that is some
> operating system driven partial shut down in my experience. I know you
> have checked that the USB hub sleep settings have been disabled but I do
> not know the full details of the Windows 10 changes in that area.
> >
> > But that brings up a feature request: please make recovery from the
> > temporary disconnection of a soundcard both graceful and automatic if
> > possible.
> That is not straightforward. Maintaining a setting of a USB audio device
> that has been removed from the system is leaving the application with an
> invalid configuration. Currently we do support USB audio devices being
> removed while the application is not running; so long as they are
> restored before the application is restarted.
>
> IMHO supporting non-existent devices will lead to far more user issues
> than the current arrangement.
>
> Running WSJT-X for extended periods of time while the system is liable
> to initiate a power saving strategy, cannot be supported unless that
> power saving strategy does not impact the resources being used by WSJT-X.
> >
> > 73
> >
> > Dave HS0ZLG WA0PND
> 73
> Bill
> G4WJS.
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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