Re: How to make my AU graph the default output?
Re: How to make my AU graph the default output?
- Subject: Re: How to make my AU graph the default output?
- From: Ondřej Čada <email@hidden>
- Date: Sun, 29 Mar 2009 01:58:52 +0100
Brian,
On Mar 29, 2009, at 12:50 AM, Brian Willoughby wrote:
...
... I still can't get the reasons why there is no "default output
AU" to be put in the graph: seems to me as clean solution as
possible... well, never mind :)
There is a "default output AU" but it only deals with audio from the
current application.
Is there? Pray tell me where to found the thing.
That's exactly what I needed; the inter-application approach is an
ugly hack which I am forced to use by only one thing: that the
"default output AU" inside an application scope does not exist (far as
I and those who answered before know).
What you're asking for is the ability to direct audio between
applications, because you're leveraging applications that you did
not write yourself.
Neither.
All I am asking for is the ability to leverage the audio of _one_
application, and do it inside the _one_ application as this
application's internal thing.
If the fact the application offers a plug-in API confuses you, well,
forget it, and consider the simplest case possible: a trivial
QuickTime-based player. Or, probably even simpler thing: consider a
very plain reader, which has only one text field in its GUI; whichever
the user writes into the field is read out through
NSSpeechSynthesizer. I estimate twenty-odd source lines needed to do
that.
Now suppose any of these extremely simple applications needs sound
output improvement -- a completely internal sound improvement, which
would be encapsulated in the application itself, of course. Suppose
it's such an improvement which can be very naturally and easily done
by a chain of a few CA units. For example, we might want to create an
illusion the "reader" strolls left and right, by moving the
synthesized speech gradually between the L/R stereo output channels.
How one does that with CA? Especially, how one does that without
resorting to KEXT-based inter-application ugly solutions?
... I get the impression that you are repacking existing
applications, and you want a simple tool that will allow you to add
surround features to programs that you did not write yourself. This
seems to me to be well outside the scope of CoreAudio. There are
tools out there that would make your job easier, but the real
solution would be for your company to develop your own modern
software that you have full control over.
Now this is quite ludicrous. Let me please know when Apple "develops
their own modern software that they have full control over" -- in
other words, when it makes iPhone OS X (or perhaps even Mac OS X!) a
completely closed environment, writing all the applications themselves
without allowing 3rd parties to!
Thanks and best,
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
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