And now my brain hurts, WSJT uses QT5 for interfacing with the audio subsystem, so it's a whole nother rathole to determine if there's an error check that'd tell you there's something wrong, or if there are bugs in QT, and the only current solution would be a 're-initialize audio' button.
73, Willie N1JBJ > On Jun 22, 2021, at 2:13 PM, William Smith <w_sm...@compusmiths.com> wrote: > > No, that would say it’s a different kind of device. > > This is something along the lines of changing a pointer to a device driver > instance. Changing any audio device, hitting OK, and changing it back fixes > it. > > 73, Willie N1JBJ > >> On Jun 22, 2021, at 1:38 PM, Alan <al...@alangroups.plus.com> wrote: >> >> >> Will it be the VID or PID data? >> >> Alan G0TLK, sent from my mobile device >> >>> On 22 June 2021 18:14:52 William Smith <w_sm...@compusmiths.com> wrote: >>> >>> In my WSJT-X.ini file, I've got: >>> >>> SoundInName=IC-7100_Rx (3- USB Audio CODEC ) >>> SoundOutName=IC-7100_TX (3- USB Audio CODEC ) >>> >>> I can't see anything changing with that device in Device Manager when it >>> stops working, so there's something else going on. >>> >>> Obviously there's a mapping from the text names above to some numeric >>> identifier, and that's the thing that changes whenever something disturbs >>> Windows. >>> >>> Durned if I can figure out what it is or if there's an easy way for WSJT to >>> figure out that it's changed. >>> >>> 73, Willie N1JBJ >>> >>>> On Jun 22, 2021, at 9:31 AM, Black Michael via wsjt-devel >>>> <wsjt-devel@lists.sourceforge.net> wrote: >>>> >>>> Seems like this should be fixable if the devices were enumerated just >>>> before opening the rig. >>>> >>>> Or put a "Refresh" button on the error dialog but the auto-enumeration >>>> would be better for any auto recovery. >>>> >>>> Mike W9MDB >>>> >>>> >>>> >>>> >>>> >>>> On Tuesday, June 22, 2021, 05:47:09 AM CDT, <al...@alangroups.plus.com> >>>> wrote: >>>> >>>> >>>> Could the code response to be that be if a USB identity cannot be found on >>>> a call to it then either a USB enumeration is done or if that's not >>>> possible (I don't know if that can be done from app code) then an error >>>> gets thrown? >>>> >>>> Just a thought so this kind of situation is handled gracefully? >>>> >>>> Alan G0TLK >>>>> On 22/06/2021 10:26, runninge...@gmail.com wrote: >>>>> Hi, >>>>> >>>>> This is an observation, not necessary a bug report, and as Bill pointed >>>>> out >>>>> in one of the groups.io threads : >>>>> >>>>> The root problem is that USB devices are "hot-pluggable" and adding or >>>>> removing a device, while the system is running, will cause all other >>>>> devices >>>>> to be re-enumerated, this can change device identities but Windows does >>>>> not >>>>> inform applications using them that they have been shuffled. >>>>> >>>>> 73's Erik. >>>>> ON4PB >>>>> >>>>> -----Original Message----- >>>>> From: >>>>> runninge...@gmail.com <runninge...@gmail.com> >>>>> >>>>> Sent: Tuesday, 22 June 2021 10:37 >>>>> To: >>>>> wsjt-devel@lists.sourceforge.net >>>>> >>>>> Subject: Re : Transmit audio dropouts >>>>> >>>>> Hi, >>>>> >>>>> I think I have a simple recipe to reproduce this problem : >>>>> >>>>> I have 4 WSTX instances connected to 4 slices on my Flex 6600M. All is >>>>> working fine. >>>>> My USB headset is connected to a USB port. >>>>> => Disconnect the headset and after that, PTT will work but no transmit >>>>> audio. Reconnecting the headset does not cure the problem, restarting >>>>> WSJTX >>>>> however does. >>>>> >>>>> Now, there are a couple of variants to reproduce the audio dropout : >>>>> - reconnecting the headset with working WSJTX instances >>>>> - doing the same on 4 WSJTX instances connected to SparkSDR. So, the Flex >>>>> is >>>>> not at fault. >>>>> >>>>> And lastly, sometimes it occurs that all 4 decode buttons remain active >>>>> blue. >>>>> >>>>> 73's Erik >>>>> ON4PB >>>>> >>>>> >>>>> ------------------------------ >>>>> >>>>> Message: 3 >>>>> Date: Sun, 20 Jun 2021 19:39:29 +0000 (UTC) >>>>> From: Louis Fiore >>>>> <mailto:ltfi...@aol.com> >>>>> >>>>> To: >>>>> "mailto:wsjt-devel@lists.sourceforge.net"; >>>>> >>>>> >>>>> <mailto:wsjt-devel@lists.sourceforge.net> >>>>> >>>>> Subject: [wsjt-devel] Transmit audio dropouts >>>>> Message-ID: >>>>> <mailto:385049449.2854162.1624217969...@mail.yahoo.com> >>>>> >>>>> Content-Type: text/plain; charset="utf-8" >>>>> >>>>> Good Afternoon, >>>>> >>>>> Running version 2.4.0. Out of the blue I?ve noticed a few instances with >>>>> my >>>>> Flex 6500 transmitter keying on but no audio is transmitted. It happens >>>>> randomly on both FT4 & FT8 about 10 to 20% of the time. Does anyone have >>>>> an >>>>> idea what may be causing this? >>>>> >>>>> 73, Lou W2LTF >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >> >> >> _______________________________________________ >> 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
