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: Paul Davis <email@hidden>
- Date: Mon, 19 Apr 2010 13:36:46 -0400
On Mon, Apr 19, 2010 at 1:04 PM, Paul Sanders
<email@hidden> 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!
Not really. The idea behind JACK was to facilitate a single, high
level, low-latency-friendly API for routing audio no matter where it
originated or was being sent (applications, audio h/w, the network).
However, since so few developers on OS X seem willing to use a
cross-platform API for audio, and partly because it turned out to be
possible, Stephane figured out how to make JACK look like a CoreAudio
device so that existing CA apps could interact with a JACK "graph"
(the JACK server and all of its clients) without any modifications.
This is both a blessing and a curse: just about every CA app can work
with JACK, which is pretty cool. But it also means that just about no
OS X developers have much interest in making their apps "JACK native",
despite the other benefits that this could offer (particularly shared
transport control, which CoreAudio currently has no concept of).
Them's the breaks, I suppose.
--p
_______________________________________________
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