• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: AudioDeviceRead / HALOutputUnit
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AudioDeviceRead / HALOutputUnit


  • Subject: Re: AudioDeviceRead / HALOutputUnit
  • From: Jeff Moore <email@hidden>
  • Date: Wed, 14 Jan 2004 11:10:54 -0800

Yes, for two primary reasons:

First, the Output AU does all the hard work of being a proper HAL client. There are a lot of details involved with this for a general applications, so the work saved by doing it is immense, especially if you are already using the Output AU for other things.

Second, not every device supports AudioDeviceRead. Currently, the popular examples of devices that don't are Digi hardware and the iSight, and the future has more on the way.

Generally speaking, I recommend that everybody use the AUs rather than using the HAL directly.

On Jan 14, 2004, at 7:25 AM, Chandrasekhar Ramakrishnan wrote:

If one already has code that uses AudioDeviceRead to get audio input
that you feed into an AU graph, is there any reason to switch to the
HALOutputUnit input capabilities?

--

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.

References: 
 >AudioDeviceRead / HALOutputUnit (From: Chandrasekhar Ramakrishnan <email@hidden>)

  • Prev by Date: Re: Input AudioUnit?
  • Next by Date: Re: Input AudioUnit?
  • Previous by thread: AudioDeviceRead / HALOutputUnit
  • Next by thread: Re: stuck on audio streams
  • Index(es):
    • Date
    • Thread