The interview is primarily David's use of Auria in his workflow.
Auria is powerful and pushes device resources to their limits especially when using its plug ins and FX, making it difficult to use on iPad 2. I don’t know if it can be made any more efficient or not? It’s easy to avoid problems. Limiting the number of simultaneous Audiobus inputs, and taking advantage of track freeze is key to avoiding low memory, low CPU warnings and crashes. The only times I ever run into those issues are when I forget to close a background app, try to run too many inputs, or fail to freeze tracks with plug ins assigned. Wave Machine Labs is really showing (as seen in recent updates) that they’re listening to users and making solid improvements; like the touch/drag duplicate region bypassing the need for a drop down, and touch controlled TimeStretch.
That is all really good advice for anyone who is trying to use Auria. In the desktop world people are used to freezing tracks to preserve CPU. On iOS we tend to just expect anything we try to do, to work! That isn't always a reasonable expectation.
Read the full interview over on iOS Musician.