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.

Audiobus with built in fx

I was thinking that it might be a good idea for the audiobus developers to build some fx into audiobus. Perhaps the standard Eq, chorus, phaser, reverb, filter. These could be assigned to any of the audiobus tracks. That way we could have multiple instances of audiobus's fx over its chanels(tracks).. Each Chanel could have an fx send or insert slot. Just a thought.

Comments

  • I really don't like the idea of audiobus becoming more than a pipeline. We have an abundance of fx and daws. I would prefer audiobus to be great at what it does and to keep its scope reduced to allow it, personally.

  • @Digitalresonance said:

    I was thinking that it might be a good idea for the audiobus developers to build some fx into audiobus. Perhaps the standard Eq, chorus, phaser, reverb, filter. These could be assigned to any of the audiobus tracks. That way we could have multiple instances of audiobus's fx over its chanels(tracks).. Each Chanel could have an fx send or insert slot. Just a thought.

    I get what you're saying. But I don't see that happening as far as Audiobus go. What really needs to happen is Apple coming up with a way to allow us and devs to run multiple instances of the same app. They could somehow limit this functionality to certain type of productivity apps (like music creation applications, CAD, design etc), and have a set of rules & policies in place an app like that would need to fulfill to pass a review and be allowed onto the AppStore as a "multi tasking enabled app". Or something like that...

  • Or effects apps themselves could become multi instance capable. So when you load aufx:dub and it sees more than one audiobus pipe pointed at it, it could offer to run a second internal instance of its processing. Similar to the way daws will create multiple tracks based on AB inputs.

    Probably far from trivial but could be a nice source of IAP for devs/apps that could swing it.

  • edited May 2014

    We'll I think it would completely enhance the audiobus experience as things currently stand regarding everything to do with how music is made on an ipad.. If I'm playing some beats from one app and couple synths from another it's all well and good placing an effect app in the fx slot of an audiobus lane but instantly limited by only using one instance of said app.

    Another way to do it could be a way to load an effect app into a new audiobus track called a send track. Then similar to a mixing desk you could have sends on the audiobus tracks to send the signal into the app fx track... This way u could send anyone of audiobuses track signals to it.

  • edited May 2014

    Implementing a bus routing system of sorts into Audiobus would be really great, and really useful. If do-able, it should be taken care of entirely by, and inside, the Audiobus app. I think adding yet another thing to the SDK that devs needs to mess around with wouldn't be too popular.

  • @ChrisG said:

    Implementing a bus routing system of sorts into Audiobus would be really great, and really useful. If do-able, it should be taken care of entirely by, and inside, the Audiobus app. I think adding yet another thing to the SDK that devs needs to mess around with wouldn't be too popular.

    I agree.

    But the sdk will change overtime anyway with things devs will need to adhere to. It's worth it even if it comes to it.

  • edited May 2014

    @syrupcore said:

    Or effects apps themselves could become multi instance capable. So when you load aufx:dub and it sees more than one audiobus pipe pointed at it, it could offer to run a second internal instance of its processing. Similar to the way daws will create multiple tracks based on AB inputs.

    Probably far from trivial but could be a nice source of IAP for devs/apps that could swing it.

    This is what I'm sayin :)

    http://forum.audiob.us/discussion/4686/is-it-possible-for-ab2-to-do-an-auria-trick-and-make-apps-appear-multiple-times#Item_12

    AB2 on steroids...

  • Yes, EQ, Compressor, Gate, Reverb. Low latency for live use and multiple instances.

  • I'm with @skoptic

    I think AB should only focus on connecting apps...and maybe unify midi if possible

  • DebDeb
    edited September 2014

    yeah..i know, we get it...

    But there needs to be development of a group of basic utility effects, nothing fancy, that can be used in multiple instances. It may have to come from the Audiobus team...I'm not a developer so I can't say for certain if third party will have the ability to implement multiple instances.

  • @skoptic said:

    I really don't like the idea of audiobus becoming more than a pipeline. We have an abundance of fx and daws. I would prefer audiobus to be great at what it does and to keep its scope reduced to allow it, personally.

    Especially if any of the possible upgrades barely hinted at by the Audiobus team come to pass - lean & mean for me!

  • Don't underestimate the savvy of J. Liljedahl, Christopher Rice, Igor Vasiliev, and people like them. They've done some incredible stuff so far and Multiple Instances might be in their plans. Definitely would be cool to have.

  • That would be great! I would rather it come from an EFX developer too...

  • Actually iMini, for all its warts, is multi-instance capable, but only in the TableTop environment. But it is an existence proof it can be done.

    The thing that might take a lot of time for the efx devs however, is if the single instance codebase uses a lot of global variables. Or any, even. Multi-instance is one of those attributes that is straight-forward to include in the initial design but a real bear to retrofit.

    Then there is the issue with e.g. IAA that IIRC assumes an App once included cannot be included again. I don't believe multi-instance is accommodated by IAA (could be wrong, pls correct).

  • edited September 2014

    @dwarman "Actually iMini, for all its warts, is multi-instance capable, but only in the TableTop environment. But it is an existence proof it can be done."

    This David ^^^^ Exactly. The same as FX in Auria can be multi-instance. I bought Turnado outside of Auria, my Turnado was grandfathered in to Auria when the Auria folks did that, yet, I can run multiple instances of Turnado in Auria...

  • @NoiseHorse said:

    Don't underestimate the savvy of J. Liljedahl, Christopher Rice, Igor Vasiliev, and people like them. They've done some incredible stuff so far and Multiple Instances might be in their plans. Definitely would be cool to have.

    Yes, but we're talking about Audiobus - somehow I doubt they will have anything to do with future AB updates, beyond making sure their apps keep up with the future AB SDK's...

  • Multiple Instances Doctor Immediately!

Sign In or Register to comment.