Could there be a Windows Event that could be picked up using Task
Scheduler and a warning run?
Alan G0TLK
On 27/05/2020 21:26, Bill Somerville wrote:
On 27/05/2020 21:16, [email protected] wrote:
Dear developers,
Looking at some of the recent “audio in problem“ posts, would it make
sense to raise audio input streaming errors to the GUI ? Maybe some
visual hint (f.e. a red decode button) or an error dialog ?
I can easily reproduce a situation on Win10-64 bit, where 8 running
WSJT-X instances (of which one is WSPR) will halt the WSPR decoding
and this without saving .wav files (although “Save decoded” is
selected).
More particularly, maybe catching these errors in Soundin.cpp and
bring them to the foreground ?
case QAudio::OpenError:
Q_EMIT error (tr ("An error opening the audio input device
has occurred."));
break;
case QAudio::IOError:
Q_EMIT error (tr ("An error occurred during read from the
audio input device."));
break;
case QAudio::UnderrunError:
Q_EMIT error (tr ("Audio data not being fed to the audio
input device fast enough."));
break;
case QAudio::FatalError:
Q_EMIT error (tr ("Non-recoverable error, audio input
device not usable at this time."));
break;
Thanks for considering and 73’s,
Erik
ON4PB
Hi Erik,
those errors do go to the user, but they don't happen when Windows
reassigns the audio device, we get no notification.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
