Water will flow (my thoughts on AU).

Antkn33

I understand. I’m not speaking of your apps, I love them.
For a users perspective when an app say it supports Au you don’t know what it really does until you buy it.

@brambos said:

@Antkn33 said:
Personally, the problem I have with AU is the uneven implementation. Meaning, some support fullscreen some don't. If the app works in stand-alone mode you can't access your presets in AU mode in some cases. And you can't access some features in AU mode that are in stand-alone mode.
I don't know if its a technical limitation of AU. I am just speaking from a user's perspective. Many times I find myself spending more time on technical hurdles than creating.

Those are not limitations or problems of AU per se. It's just a developer choosing not to implement something. In general AU implementations are a lot more consistent with each other across the board than IAA, where MIDI, Link, state saving and other things tend to be completely different from one app to the next.

@brambos said:

@Antkn33 said:
Personally, the problem I have with AU is the uneven implementation. Meaning, some support fullscreen some don't. If the app works in stand-alone mode you can't access your presets in AU mode in some cases. And you can't access some features in AU mode that are in stand-alone mode.
I don't know if its a technical limitation of AU. I am just speaking from a user's perspective. Many times I find myself spending more time on technical hurdles than creating.

Those are not limitations or problems of AU per se. It's just a developer choosing not to implement something. In general AU implementations are a lot more consistent with each other across the board than IAA, where MIDI, Link, state saving and other things tend to be completely different from one app to the next.

ZenLizard

@Antkn33 said:
Why not the last 2%?

@J_B1GS said:

@gusgranite said:

Anyway... AU.
I have been working on a new track and my workflow is to build it in AUM and AB3 MIDI and then export the stems to BM3 for arranging and further sampling/tweaking/layering. I realized that I am, almost subconsciously, only choosing AU apps. Which is crazy as I have the most amazing IAA sound sources and effects on my iPad. But the convenience just always makes me choose the AU version if there are AU and IAA apps that do something similar. I hadn’t really registered just how helpful the AU state saving really is. And now with folders in AUM, version control of states is really useful. The low resource overhead of most AUs means I can have 20 AU channels running in AUM with no issues (half of them are Rozeta modules, mind). Often, introducing an IAA app into the mix will crash it much sooner than that. Then there is BM3 which naturally pulls you to AU also (and now AU MIDI as well).

Don’t get me wrong, some IAA apps (in my case apps like Navichord, Quantum, Xequence and DrumPerfect Pro) still make the cut. But, if I am honest, this is probably because there is currently no real AU alternative to these wonderful apps.

Now the respect part. I understand the effort that goes into development. I understand that developers may not have the resources to immediately upgrade their apps to AU. I also understand the endless desire that people have for ‘bright shiny objects’ and that some developers may want to watch to see where this lands before committing to AU. I just wanted to share an individual iOS workflow and how I seem to have chosen the AU path without really thinking about it. I am still very new to music production however so please take this a personal opinion piece.

Very well written!
I am in agreement with all 3 of your paragraphs (thoughts). I too find my self going the AU route and have started to realize that maybe I am doing this is because of the “Newness” of Au and now AU Midi. Owning probably, without exaggeration, 98% of all the Audio Music Apps available for IOS (1254 and counting) so I definitely have everything and anything available to me for my projects, but as you say, I am going to AU a lot more BUT it is not a deal breaker if the new App coming out isn’t available as an AU

Have you seen the last two percent? (shudder)

Antkn33

Hah

gusgranite

@brambos @jimpavloff out of interest - do developers get stats on when their apps are opened as AUs vs IAA? You have apps that are both so I am curious what the usage is like.

SpookyZoo

@gusgranite said:
@brambos @jimpavloff out of interest - do developers get stats on when their apps are opened as AUs vs IAA? You have apps that are both so I am curious what the usage is like.

Great question!

gusgranite

Very interesting that it looks like Nanostudio 2 will ONLY support AU and will not be IAA compatible. This is a first I think? Snip from another thread:

https://forum.audiob.us/uploads/editor/pu/zor3m70j8r97.png

TheOriginalPaulB

I’ll use anything that makes the noises I’m after. AB now even lets me record non AB/IAA/AU apps into my DAWs if I need to, so it’s all good.

