Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: scheduling a block from a render callback

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: scheduling a block from a render callback

Subject: Re: scheduling a block from a render callback
From: Paul Davis <email@hidden>
Date: Wed, 08 Jan 2014 10:35:43 -0500

On Wed, Jan 8, 2014 at 10:21 AM, Tim Dorcey <email@hidden> wrote:

I put the data on a non-blocking FIFO queue, then send a 0 length UDP packet to a non-blocking socket I am waiting on with select(). It happens that I want to process the audio in my network I/O thread that is already waiting on the select() so this was convenient. I missed the rule about not using anything in the BSD layer, but I don't think this has caused any problems.

i would probably avoid using UDP for this, because i think it has notably more internal (kernel) overhead than a POSIX FIFO ("pipe"), which you could add to the fd's used by select(2). but to each their own. really, mach ports are the lightest object for this on Darwin but apple is making it incrementally harder to use them.

 _______________________________________________
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: scheduling a block from a render callback
  - From: Tim Dorcey <email@hidden>

References:
	>scheduling a block from a render callback (From: Lucas Ives <email@hidden>)
	>RE: scheduling a block from a render callback (From: Tim Dorcey <email@hidden>)

Prev by Date: Access AUSampler's pan & pitch parameters via UISlider
Next by Date: Re: Using AudioQueues with AudioConverterFillComplexBuffer....
Previous by thread: RE: scheduling a block from a render callback
Next by thread: RE: scheduling a block from a render callback
Index(es):
- Date
- Thread