• 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: [ios] graph init and start in separate thread
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ios] graph init and start in separate thread


  • Subject: Re: [ios] graph init and start in separate thread
  • From: Gregory Wieber <email@hidden>
  • Date: Thu, 26 May 2011 14:20:35 -0700

Since iOS doesn't have those effect audio units, option a is out for the time being. I made a modular synth on iOS about a year ago, and struggled to find an efficient way to evaluate the entire graph of nodes. I'm interested in what other people here might suggest. Maybe cross-post this in a comp-sci mailing list as well? 



On Wed, May 25, 2011 at 5:21 PM, Aran Mulholland <email@hidden> wrote:
On Q1, I have never had a drama doing this and like to because of the
excessive amount of time it takes to init the lot. the other technique
I have used is to start it going while the splash screen is still
visible.

no answer on Q2 from here...but would like to hear what others have to say.

On Wed, May 25, 2011 at 6:11 PM, steph ohara <email@hidden> wrote:
> hello
> i have 2 questions regarding creating, initialising and starting a coreaudio
> graph with ios devices
> 1. is it safe to place the init/start calls in a separate thread thus
> "free-ing" the main thread to do other work such as ui updates? i have tried
> this technique and it works but i have not tested on all devices.
> 2. this is more an open question to developers. what is the more efficient
> technique if one were to build say a modular audio structure. either (a) use
> coreaudio's built-in graph/audio unit or (b) roll out your own. as an
> example
> technique (a) create an AUGenerator -> AUFilter -> AUDelay ->AUOutput, each
> being a audio unit.
> technique (b) create an AUOutput and inside rendering, have a custom
> node/graph structure.
> i am mostly interested in efficiency (cpu use) and if there
> are accumulative  bottle-necks between AUUnits.
> cheers steph
>
>
>  _______________________________________________
> 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

 _______________________________________________
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: [ios] graph init and start in separate thread
      • From: Gregory Wieber <email@hidden>
References: 
 >[ios] graph init and start in separate thread (From: steph ohara <email@hidden>)
 >Re: [ios] graph init and start in separate thread (From: Aran Mulholland <email@hidden>)

  • Prev by Date: Re: Iterating through audio data
  • Next by Date: Re: [ios] graph init and start in separate thread
  • Previous by thread: Re: [ios] graph init and start in separate thread
  • Next by thread: Re: [ios] graph init and start in separate thread
  • Index(es):
    • Date
    • Thread