Hi Ed, Thanks a lot for the info. As it is a virtual driver for RAVENNA/AES67 audio protocol, I think there is some chance to make CoreAudio thinks number of channels has changed. Hopefully this will not generate too many side effects…
Bertrand From: Ed Wynne <[email protected]> Sent: Thursday, April 15, 2021 7:23 PM To: Bertrand Van Kempen <[email protected]> Cc: [email protected]; [email protected] Subject: Re: kAudioObjectPropertyElementName notification from plugins ignored by HAL/Applications On Apr 15, 2021, at 2:15 AM, Bertrand Van Kempen <[email protected]<mailto:[email protected]>> wrote: Do you know which others notifications I could use to "force" the Application/HAL to ask again channels' name? Otherwise I'll have to inform users to relaunch the application by itself ;( Unfortunately, this behavior is entirely voluntary and worse, a bit hard to discover. So it has been my experience, over the past decade or so, that almost no applications actually do it. The only sure fire work around that I know of is to either make the channels in question, or the entire device, go away and come back. Unfortunately, if this isn’t a virtual device you control, that is pretty hard to do outside of whacking coreaudiod… and I really don’t recommend that, as it both requires admin privileges and causes other issues. -Ed
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
