• 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: Another question about output routing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Another question about output routing


  • Subject: Re: Another question about output routing
  • From: William Stewart <email@hidden>
  • Date: Tue, 14 Mar 2006 11:24:53 -0800


On 14/03/2006, at 8:17 AM, Chandrasekhar Ramakrishnan wrote:

Rick Cohen schrieb:
If I want to leave the default output connected to one hardware
interface and have my app sending audio to a different interface, which
output AU should I connect to? Generic, HAL, or something else? Are
these output AUs already connected to some hardware interface?


What parameters do I need to set up? Buffers, sample rate, channels,
etc.? The default output AU seems to work very well with minimal setup.

Use the HALOutput and set the kAudioOutputUnitProperty_CurrentDevice to the audioDeviceID of the device you want to use. Otherwise set up is the same as with the default output.

What if my user chooses the same hardware interface that is currently
connected to the default output AU.  In that case should I silently
connect to the default AU?

In my software I still use the HAL output. This means that even if the default output gets changed to a different device, my app stays connected to the old device. But if you wanted your software to behave differently, you can use the default AU.

The main difference is essentially the level at which you want to interact with the user. If you don't want to have any UI in your app to allow the user to set a particular device (for example, a game, QT Player, iTunes don't generally want to have to deal with this), then the system pref support the ability to choose a device as the default output. Your app can use this too by using this AU.


On the other hand, if you want to provide a UI to manage device selection, etc, then the AUHAL and the device selection property are the way to go...

Underneath all of this, the code running is essentially the same, just some minor differences which Sekhar describes above (the default AU will track changes that the user makes)

BIll


- sekhar

--
C. Ramakrishnan        email@hidden
 _______________________________________________
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

--
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
________________________________________________________________________ __


_______________________________________________
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


References: 
 >Re: Another question about output routing (From: Chandrasekhar Ramakrishnan <email@hidden>)

  • Prev by Date: Re: AudioConverter MP3 decode questions
  • Next by Date: Re: AudioConverter MP3 decode questions
  • Previous by thread: Re: Another question about output routing
  • Next by thread: PlayThrough settings
  • Index(es):
    • Date
    • Thread