IAA-Sync vs Link on a single device?

boberto

I do all my music stuff on a single iPad. I've been going back and forth between using IAA and Link. Can't make up my mind!

Link:

• Not widely adopted.
• Lacks a "Master" start-stop for all apps.

IAA:

• For IAA apps it's I've found it impossible to tell which support IAA-sync without experimenting.
• Only a host app (AUM, BM2, ___)can act as master stop/start/tempo-set.

There was that one blog article that said working with IAA is better for a single device, but I dunno, I find that few IAA apps actuall respond to tempo-sync instead of just start/stop...

Your 2c?

Kaikoo2

Their functions are not in the same equation (IAA and Link). Don't hurry yourself, see all my tutorials on app Tips and Tricks. you will learn.

[Deleted User]

Link is new tec. And it's wildly adopted. I'm counting 50+, getting more each day
There is a master start stop in the ab sidebar in link/ audiobus only set ups. (I don't think that part is iaa). Any app can set and change the tempo if u want to with link.(forget the master slave thing of host and plugin and midi clock master slave - that's so yesteryear )

https://audiob.us/apps/capability/link/page/1-3

What is causing a little confusion with link is that apps with link can start in at the next 1 in the beat, not all apps support this or need this.
Some just grab the tempo but are not on the "next one" in the beat, so they are in time - that has its use cases. https://audiob.us/apps/capability/link/page/1-3

This isn't well explained if you haven't read the link api guidelines.
@Sebastian Someone cough needs to step up their explain this to the non hardcore user game. as you can use link without live I guess it's your part to do. Who else will do it?

Hope this helps.

Audiojunkie

Link is for live use and for using multiple devices. That is where it works best. It syncs all of the multiple components up within a live situation, but it doesn't have transport controls beyond what is commonly used live.

IAA is best for working on one device and works great with sequencing material. A lot of developers claim IAA support just because the app supports Audiobus. You have to be careful of this, because the IAA support that comes with Audiobus is only a small subset of the tech, and quite useless. Before you buy an app that interests you, check with people to confirm that the app works with sequencing from a piano roll, has a working transport control, and everything works properly. If you do this, you will do well with IAA.

Audiojunkie

Both are important and useful technologies that complement rather than compete with each other.

AudioGus

I use them both. If a third sync option comes out I will likely use that too.

zeropoint

Is there a list somewhere of apps that support IAA sync ? Thanks

boberto

@zeropoint said:
Is there a list somewhere of apps that support IAA sync ? Thanks

Seconded. But I've been looking for that for a while. :-/

[Deleted User]

@zeropoint said:
Is there a list somewhere of apps that support IAA sync ? Thanks

Not that I'm aware of. One of the strengths and services provided by Audiobus is that you have a searchable database in the app which includes information about whether apps have the following:

Inputs
Effects
Outputs
Audiobus
State Saving
Ableton Link
Remote Triggers

Since music is just one part of Apple's iOS user base and music creation an even smaller proportion, Apple's attention to these sorts of details doesn't occur. At times this can lead to developers coming up with ideas like Audiobus or the many MIDI use innovations by the Secret Base Design developer that get undermined in the next major iOS release as Apple incorporates their approach into iOS.

IAA is certainly such a case and forced a major recoding of Audiobus to incorporate IAA as a free upgrade to work on versions of iOS when IAA was added to iOS. The uneven and disjointed way IAA has been implemented versus how the Audiobus team has worked with developers is significant.

It would be useful to find a way to support more collaborative developers like the Audiobus team and the developers who have added Audiobus support so that we have consistently useful apps for creating music and sensible ways of finding out about their functionality. We can all benefit by urging Apple to communicate clearly with independent app developers to minimize their efforts being wasted or co-opted by inconsiderate Apple decisions.

I'd encourage and support developers of IAA apps to provide information about their apps which provides:

Input
Effect
Output
IAA Host Sync
Transport Controls
Icon Switch to and from IAA host sync app
(note how similar all of this is to Audiobus)

Who is going to compile such a database, how will it be updated, and where will the resources to do any of this come from? How can developers be encouraged to participate?

While I've always liked the capabilities of Audiobus from the get go, there are apps such as AUM (it has Audiobus support) which offer alternative work flows based on using IAA apps (including apps without Audiobus support) not currently available in Audiobus which appeal to me. Nevertheless it is equally clear that the AUM developer is not in a position to support IAA developers and IAA as the Audiobus team has for many years. It would be a shame to see the efforts of the Audiobus team undermined by apps like AUM which would not have been possible without the efforts of the Audiobus team. It'd be a loss if IAA and AU led to developers creating apps lacking the coherent GUI, compatability, and work flow Audiobus has provided and we end up with a fractured and broken iOS music creation ecosystem.

Audiojunkie

@zeropoint said:
Is there a list somewhere of apps that support IAA sync ? Thanks

Loran Pittman has a list that does this, I believe. He's a member of iOS Musicians on Facebook.

zeropoint

Thanks for the replies guys. I'll see if Loran has a list that he wants to share......