[Deleted User]

When using multiple apps AU is just a better work flow, hard to argue that.

kinkujin

Oh golly ... c’mon NanoStudio!

realdawei

Nuff said

[Deleted User]

I think the Nano dev is doing the right thing. Keeping the app streamlined for AU work. When wanting to connect up IAA, AudioBus 3 is still my preferred solution.

wim

As long as it is AB3 compatible, shouldn’t be a huge issue. If it isn’t AB3 compatible then it will be simply not for me. I have too many cherished apps that will never be AUv3 to sideline them all.

Gutsy move btw.

gusgranite

Just read that Apple are lifting the AU max memory limit for iOS 12 (on higher end devices at least). This is big news! (Thx @YZJustDatGuy ).

JeffChasteen

@TheOriginalPaulB said:
I’ll use anything that makes the noises I’m after.

This.
So much this.

gusgranite

I hope Apple make developing an AU less complex as well. It sounds like that is still a barrier and why some new apps are still going the old IAA route.

gusgranite

@JeffChasteen said:

@TheOriginalPaulB said:
I’ll use anything that makes the noises I’m after.

This.
So much this.

Well that’s the bottom line, for sure! But I’ve had a hell of a time with IAAs crashing in my current track (Chordploypad and Future Drummer in this case) that I am pretty excited by the way things are going. It’s great to hear that Apple are taking note on how to improve AU as we all know it isn’t perfect either. Good times!

YZJustDatGuy

@gusgranite said:
Just read that Apple are lifting the AU max memory limit for iOS 12 (on higher end devices at least). This is big news! (Thx @YZJustDatGuy ).

Courtesy of Crudebyte:

https://twitter.com/crudebyte/status/1040245699626057728

Also, I have installed iOS 12 on my iPad after reading this. I haven’t had an AU crash on me yet using BM3 on iOS 12, iPad Pro 10.5. I’ve loaded at least 10 CPU heavy sessions that would crash BM3 every time after constant loading.

gusgranite

@YZJustDatGuy very cool

AtticusL

@gusgranite said:
Just read that Apple are lifting the AU max memory limit for iOS 12 (on higher end devices at least). This is big news! (Thx @YZJustDatGuy ).

This is great news. I have a feeling it might solve the hassles I’ve had with Neo-Soul keys studio and PPG Infinite acting up in Garageband.

rezidue

I'm super happy to hear that they bumped up the memory limit. Time to test!

gusgranite

Older thread but still relevant. It looks like Audio Damage are the next to drop IAA support:

supadom

I see varying responses to this and imagine they will depend on what people are using.

Those not having any precious IAA apps go like: we need to move on, it’s old tech, get over it etc.

Those like me with samplr etc are the exact opposite.

So the argument is DOA because camps are predefined and will never agree. I love new tech but when I see every iOS update breaking shit I’m not so sure anymore. Too much freaking stress!

I will stop updating if IAA gets dropped completely.

Unless Drambo gets all the functionality I require, which might still take a while but won’t be far from the truth.

[Deleted User]

I’m still on monolithic approach (Blocs, GTL, ...) and little IAA for lumbeat apps (but I can work with midi out) and I will go the gb hosting into logic so I will keep these update up to a certain point but not further.

Water was flowing and will be. Give iOS app wrapper into macOS (or logic for iPad pro...) and I will consider update even hardware things (I know... catalyst) but not so a must.

Things are workable as is...

aleyas

Yeah, I still use IAA when I’m in need of a sound module to use with IDAM to Ableton. Or for sample fodder. In a way, lots of those old IAA feel more like instruments unto themselves than a lot of AUs do. I guess to me, the AUs feel like pieces of a larger whole, but not the whole picture itself.

That said, there aren’t many IAA I still use. Samplr, Borderlands, Thumbjam, Zmors and Hexaglyphics are really the only ones that matter to me anymore. I think they just excel in different workflow scenarios than are currently developing in the iOS music scene.

ashh

Ah, a visual thinker. I do love a visual thinker. Water will flow. Very good.

Oh, and, they're all personal opinion pieces. Even if Beethoven lived today and the iPad was his medium.