Hi Uwe,
I can understand that the AudioDeviceInfo for the AudioInput or AudioOutput can become invalid within WSJTX but wouldn't a fresh QAudioDeviceInfo::availableDevices find it back ? Note that the soundcard with its explicit name (f.e. "USB Audio CODEC") is not gone but the device info is gone or the device list is now incorrect. I have observed this in two situations which are easily reproducible on my end : * When you connect or disconnect a PNP device (or it goes to sleep ..), a HDMI monitor (with sound) goes on or off * At a remote station, when one connects or disconnects with Windows remote desktop. Again, and this is only for Windows, my suggestion would be to lock the audio on its explicit device name, and do a fresh search if the device is lost. My apologies if I have it all wrong . 73's Erik ON4PB From: DG2YCB <dg2...@gmx.de> Sent: Monday, 28 April 2025 19:35 To: WSJT software development <wsjt-devel@lists.sourceforge.net> Cc: Erik Icket <runninge...@gmail.com> Subject: Re: [wsjt-devel] Subject: Feature request: Output audio device selection Erik, Locking anything in our program doesn't help when this device is no longer available on OS level. You would then only see something like "... (not found)". 73 de DG2YCB, Uwe _________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de <mailto:dg2...@gmx.de> Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB> Am 28. April 2025 13:45:54 schrieb Erik Icket via wsjt-devel <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> >: May I suggest a different feature update to the audio / soundcard / input - output device selection logic ? What about the ability to lock the selection for the input / output soundcard ? This to prevent WSJTX losing the sound device : - whenever Windows re-assigns / re-enumerates the devices after a USB PNP device update - or worse, whenever you connect to a remote desktop where WSJTX is running. Once the audio devices are locked in the settings panel, and would be lost, WSJTX could go into a retry cycle to recover the devices ... Any thoughts ? 73's Erik ON4PB ------------------------------ Message: 3 Date: Mon, 28 Apr 2025 12:34:31 +0200 From: "Uwe, DG2YCB" <dg2...@gmx.de <mailto:dg2...@gmx.de> > To: WSJT software development <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > Subject: Re: [wsjt-devel] Subject: Feature request: Output audio device selection for alert sounds Message-ID: <18f8ab9d-a70a-4a11-a70a-ce6e50d5b...@gmx.de <mailto:18f8ab9d-a70a-4a11-a70a-ce6e50d5b...@gmx.de> > Content-Type: text/plain; charset="utf-8"; Format="flowed" Bonjour Olivier, Thanks for your suggestion. I would just like to briefly explain why we have not done this so far. Firstly: A second sound card selection menu would not solve the fact that alerts can only be played if you have at least 2 sound cards on your PC. Secondly, something like this would only make things more complicated. Because then it would have to be programmed in such a way that the settings in both are mutually exclusive. Imagine Windows resetting all sound card numbering after a Windows update (or after you have plugged in a new USB audio device). This would then cause quite a mess, because you have to correct two sets of settings which are dependent of each other. Thirdly: Honestly, many OMs don't really understand these technical details one way or another. That's why the alerts are switched off by default. This means that those OMs who have never heard of an Audio Alerts feature and have never reached the Alerts tab in Settings will find the Soundcard menu in Settings/Audio exactly as it has always been. However, we have now explained the correct audio settings in more detail in the User Guide for the upcoming ?250501? update. It will be released on Thursday. Allow me one general comment: My recommendation is that Windows users who also use JTAlert should use the audio alerts from JTAlert, because JTAlert does this best. The Alerts feature in WSJT-X Improved was primarily developed for Linux and macOS, because JTAlert is only available for Windows, and for those OMs who do not use JTAlert. 73 de DG2YCB, Uwe ________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de <mailto:dg2...@gmx.de> Info: www.qrz.com/db/DG2YCB <http://www.qrz.com/db/DG2YCB> _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto: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
