• 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: Audio Units and OpenCL?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Audio Units and OpenCL?


  • Subject: Re: Audio Units and OpenCL?
  • From: philippe wicker <email@hidden>
  • Date: Thu, 10 Sep 2009 10:54:10 +0200


On 10 sept. 09, at 10:11, Stéphane Letz wrote:

What is available for audio developers with specialized AU does not solve the issues for people that would like to use newest Apple technologies (GCD, OpenCL) in audio applications outside of AU context.

Would it make sense to have a special version GCD for real-time usage? Right now GCD uses a pool of "normal" threads to execute pending tasks waiting on GCD queues. Why not have a pool of "time- constraints" threads to deal with RT tasks? Then we could have an extended API like:

dispatch_queue_t rt_queue = dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_REAL_TIME, 0);

and then tasks could be enqueued and executed (assuming they do not contain non RT code... as usual). We would need a way to set time- constraints for the set of RT threads (and assume the entire application would use the same time-constraints parameters).

[In the JACK on OSX project (http://www.jackosx.com/), we have JACK clients define a "time-constraints" thread that just use the same time-constraints parameters that are currently used in the RT thread used by the JACK server. So in essence we duplicate the time- constraints parameters given by CoreAudio to the JACK server to all JACK clients.. and this works quite well]

It seems that the OSX scheduler can deal with that situation. Maybe it doesn't mind a computational need exceeding the total available time.



Comments?

That would be nice :-)

This API should also provides means to get back the processed data compatible with a short latency constraint. Could that kind of services be built on top of an AUDifferedRenderer pool?


Stéphane Letz



_______________________________________________
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
References: 
 >Re: Audio Units and OpenCL? (From: Stéphane Letz <email@hidden>)

  • Prev by Date: RE: Using an AU directly
  • Next by Date: RE: Using an AU directly
  • Previous by thread: Re: Audio Units and OpenCL?
  • Next by thread: Re: Audio Units and OpenCL?
  • Index(es):
    • Date
    • Thread