Re: Capturing currently played audio using CoreAudio on Mac
Re: Capturing currently played audio using CoreAudio on Mac
- Subject: Re: Capturing currently played audio using CoreAudio on Mac
- From: Jeff Moore <email@hidden>
- Date: Mon, 19 Apr 2010 12:34:30 -0700
The kAudioHardwarePropertyDevices notification isn't in your hands. That's what the HAL sends whenever a new device shows up on the system or an existing device goes away. So, if the JACK plug-in is making a device appear or disappear during some operation, then this notification is going to be seen by all processes.
It is probably a bug in the app if its playback glitches when a device not being used appears or disappears.
On Apr 19, 2010, at 12:19 PM, Stéphane Letz wrote:
>
>>
>>> Ah, you're interacting JACK as a CoreAudio device. Sorry, out of my
>>> area of expertise. I was describing JACK's interactions with
>>> JACK-native clients. I don't know much about the story it presents to
>>> apps that want to treat it like a regular CoreAudio device.
>>
>> I thought that was the whole idea! Anyway, I will report the fact that our app is left hanging when you shut down the JACK server to the JACK folks, but judging by the warning message they currently display, they've already given up on that one.
>>
>
> One thing about this specific point : JackRouter device triggers a "kAudioHardwarePropertyDevices" property when the JACK server appear or disappear. It seems this is enough for iTunes or GareBand to properly detect something and adapt : iTunes switches on default device and GarageBand display an alert. I don't know if "kAudioDevicePropertyDeviceIsAlive" property would have to be triggered also.
>
> Jeff what is the proper way to behave?
>
> Best Regards
>
> Stephane Letz
--
Jeff Moore
Core Audio
Apple
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden