• 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: IOProc limitations
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: IOProc limitations


  • Subject: Re: IOProc limitations
  • From: James McCartney <email@hidden>
  • Date: Thu, 31 May 2001 20:52:49 -0500

on 5/31/01 7:44 PM, Jeff Moore at email@hidden wrote:


> Bear in mind, that you don't need to be holding a mutex to signal on it's
> associated condition variable (assuming you're using the PThread API).

Oh, I thought you had to hold a mutex just like on cond_wait.
I guess I just got in that habit writing semaphores with counters.
So that clears up all my concerns about that.

The other thing, is that if you are doing throughput processing, not doing
it in the IOProc causes an extra buffer of latency, correct? Because you
then must have the output ready when the IOProc runs, but you don't have the
input yet. So you must operate on the previous buffer of input.


--- james mccartney email@hidden <http://www.audiosynth.com>
SuperCollider - a real time synthesis programming language for the PowerMac.
<ftp://www.audiosynth.com/pub/updates/SC2.2.10.sea.hqx>


  • Follow-Ups:
    • Re: IOProc limitations
      • From: Bill Stewart <email@hidden>
References: 
 >Re: IOProc limitations (From: Jeff Moore <email@hidden>)

  • Prev by Date: Re: IOProc limitations
  • Next by Date: Re: IOProc limitations
  • Previous by thread: Re: IOProc limitations
  • Next by thread: Re: IOProc limitations
  • Index(es):
    • Date
    • Thread