Re: kAudioDevicePropertyStreamFormat error on Tiger
Re: kAudioDevicePropertyStreamFormat error on Tiger
- Subject: Re: kAudioDevicePropertyStreamFormat error on Tiger
- From: Jeff Moore <email@hidden>
- Date: Wed, 16 Nov 2005 14:23:16 -0800
On Nov 16, 2005, at 12:50 PM, Dominic Feira wrote:
With all due respect to whomever wrote AMS, it sucks. Not because
it can't do things, but because most consumers don't have a clue
about using it or even that it exists. AMS really is designed with
audiophiles in mind. It seems to me that device settings would be
a better fit in the System Preferences than tucked away.
Not being a UI guy, I'll just say that reasonable people can disagree.
I wouldn't be surprised if most consumers never even ventured into
their Utilities folder.
There's no need for them to do so since your app can launch AMS for
them with a few lines of code. This is one of the reasons why
kAudioDevicePropertyConfigurationApplication exists.
For an example of this, just look in HALLab's code. In the file,
HLDeviceWindowInfoController.mm, the method -
LaunchConfigAppButtonAction: is called when the user hits the
"Launch" button in the device info window. It gets the bundle ID from
the HAL and then uses Launch Services to launch the app with that
bundle ID.
The reason that I change the settings of the device myself is so
that I can ensure that decent quality input is coming into my app.
Before doing this, I can't tell you how many times I heard,
"Everything works fine the but quality isn't that great." Of
course, their settings in AMS were wrong, but the blame wasn't
assigned appropriately.
IMHO, it is troublesome for random applications to slam hardware
settings. The app is pretty much never in a position to know what the
right thing to do for the system as a whole, especially in multi-user
scenarios. Worse, most apps that slam settings assume that they're
the only ones that matter and then do whatever they want no matter
what the results are in other apps. This is never a good thing.
It is much better to leave this kind of operation to the typical
control panel applications like AMS. Plus, it's less code you, the
developer, have to write and maintain in your app. Honestly, I see it
as a win-win situation all around. Your app requires less code and
the user gets a consistent UI for adjusting hardware settings,
regardless of the app. Plus, it engages the user to think a tiny bit
about what the right thing to do is. All good things, in my book.
I'll have to make appropriate changes now that I realize
kAudioDevicePropertyStreamFormatMatch is "deprecated". Thanks for
such a quick response. The CA team rocks.
No worries. Happy to help.
--
Jeff Moore
Core Audio
Apple
_______________________________________________
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