• 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: Multiple data sources and kAudioStreamPropertyTerminalType
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multiple data sources and kAudioStreamPropertyTerminalType


  • Subject: Re: Multiple data sources and kAudioStreamPropertyTerminalType
  • From: Edward Peterlin <email@hidden>
  • Date: Fri, 8 Apr 2005 16:52:16 -0700

You might provide some feedback in the GUI about what the driver for each device says about it's terminal type to help guide the user when picking. But I would definitely let the user choose since they should know which devices they have that meet your app's criteria. That will allow your app to work with the largest set of devices possible.

I definitely hear that...the difference is in our case that we're selling a hardware+software combo and the hardware's physical connector is either a miniplug or RCA style line in. I'm already displaying a list to the user but was using the terminal type to filter out sources that our hardware obviously couldn't be connected to (e.g. internal microphone, digital input, etc.). We're writing an educational product for children and have been trying to keep the setup as simple as possible. We leave the drivers that report generic types or return unsupported errors in the list to to be safe.


I'm waiting for successful property change notifications on the audio device but after switching to the external Line-In data source the terminal type on the albook is still indicating INPUT_MICROPHONE...but I know it's not the microphone since the actual audio data on the stream is coming from the line in jack. I had expected the terminal type to be EXTERNAL_ANALOG_CONNECTOR or perhaps EXTERNAL_LINE_CONNECTOR like the G5 tower builtin audio device.

I'll go ahead and whittle down a test case for the albook to put in bug reporter. In the meantime I'll try to sneak that device back in based upon comparing it by name. It doesn't appear the data source name returned by the DataSourceNameForIDCFString property is being changed with the system-preferred language (10.3.8).

thanks for the help,
Edward Peterlin
BIOPAC Systems, Inc.


_______________________________________________ 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: 
 >Multiple data sources and kAudioStreamPropertyTerminalType (From: Edward Peterlin <email@hidden>)
 >Re: Multiple data sources and kAudioStreamPropertyTerminalType (From: Jeff Moore <email@hidden>)
 >Re: Multiple data sources and kAudioStreamPropertyTerminalType (From: Jeff Moore <email@hidden>)

  • Prev by Date: Re: Multiple data sources and kAudioStreamPropertyTerminalType
  • Next by Date: Re: The AU header problem, but a little different (addendum) (Gewijzigd door Toine Heuvelmans)
  • Previous by thread: Re: Multiple data sources and kAudioStreamPropertyTerminalType
  • Next by thread: SuperCollider research project
  • Index(es):
    • Date
    • Thread