Re: Third Party Audio Hardware
Re: Third Party Audio Hardware
- Subject: Re: Third Party Audio Hardware
- From: William Stewart <email@hidden>
- Date: Mon, 12 Jan 2004 15:48:33 -0800
Yes
On 12/01/2004, at 1:13 PM, Daniel Todd Currie wrote:
So the best I can do is to have support for CoreAudio devices, as I
have already done? (simple yes/no will suffice)
// D
On 2004 Jan 12, at 12:34, Jeff Moore wrote:
James comment is a little extreme. The way I understand it is this:
1) The Digi hardware only allows for one process to use it at a time.
2) Digi's HAL plug-in has a list of apps it allows itself to run in.
The reason for this is to allow apps that only work with the default
device (QT, iTunes, etc) to use the hardware but to disallow certain
long-lived processes like LoginWindow from accidentally monopolize
the device.
3) There's an app or control panel somewhere in the Digi software
install that allows for editing this list.
While Digi's driver is the only one I know of that has an access
control list like this, there are other examples of devices that only
work with one process at a time; the chief example being the iSight.
On Jan 12, 2004, at 10:59 AM, James Coker wrote:
The digidesign drivers are a special case -- Digi doesn't want
anyone's
apps but their own talking to their hardware, very disappointing.
Search
for "digi" in the list archives for all the details. All other
hardware interfaces
w/ CoreAudio drivers should show up just fine. Your code looks
fine. Also
see Bill Stewart's posts on the HALOutputUnit for details on using
that AU
for device output (they're dated Jan 9th).
Jim
On Jan 12, 2004, at 1:11 AM, Daniel Todd Currie wrote:
I'm trying to support as much audio input hardware as possible with
my application, and I guess I just don't know the limitations of
the HAL... I try the following bit of code to get a device count,
and some things show up (MOTU 828) and others don't (Digi 001).
The Digi 001 does show up in system preferences, however.
Should I expect
AudioHardwareGetProperty(kAudioHardwarePropertyDevices, ...) to
return all of the devices I ought to support? Does my inability to
list the Digi 001 stem from uncertain manufacturer support for
Panther? What other ways are there to get a list of audio devices?
How does System Preferences find the Digi 001? Will I need to
support some of these devices directly somehow, as opposed to
universal support through an API like CoreAudio that I assumed
would manage all of the accessible devices? Is support for the
plethora of audio devices available on the market perhaps out of
reach for a freeware hobbyist like myself?
Answers to any of these questions would be a great deal of help,
thanks.
// Daniel Currie
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
--
Jeff Moore
Core Audio
Apple
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________
__
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________
__
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.