The API is called when you are in the Configuration screen, but not when you are in the RX/TX screen.
>However, if I leave MultiPSK running, and then the idle timer kicks in to lock the screen, when I come back in after some period of time has passed, all things being equal, the output from MultiPSK is >now coming out on a different soundcard # (and not always the same “wrong” one each time):
The behavior that you described looks like as if Windows, for an unknown reason, stops the sound card in progress for another sound card. Curious.
De : email@example.com [mailto:firstname.lastname@example.org] De la part de Mark Bailey
OK, will try that. On the same point, would MultiPSK call that same Windows API call again on a Lock screen unlock, desktop restore/redisplay? What's odd is that this remapping seems to stick for as long as the screen is not locked. But I haven't tried to retest the sound card mapping across multiple consecutive idle->lock->unlock events.