Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Observing changes to kAudioDevicePropertyDataSources

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Observing changes to kAudioDevicePropertyDataSources

Subject: Observing changes to kAudioDevicePropertyDataSources
From: Daniel Kennett <email@hidden>
Date: Fri, 16 Nov 2012 15:54:41 +0100

Hi (again) guys,

I'm using kAudioDevicePropertyDataSources to get the data sources of an AudioDeviceID, then AudioValueTranslation to get the name of that data source.

This is so I can see the actual device names (Internal Speakers instead of Built-in, DELL U3011 instead of DisplayPort, etc), as well as getting AirPort device names for display in my UI.

However, I can't seem to find out how to observe changes to those names:

1) When "Internal Speakers" changes to "Headphones", is it actually a new source?

2) How about when an AirPlay device's name changes?

3) Either way, how do I observe these changes?

Thanks again for your help.

--
Daniel Kennett
Platform Programmer
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

Prev by Date: Re: kAudioOutputUnitProperty_CurrentDevice not sticking (Mac)
Next by Date: Multi-input audio unit - inBuffer.mNumberBuffers is always 2?
Previous by thread: CoreMIDIServer framework SDK
Next by thread: Multi-input audio unit - inBuffer.mNumberBuffers is always 2?
Index(es):
- Date
- Thread