Re: Curious happening with CAPlayThough
Re: Curious happening with CAPlayThough
- Subject: Re: Curious happening with CAPlayThough
- From: Stephan M.Bernsee <email@hidden>
- Date: Sat, 10 Jan 2009 12:24:26 +0100
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.
So you're saying that for instance the ExtAudioFile examples create
valid audio files only as a welcome and happy side effect? I don't
think that it could be the motivation behind any example project to
create things that don't really work.
But anyways, the Apple sample code is pretty much all there is
especially when it comes to capturing system audio so having an
example that actually worked as intended would be great (what good is
an "AudioReflector" that doesn't work for reflecting system audio?
Maybe the name is misleading then, too).
A separate project could do the trick, so the extra logic doesn't
clutter the code too much (I'm 100% with you on that, btw. Examples
should be clean and easy to read - but they should also work for what
they were designed to demonstrate).
I'm sorry that the AudioRefelctorDriver and CAPlayThrough are giving
you fits when you try to cobble them together. I'm pretty sure though
that the core problem is the problem that I was referring to earlier.
Ok we'll look into the scheduling problem in more detail then.
Thanks again for all your help!
Stephan
_______________________________________________
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