On Sat, Jan 15, 2022 at 11:17:58PM -0800, Paul Kube via wsjt-devel wrote: > On Fri, Jan 7, 2022 at 1:25 AM Fons Adriaensen via wsjt-devel > > > So does this mean that when a new audio device becomes available > > while a music app is playing some file, the output from that > > app would be redirected to some other device ? > > > > No, rather it seems to be a result of what happens when an audio device in > use becomes unavailable. For example, headphones get unplugged, or an HDMI > monitor goes into sleep mode, etc. Then it kind of makes sense that Windows > would try to find another device that applications can use. Of course, it > does this badly, not always correctly restoring connections when the device > becomes available again.
But in this case the audio interface is used to transfer signals to/from the rig, so why should it ever become 'unavailable' during operation ? > Isn't the real issue here that WSJT is opening and closing the audio > > devices again and again for each RX or TX cycle ? > > I don't think so; have you looked at the source code, or traced audio > subsystem calls? :-) I'm not a WSJT dev, so just finding all the right places in the huge code base in order to answer that question with any degree of certainty would probably take a very long time... But surely the devs should know how they are using the audio interface. If they are indeed opening and closing the audio device in each cycle then I'm pretty sure that is the source of the problem. Ciao, -- FA _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
