• 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
Bug in CA kAudioDevicePropertyDataSourceNameForIDCFString?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bug in CA kAudioDevicePropertyDataSourceNameForIDCFString?


  • Subject: Bug in CA kAudioDevicePropertyDataSourceNameForIDCFString?
  • From: Ulrich David <email@hidden>
  • Date: Fri, 2 Mar 2007 01:32:47 +0100

Hi everyone,

I have a small app which get all avaible audio devices and sources and put it in menus. I used HALLab for example to write the code, but in objective-c++ instead of cpp.
I use this app for 2 years now and all works well (on PowerPC).


I recently get a MacPro and I notice that I have trouble with getting kAudioDevicePropertyDataSourceNameForIDCFString after changing a source.

I have listener in my app. When data source or device property change, I update my menus (rebuilding them from scratch with a complete discover of device and source).
The first load of app build a complete menu without error. But when I change source, for example I put my headphone on front panel of MacPro) the data source name given by


AudioDeviceGetProperty(inDeviceID,
inChannel,
dataSourceIsInput,
kAudioDevicePropertyDataSourceNameForIDCFString,
&theSize,
&theTranslation);


is nul !!
I got an OSStatus error : 1852797029 -> ('nope')

It's very strange because I use the same function at the start of the app which return me a valid name. When the datasource change I destroy and re-create a full new object handling the property of device and attached datasources...

I don't have this problem on HALLab. I control the device ID, data source ID, channel, sizeof AudioValueTranslation between the two app and they are exactly the same when the problem occurs.

I don't know what to do now. Have someone an idea?

Thx

David
_______________________________________________
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


  • Follow-Ups:
    • Re: Bug in CA kAudioDevicePropertyDataSourceNameForIDCFString?
      • From: Jeff Moore <email@hidden>
  • Prev by Date: Can Audio Units be MIDI processors?
  • Next by Date: Re: Bug in CA kAudioDevicePropertyDataSourceNameForIDCFString?
  • Previous by thread: Re: Can Audio Units be MIDI processors?
  • Next by thread: Re: Bug in CA kAudioDevicePropertyDataSourceNameForIDCFString?
  • Index(es):
    • Date
    • Thread