• 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: tahome izwah <email@hidden>
  • Date: Wed, 9 Sep 2009 17:38:57 +0200

Well, I must admit I am a bit disappointed then. I was planning on
using GCD to help me schedule tasks for FX rendering in a realtime
environment, but apparently I'd better go back to using threads in
this case. I thought GCD was lower level than using threads (Apple
seems to hint to this in their documentation), but apparently not.

GCD sounded like a very useful feature for doing distributed rendering
in video and audio apps, but if it's just a scheduler that runs
through a list of function pointers within the main thread level this
is not really worth investing time into checking out, unless you're
looking for a nifty way to get your progress bar moving etc... :-(

--th

2009/9/9 Markus Fritze <email@hidden>:
> GCD is very useful, but from what I see just not for real-time applications.
> And no, it doesn't necessarily come to a "halt", but it can be affected,
> which is what you really DON'T want in a real-time situation.
>
>
> Markus
>
> On Sep 9, 2009, at 8:28 AM, tahome izwah wrote:
>
>> Really?? Now that wouldn't make GCD very useful in practice, would it?
>> If everything scheduled by GCD across all CPUs comes to a halt when
>> you hold down the mouse on a dialog what good is it then? That sounds
>> a bit like a flashback to MacOS 9 times to me... or am I
>> misunderstanding what you are saying? (still waiting for my copy of
>> SL..).
>>
>> --th
>>
>> 2009/9/9 Markus Fritze <email@hidden>:
>>>
>>> Ehm, you know that GCD is running at the main thread level? Which can be
>>> blocked by UI operations, etc. That doesn't seem like a wise choice for
>>> real-time processing. OpenCL also doesn't have a threading mode, so you
>>> tasks will be shared among all the others and your latency becomes
>>> unpredictable.
>>
>
>
 _______________________________________________
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: 
 >Audio Units and OpenCL? (From: Mike Lemmon <email@hidden>)
 >Re: Audio Units and OpenCL? (From: Jean-Daniel Dupas <email@hidden>)
 >Re: Audio Units and OpenCL? (From: Markus Fritze <email@hidden>)
 >Re: Audio Units and OpenCL? (From: tahome izwah <email@hidden>)
 >Re: Audio Units and OpenCL? (From: Markus Fritze <email@hidden>)

  • Prev by Date: Re: Two AUs in one bundle
  • Next by Date: Re: Audio Units and OpenCL?
  • Previous by thread: Re: Audio Units and OpenCL?
  • Next by thread: Re: Audio Units and OpenCL?
  • Index(es):
    • Date
    • Thread