• 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: Testing a device for output
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Testing a device for output


  • Subject: Re: Testing a device for output
  • From: Jeff Moore <email@hidden>
  • Date: Fri, 18 Nov 2005 12:27:53 -0800

That's a totally reasonable way to do the job. One caveat is that devices are dynamic and their stream layout can change at any time. A device that doesn't have output now just possibly might have output later. The is most true of aggregate devices.

On Nov 18, 2005, at 11:12 AM, Art Gillespie wrote:

For my current requirements, I only need to enumerate devices that support output. In my first-pass implementation, I'm testing each of the enumerated devices returned by kAudioHardwarePropertyDevices for 'output support' by counting the number of outputs in the device's kAudioDevicePropertyStreamConfiguration (function implementation below). Is this the sanest way to go about it, or am I missing a simple mask or different property selector?


--

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
References: 
 >Testing a device for output (From: Art Gillespie <email@hidden>)

  • Prev by Date: Testing a device for output
  • Next by Date: Re: AudioFileGetPropertyInfo() on kAudioFilePropertyDataFormat returning 0?
  • Previous by thread: Testing a device for output
  • Next by thread: IAC Midi port 1 bug
  • Index(es):
    • Date
    • Thread