• 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: Does anybody implement 'reset' in their Instrument Audio Units?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Does anybody implement 'reset' in their Instrument Audio Units?


  • Subject: Re: Does anybody implement 'reset' in their Instrument Audio Units?
  • From: William Stewart <email@hidden>
  • Date: Wed, 24 Feb 2010 18:55:42 -0800

On Feb 24, 2010, at 2:37 PM, Paul Davis wrote:

> On Wed, Feb 24, 2010 at 5:32 PM, Eagle Offshore <email@hidden> wrote:
>> Because my experimentation suggests the answer is NO.
>>
>> I've been mucking about with trying to reduce CPU load by removing idle instruments from the AUGraph.
>
> I believe you should be called init/uninit in association with graph
> additions, not reset.

Not required.

For instance. In AULab when you mute one of the tracks we actually disconnect the last unit in that chain from the mixer. The unit is still in the graph, it is not going to render however. When the track is unmuted, you just connect the last unit back to the mixer. At this point there would be no format changes from what it last was, so the unit(s) are ready to go and just continue on their merry way. AudioUnitReset is called on the units before they are re-connected.

So, that is the expected behaviour/scenario.

One thing we did explore with the Logic guys was additional management of state.

When you took an AU strip out of the direct rendering chain, they were also interested in Ununitializing the AUs in order to reclaim memory that was being used by these inactive AUs. However, this turned out to be problematic as the user can still interact with the views of those audio units, and virtually NO 3rd party AUs worked properly with their view showing and the AU being uninitialized. So, that approach was shelved (the alternative would have been to do some additional work to disable the AUs from any user interaction in this state, but I guess they didn't want that kind of UI).

So, the summary from this is that just uninitialising the AU may be a cause for problems.

>
> we've just been through this in ardour/mixbus, and that was our conclusion.

You might want to revisit this (I don't know the workflow of you app, so it does depend on that).

Bill

 _______________________________________________
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: 
 >Does anybody implement 'reset' in their Instrument Audio Units? (From: Eagle Offshore <email@hidden>)
 >Re: Does anybody implement 'reset' in their Instrument Audio Units? (From: Paul Davis <email@hidden>)

  • Prev by Date: Re: Does anybody implement 'reset' in their Instrument Audio Units?
  • Next by Date: Re: kAudioUnitType_MusicEffect and Soundtrack Pro 3.0
  • Previous by thread: Re: Does anybody implement 'reset' in their Instrument Audio Units?
  • Next by thread: Re: Does anybody implement 'reset' in their Instrument Audio Units?
  • Index(es):
    • Date
    • Thread