• 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: A core audio bug? Is there a work-around?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A core audio bug? Is there a work-around?


  • Subject: Re: A core audio bug? Is there a work-around?
  • From: William Stewart <email@hidden>
  • Date: Tue, 24 May 2005 12:48:57 -0700

From what we can determine, this is only needed for Panther (the problem is fixed in Tiger) - we're in the process of writing up a Tech note for this problem

Bill

On 16/05/2005, at 10:04 AM, Luke Bellandi wrote:

Hi John,

Calling AudioDeviceAddIOProc(...) to add your IOProc(s) BEFORE making any calls to NSSound seems to successfully work around this problem.

You don't have to start your IOProc, just add it to the device.

Best,
Luke

On May 2, 2005, at 12:23 PM, John Draper wrote:


Hi,

There appears to be a bug in the CoreAudio HAL in a user-error situation.
the inInputData AudioBufferList is supposed to be treated as read- only,
and when our IOProc gets called, the inInputData->mBuffers [0].mData
is NULL.


It'll stay that way for every callback by the HAL after that. the HAL
makes one version of that AudioBufferList that it then fills in with
recorded audio and sends to you over and over. so if it gets broken,
it stays broken. Only after re-starting the Mac will it be reset again
until another error occurrs.


Mike Thornburg, the author of MTCoreAudio framework has reported
this bug in NSSound to Apple, and as of 10.3.9 it has NOT been fixed
where the NSSound IOProc would do that very thing to the *input* side,
which it wasn't even using.


Has anyone else found this problem? If so, please let me know, because
this is a show stopper, and might result in the cancellation of our entire
project (And my Job).


An Instance of support with Apple has already been submitted. But I want
to know if others ran into this problem.


John

_______________________________________________
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



_______________________________________________ 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


--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __


_______________________________________________
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: 
 >A core audio bug? Is there a work-around? (From: John Draper <email@hidden>)
 >Re: A core audio bug? Is there a work-around? (From: Luke Bellandi <email@hidden>)

  • Prev by Date: Re: Multiple outputs for the same source
  • Next by Date: Re: Building AU for pre 10.4 with Tiger
  • Previous by thread: Re: A core audio bug? Is there a work-around?
  • Next by thread: starting point of audio output for CoreAudio driver
  • Index(es):
    • Date
    • Thread