RE: Does anybody implement 'reset' in their Instrument Audio Units?
RE: Does anybody implement 'reset' in their Instrument Audio Units?
- Subject: RE: Does anybody implement 'reset' in their Instrument Audio Units?
- From: Muon Software Ltd - Dave <email@hidden>
- Date: Fri, 26 Feb 2010 09:31:35 +0000
- Acceptlanguage: en-US, en-GB
- Thread-topic: Does anybody implement 'reset' in their Instrument Audio Units?
> For a AU host, you can use these numbers to load balance your plugins - once they have gone past an active segment, you can use these numbers to know how much additional data you > need to pull through them. Once you have done that, any further "rendering" by that AU is wasted CPU cycles until you have new data to give it.
When referring to AU instruments as the OP apparently was, I can't agree with this suggestion for reasons already stated. I would say that hosts additionally need to check to see if the instrument's GUI is open and has focus - if the GUI is open and it has focus, it could make a sound *without* the host being involved at all. Patch browser previewing or onscreen keyboards are commonplace and even pretty much standard these days - they're certainly far too commnplace to be broken in any given host.
Whilst I think about it, I even wrote an AU effect for a client recently that, for one reason or another I won't go into, needs to have its audio thread running continously. It is designed to be inserted on an Input channel strip so (in Logic at least) its Render function is called continously. I probably shouldn't rely on that, so it'd be nice if there was a property I could set that declared "this AU needs continous rendering".
David Waugh
Managing Director
Muon Software Ltd
http://www.muon-software.com
http://muonsoftware.blogspot.com
_______________________________________________
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