• 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
MTCoreAudio.framework bugfix release
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

MTCoreAudio.framework bugfix release


  • Subject: MTCoreAudio.framework bugfix release
  • From: Michael Thornburgh <email@hidden>
  • Date: Wed, 2 Jul 2003 21:42:09 -0700

howdy everybody.

there is a new release (1.1.2) of MTCoreAudio.framework to address a problem i noticed while playing with my new iSight. :) it also adds one feature. both items are detailed below.

as always, the framework, two sample programs, full source, and documentation can be downloaded from

http://aldebaran.armory.com/~zenomt/macosx/MTCoreAudio/

new feature: there is now a +[MTCoreAudioDevice attachNotificationsToThisThread] method to change the run loop on which the HAL's notification mechanism runs, as recommended by jeff on dec 6 2002. the AudioMonitor sample application now does this in its main(), which solves some gui glitches while simplifying the implementation.

problem that was corrected: devices that are input-only AND which pass NULL in on the outOutputData parameter of the IOProc could cause the MTCoreAudio IOProc/IOTarget dispatcher to crash, but only if more than one IOProc/IOTarget was active on that physical device simultaneously. the cause of this was that i assumed outOutputData would never be NULL, but instead would just be a valid AudioBufferList* with zero streams (as is currently the case with all input-only devices to which i have access, which are USB audio devices). if only one IOProc/IOTarget is active, there's no problem, but when the second one starts, the dispatcher will take extra steps to accommodate outOutputData mixing from the different IOProc/IOTargets. these operations dereferenced that NULL pointer. this case is now checked for.

the iSight presents a NULL outOutputData to its IOProc, which is how i found this.

if your application never has more than one IOProc/IOTarget on a physical device, then you don't need to worry about this. :)

finally, for those who don't know: MTCoreAudio.framework is a Cocoa-flavored Objective-C wrapper for the CoreAudio HAL. let me know if you have trouble, questions, or feature requests.

-mike
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Bug in Daisy
  • Next by Date: MusicPlayer/MusicSequence
  • Previous by thread: Re: Bug in Daisy
  • Next by thread: MusicPlayer/MusicSequence
  • Index(es):
    • Date
    • Thread