• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Capturing currently played audio using CoreAudio on Mac
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Capturing currently played audio using CoreAudio on Mac


  • Subject: Re: Capturing currently played audio using CoreAudio on Mac
  • From: "Paul Sanders" <email@hidden>
  • Date: Mon, 19 Apr 2010 19:08:25 +0100

> 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.

Thank you.  I am educated.  I might have used it myself, had I known about it.  Core Audio could certainly use a higher level API.  OTOH, I like to minimise external dependencies.
 
As it was, I learned a lot from MTCoreAudio and from the 'school of hard knocks'.  I found it hard work getting to grips with Core Audio, not least because the documentation is so dense.  I found out the hard way, for example, that one has to handle at the application level the fact that some devices interleave channel data and some don't (and some - specifically the Motu 828 - do a bit of both).  Some kind of primer is badly needed and I didn't really find what I was looking for in the Core Audio SDK.  But I've said most of this before so I'll shut up.
 
Nice talking to you.  Good luck with whatever you are up to these days.
 
Paul Sanders.
 
 _______________________________________________
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

References: 
 >Capturing currently played audio using CoreAudio on Mac (From: Aron Homberg <email@hidden>)
 >Re: Capturing currently played audio using CoreAudio on Mac (From: Paul Davis <email@hidden>)
 >Re: Capturing currently played audio using CoreAudio on Mac (From: "Paul Sanders" <email@hidden>)
 >Re: Capturing currently played audio using CoreAudio on Mac (From: "Paul Sanders" <email@hidden>)
 >Re: Capturing currently played audio using CoreAudio on Mac (From: "Paul Sanders" <email@hidden>)
 >Re: Capturing currently played audio using CoreAudio on Mac (From: Paul Davis <email@hidden>)
 >Re: Capturing currently played audio using CoreAudio on Mac (From: "Paul Sanders" <email@hidden>)
 >Re: Capturing currently played audio using CoreAudio on Mac (From: Paul Davis <email@hidden>)
 >Re: Capturing currently played audio using CoreAudio on Mac (From: "Paul Sanders" <email@hidden>)
 >Re: Capturing currently played audio using CoreAudio on Mac (From: Paul Davis <email@hidden>)

  • Prev by Date: Re: CFRelease issue with preset names
  • Next by Date: Re: Capturing currently played audio using CoreAudio on Mac
  • Previous by thread: Re: Capturing currently played audio using CoreAudio on Mac
  • Next by thread: Re: Capturing currently played audio using CoreAudio on Mac
  • Index(es):
    • Date
    • Thread