Audiobus: Use your music apps together.

What is Audiobus?Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.

Download on the App Store

Audiobus is the app that makes the rest of your setup better.

Loopy (HD) / AUM Best Practices?

124»

Comments

  • @espiegel123 said:

    @TheDubbyLabby said:

    @espiegel123 said:

    @TheDubbyLabby said:

    @Hmtx said:
    little more work to set everything up but does not add any level of “instability” as was suggested as a concern earlier up in the thread. If anything it is the glue that makes everything more stable.

    By definition if I use just one app (GTL) vs GTL + any app (AB3/AUM/whatever) complexity is increased. So if I add one more as funnel or whatever function add an extra complexity layer...

    I use GTL mostly without anything else but if I can IAA directly (without AUM nor AB3 nor any host) then complexity is reduced (alongside boost in stability or almost common sense says that)

    I said this in that context and also said the point isn't against AB3 more than against any extra step in my uber simplified workflow where I even bought dedicated hardware for sounds and fx and I just use two or three apps (BlocsWave, Garageband and GTL). I even wondering buy a dedicated hardware mixer and avoid AUM for that duties...

    I bought Digitech trio+ as GTL replacement so go figure...

    GTL is a great app. Perhaps the point of this thread wasn't clear. The genesis of this was finding a nice realtime looping workflow for people that really dig their AUM setup and are looking to bring realtime looping in that context.

    It could also apply to people that love ApeMatrix.

    I have it clear and stated myself clear (so agree) but arguing some info gets out of context and needs put things clear.

    Realtime isn’t equal to gig oriented. I can do realtime looping with iOS but I need to test GTL (or any single app) as stable option for gigging. Adding extra layers goes against stability so no option for me at gigging. If I can’t trust any single app I will keep iDevices just for home (realtime or not) and use just hardware for gigging.

    If we talk about best practices for looping, or for gigging or for gigging looping with AUm/AB/Apematrix it makes a huge difference... but let’s try to be common sense talking about layers and stability (including crashes and usb inconsistent behaviour) and make clear the context with our affirmations.

    Said that I explain (and try to understand each) POV and even suggest how to be useful in the long run. I don’t want to sound cathegoric just answered because you quoted me :wink:

    I get lot of useful info and better background from all of you so I can discuss properly and share info wisely. <3

    I am not arguing that you should do anything differently.

    You imply that adding anything--I.e the AB3/AUM/Loopy combination-- adds instability. I can say confidently that it is a stable combination. One needs to be careful about which plugins and synths use but that is a completely separate issue.

    So, I'd be careful about implying that this is not a stable setup.

    I know mate but again crossed quotes and assumptions. I'm not saying AUM/AB3 are a problem per se, I'm saying more layers of cpu charge which it's obvious hard to keep stable than just single app. In fact iOS itself could be a problem for live gigging (and heaven for studio at same time)
    It could be that app (being GTL or any looper) could be worst coded than AUM/AB3 so make my argument weak but since I only use one app at time and none of them (AUM/AB3/Loopy or any single looper I found) offers quantized part launch (Michael said years ago this was in the roadmap for Loopy Masterpiece) I'm not going to add extra layer (midiflow) to try emulate what GTL does by default. One lf the biggest points of crashes (in my experience and maybe related to my interfaces) is connecting/disconnecting IAA and AUv3 between them, as host (for AB3) and to the hardware interface (as example Pure Synth or NeoSoul keyboards are madness in my set doing it no way for live rehersals... and I'm not affraid to say it loud and state things clear as most as I can in my experience (and trying to be polite and helpful) because I lost too much time and effort to make things work and found that simple sunny day puts my iPad into warning mode and waters the party...

    But that's my setup and personal stability levels and it's in that context I state myself. Less layers should mean less cpu stress by definition but I can be wrong for sure... and I hope iPadOS even makes things better for everyone.

    If I didn't need song part switching I will go for loopy since for me it's the most stable app but trying to replicate it (with or without midiflow) makes the whole setup just a mess (with app switching etc). I hope someday LMp arrives but probably I will be full hardware for this tasks at that moment of time (since I'm now with trio+ and I'm happy).

    This should be my last post in this topic because I'm repeating myself but answering due being quoted and expecting be able to add something useful to someone... so I will recap to end my intervention:

    • less (apps) is more (cpu free power for stability)
    • Harware usually is more stable than soft.
    • Software is usually more flexible than hardware.
    • I love flexibility for studio and stability for gigs.
    • iOS wasn't designed for music apps in mind but devs like Michael done an amazing job to prove Apple why it should be.
    • iPadOS seems the true answer to our needs and wishes as musicians but still complex software based (hybrid hardware) and we need to see true performance vs dedicated hardware solutions.
    • I'm not talking about personal taste (in fact I loved those bizarreous setups) more than applied experience so I needed to ditch this path and go more and more conservative for professional use (gigging). Shame but true (almost in my context)
    • I'm happy if other users find their own needs filled and can experience full iOS potential without drawbacks. It makes me keep hopes.
    • Opinions are personal and should be taken as grain of salt but facts should be set an standard. Performance tests should include sunny day performance more than controlled studio environment if we are giving advices for live gig use.

    That's all I can remember and say after 2 days without sleeping and playing rumba 10 hours yesterday :lol:

  • @TheDubbyLabby said:

    @espiegel123 said:

    @TheDubbyLabby said:

    @espiegel123 said:

    @TheDubbyLabby said:

    @Hmtx said:
    little more work to set everything up but does not add any level of “instability” as was suggested as a concern earlier up in the thread. If anything it is the glue that makes everything more stable.

    By definition if I use just one app (GTL) vs GTL + any app (AB3/AUM/whatever) complexity is increased. So if I add one more as funnel or whatever function add an extra complexity layer...

    I use GTL mostly without anything else but if I can IAA directly (without AUM nor AB3 nor any host) then complexity is reduced (alongside boost in stability or almost common sense says that)

    I said this in that context and also said the point isn't against AB3 more than against any extra step in my uber simplified workflow where I even bought dedicated hardware for sounds and fx and I just use two or three apps (BlocsWave, Garageband and GTL). I even wondering buy a dedicated hardware mixer and avoid AUM for that duties...

    I bought Digitech trio+ as GTL replacement so go figure...

    GTL is a great app. Perhaps the point of this thread wasn't clear. The genesis of this was finding a nice realtime looping workflow for people that really dig their AUM setup and are looking to bring realtime looping in that context.

    It could also apply to people that love ApeMatrix.

    I have it clear and stated myself clear (so agree) but arguing some info gets out of context and needs put things clear.

    Realtime isn’t equal to gig oriented. I can do realtime looping with iOS but I need to test GTL (or any single app) as stable option for gigging. Adding extra layers goes against stability so no option for me at gigging. If I can’t trust any single app I will keep iDevices just for home (realtime or not) and use just hardware for gigging.

    If we talk about best practices for looping, or for gigging or for gigging looping with AUm/AB/Apematrix it makes a huge difference... but let’s try to be common sense talking about layers and stability (including crashes and usb inconsistent behaviour) and make clear the context with our affirmations.

    Said that I explain (and try to understand each) POV and even suggest how to be useful in the long run. I don’t want to sound cathegoric just answered because you quoted me :wink:

    I get lot of useful info and better background from all of you so I can discuss properly and share info wisely. <3

    I am not arguing that you should do anything differently.

    You imply that adding anything--I.e the AB3/AUM/Loopy combination-- adds instability. I can say confidently that it is a stable combination. One needs to be careful about which plugins and synths use but that is a completely separate issue.

    So, I'd be careful about implying that this is not a stable setup.

    I know mate but again crossed quotes and assumptions. I'm not saying AUM/AB3 are a problem per se, I'm saying more layers of cpu charge which it's obvious hard to keep stable than just single app. In fact iOS itself could be a problem for live gigging (and heaven for studio at same time)
    It could be that app (being GTL or any looper) could be worst coded than AUM/AB3 so make my argument weak but since I only use one app at time and none of them (AUM/AB3/Loopy or any single looper I found) offers quantized part launch (Michael said years ago this was in the roadmap for Loopy Masterpiece) I'm not going to add extra layer (midiflow) to try emulate what GTL does by default. One lf the biggest points of crashes (in my experience and maybe related to my interfaces) is connecting/disconnecting IAA and AUv3 between them, as host (for AB3) and to the hardware interface (as example Pure Synth or NeoSoul keyboards are madness in my set doing it no way for live rehersals... and I'm not affraid to say it loud and state things clear as most as I can in my experience (and trying to be polite and helpful) because I lost too much time and effort to make things work and found that simple sunny day puts my iPad into warning mode and waters the party...

    But that's my setup and personal stability levels and it's in that context I state myself. Less layers should mean less cpu stress by definition but I can be wrong for sure... and I hope iPadOS even makes things better for everyone.

    If I didn't need song part switching I will go for loopy since for me it's the most stable app but trying to replicate it (with or without midiflow) makes the whole setup just a mess (with app switching etc). I hope someday LMp arrives but probably I will be full hardware for this tasks at that moment of time (since I'm now with trio+ and I'm happy).

    This should be my last post in this topic because I'm repeating myself but answering due being quoted and expecting be able to add something useful to someone... so I will recap to end my intervention:

    • less (apps) is more (cpu free power for stability)
    • Harware usually is more stable than soft.
    • Software is usually more flexible than hardware.
    • I love flexibility for studio and stability for gigs.
    • iOS wasn't designed for music apps in mind but devs like Michael done an amazing job to prove Apple why it should be.
    • iPadOS seems the true answer to our needs and wishes as musicians but still complex software based (hybrid hardware) and we need to see true performance vs dedicated hardware solutions.
    • I'm not talking about personal taste (in fact I loved those bizarreous setups) more than applied experience so I needed to ditch this path and go more and more conservative for professional use (gigging). Shame but true (almost in my context)
    • I'm happy if other users find their own needs filled and can experience full iOS potential without drawbacks. It makes me keep hopes.
    • Opinions are personal and should be taken as grain of salt but facts should be set an standard. Performance tests should include sunny day performance more than controlled studio environment if we are giving advices for live gig use.

    That's all I can remember and say after 2 days without sleeping and playing rumba 10 hours yesterday :lol:

    What don’t you get?

    Loopy (HD) / AUM Best Practices?

    The topic of the thread was very specific and you know exactly what the thread was attempting to discuss......

    🥴😉🤐

Sign In or Register to comment.