For me it's mostly a matter of taking precautions. Right now I can open 35 instances of my most demanding plugin before they all go *poof*
But I don't like having a product with such a gaping boobytrap in it. Having said that, there are currently other plugins out there which are more sample-heavy or graphics/GUI-heavy which crap out after half a dozen instances. And it's reflecting badly on the entire platform (with vocal users concluding the system isn't ready for prime-time yet). ________________________________ From: Paul Sanders <p.sand...@alpinesoft.co.uk> Sent: Friday, July 27, 2018 11:20:40 AM To: Bram Bos; coreaudio-api@lists.apple.com Subject: Re: (iOS AUv3) memory limit for AU Extensions I guess my question would be: what are you using so much RAM for in the first place? Just my $.02. Also: please define 'crash'. Thanks. Paul Sanders (occasional poster). On 27/07/2018 10:05, Bram Bos wrote: Currently, iOS imposes a memory limit for AUv3 extensions. All combined instances of an AU extension should remain below a cap of 360Mb memory usage (on 64 bit devices). In all hosts I've tested with, crossing this limit will crash all instances of the extension without warning, often leading to problems like corrupted projects etc. - Are there any known plans to remove this 360Mb cap? Available memory has doubled/quadrupled since the standard was introduced, so it seems less necessary now. - Is there a way for either hosts or extensions to catch/prevent the crash from happening in the first place? Something a little more elegant than going down in flames 😉 Thanks for any insights!
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list (Coreaudio-api@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to arch...@mail-archive.com
