Re: Curious happening with CAPlayThough
Re: Curious happening with CAPlayThough
- Subject: Re: Curious happening with CAPlayThough
- From: "tahome izwah" <email@hidden>
- Date: Mon, 12 Jan 2009 07:52:52 +0100
2009/1/9 Jeff Moore <email@hidden>:
> It is admirable that you are trying to cobble together something using our
> sample code.
I'm not sure if his attempt would qualify as "admirable"
("unenviable" would probably be a better word) but from my experience
with Apple code (like the Cocoa AudioUnit templates that were broken
for a couple of releases) it sure can be quite a challenge at times.
I'm curious: do you have any other recommendation on where to
start looking for information on writing a working audio reflector
kext for MacOS X? Because if you do I'm all ears. We need that
functionality in our product as well, and as far as I know the Apple
example code is all there is and MacOS X makes it *really* difficult
to capture system audio. In fact, on any other operating system this
is much easier than it is on the Mac. And as we all know the Apple
documentation isn't really much help to get anything productive done
either, so if you have in fact some other source for information I'm
sure you'll have our full attention.
> But I think you misunderstand the concept of sample code here.
> The goal of sample code is usually not to deliver a finished, working bundle
> of code. The goal is to deliver a bundle of code that illustrates the
> concepts of the APIs it uses. The fact that the code actually does something
> useful is always a welcome and happy side effect.
LOL! Now that's an interesting take on cobbling together some
sources to ship it as sample code... but looking at the quality of the
documentation it seems that Apple is at least consistent about it...
:->
--th
_______________________________________________
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