• 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: Locking the CoreAudio thread
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Locking the CoreAudio thread


  • Subject: Re: Locking the CoreAudio thread
  • From: "Timothy J. Wood" <email@hidden>
  • Date: Fri, 18 Jan 2002 13:39:28 -0800

On Friday, January 18, 2002, at 01:05 PM, Jeff Moore wrote:
[...]
I don't advise blocking the HAL's IOThread. You will get timing anomalies
that result in lost data. This is why there are no such locks you can take
to prevent the HAL (and therefore the Sound Manager) from calling you.
[...]

Yeah, but in this case I'd rather get sound glitches than crash :)

At any rate, you need not worry since this doesn't work anyway. I managed to block the CoreAudio thread during calls into the plugin, but the plugin then needs to get the SoundManager/CoreAudio lock when it attempts to start a sound (which would have been obvious if I'd thought about it).

So, the whole app ends up deadlocking.

Oh well, I guess plugins will just have to be threadsafe -- time to get in touch with Macromedia, I guess :)

-tim


References: 
 >Re: Locking the CoreAudio thread (From: Jeff Moore <email@hidden>)

  • Prev by Date: Re: HAL Devices and Streams (with QuickTime)
  • Next by Date: Re: HAL Devices and Streams (with QuickTime)
  • Previous by thread: Re: Locking the CoreAudio thread
  • Next by thread: Re: Sorry for wrong subject - question again
  • Index(es):
    • Date
    • Thread