Re: Stereo panning with the HAL
Re: Stereo panning with the HAL
- Subject: Re: Stereo panning with the HAL
- From: "Mikael Hakman" <email@hidden>
- Date: Thu, 8 May 2008 00:34:38 +0200
- Organization: Datakonsulten AB
I don't know how rare these exceptions are, but in the world I live in, we
don't develop applications that do what other, already available
applications do very well. We develop applications and utilities that make
it easier for people to use what's already there, and for some groups of
users make the Mac OS X an attractive environment. These applications must
therefore function on a global, shared level.
For example, when developing alternative means for controlling volume (such
as IR, RF, USB, and even TCP/IP) our application controls the volume on
behalf of the users, and as a direct response to increase/decrease commands
given by the users. Therefore such an application needs to control the
volume for each and all other application running on the Mac OS X, even
those not written yet.
Another and more advanced application, of which the above volume control is
a part, is an utility that allows the users to, depending on the task at
hand, switch among a number of predefined input/output environments (audio
devices, display devices, hardware-based filters and effects, and more) at a
single press of a button, not necessarily on the keyboard or mouse, not even
in the immediate vicinity of the computer. The less the users have to focus
on the mechanics of computer control and logic of what devices to turn on
and off and how and in which sequence, the more they can focus on their
actual work or entertainment task. In some environments and for some groups
of users you cannot even separate work from entertainment - lucky them!
On May 07, 2008 8:43 PM, Jeff Moore wrote:
Finally, I have to give my standard speech about shared settings like
hardware volume. Apps should not, in general, be messing about with these
sorts of things. They belong to the user and often are configured
specifically the way the user wants them. Apps that come along and think
they know better than the user often end up causing more problems than
they solve. For nearly all applications out there, the right thing to do
is to handle your volume, panning, etc. in your own mix engine and leave
the shared settings alone. Obviously there are exceptions to every rule,
but please keep this in mind when thinking about your application.
On May 7, 2008, at 11:18 AM, Andrew MacDonald wrote:
This leads to an additional question: is there a way to detect if
something is plugged into the output jack? I tried
kAudioDevicePropertyJackIsConnected, but it also isn't recognized by the
built-in output.
_______________________________________________
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