• 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
Multi-threaded render
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Multi-threaded render


  • Subject: Multi-threaded render
  • From: Ethan Funk <email@hidden>
  • Date: Sat, 5 Aug 2006 12:41:00 -0700

Currently, I have an audio application, like many, where multiple audio sources are mixed together by a custom mixer and delivered to the HALoutput AU. All is well except, in the interest of efficiently using multi-processor systems, I would like to move away from the single thread render approach, and have each mixer input run in it's own thread.

For example, the HALOutput AU would callback to my mixer in the usual coreaudio rendering thread. My mixer would then wake a render thread associated with each of it's inputs and block the calling rendering thread until all the input threads have buffers ready for my mixer. My mixer would then continue executing the coreaudio render thread where it would mix the input results and return the final buffer to the HALOutput AU. All this should be simple to implement, however, I believe that rendering threads have some special realtime properties, and I have no idea how to create such threads for each of my mixer inputs. Likewise, I don't understand threading on OS X well enough to know what scheduling problems I may encounter. Any ideas where I can go to learn more about this sort of thing?

My ultimate goal is to move each mixer input render in it's own thread so that concurrent processing COULD occur when there is more than one processor available. It would appear that as things stand with the single thread approach, each mixer input chain must be rendered one at at time. The total render time is the sum of the time required to render from all the inputs together. If I have a heavy processing load (a lot of AU effects in the input chains), even with multiple processors, the whole render process will only use one of the available processors. If I have two or more processors, it would be nice to have each processor work on different renders to improve the chance that it would all get done in time to deliver the results to the HALOutput AU.

Any one else doing anything like this? Am I going down a wrong road here?

Ethan...
_______________________________________________
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: Multi-threaded render
      • From: William Stewart <email@hidden>
    • Re: Multi-threaded render
      • From: Craig Hopson <email@hidden>
  • Prev by Date: Re: GetParameterList in ableton Live problem - AuParameterListenerNotify usage.
  • Next by Date: Re: Multi-threaded render
  • Previous by thread: Re: Coreaudio-api Digest, Vol 3, Issue 240
  • Next by thread: Re: Multi-threaded render
  • Index(es):
    • Date
    • Thread