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.

Using Drambo as midi looper inside Loopy Pro

espiegel123espiegel123
in Loopy Pro

Ultra quick demo showing how to set up Drambo as a midi looper inside Loopy Pro

Comments

  • gregsmithgregsmith

    Nice one. This is exactly what I do whilst waiting for midi loops in Loopy.

  • senhorlampadasenhorlampada

    Awesome, mate. Thanks for this

  • emc87emc87

    Yes works well, I have mine setup now with a dummy donut to set whatever amount of bars I set in the master in loopy pro, and one that just records to whatever i have set in Drambo, so I don’t have to go back and forth so much. Also have automation recording in Drambo to loopy pro now. It’s a bit complicated to set up but yea really cool. Can’t wait for midi loops and multi in and out AUV3.

  • wimwim

    I have one suggestion for this setup:

    I like to first add Drambo as an Audio Input, then add that same instance as a MIDI Input. That way if I wish to make use of some tracks with Drambo generators I can. If you add the MIDI first, you can't add the same instance as an Audio Input.

    My default template has these two already set up with both muted so Drambo is always available for whatever I need.

  • mistercharliemistercharlie

    This is very useful. Usually, I do the exact opposite: Loopy Pro as an audio looper inside Drambo!

  • wimwim

    The wonderful thing about doing it this way around is being able to commit to audio then idle plugins to save CPU - important with my aging device.

  • BroCoastBroCoast

    @wim said:
    The wonderful thing about doing it this way around is being able to commit to audio then idle plugins to save CPU - important with my aging device.

    Initially I was doing Loopy hosted by Drambo to take advantage of the easy au parameter automation. But I prefer Loopy as the host now and committing to audio basically achieves the same result.

  • gregsmithgregsmith

    @wim said:
    I have one suggestion for this setup:

    I like to first add Drambo as an Audio Input, then add that same instance as a MIDI Input. That way if I wish to make use of some tracks with Drambo generators I can. If you add the MIDI first, you can't add the same instance as an Audio Input.

    My default template has these two already set up with both muted so Drambo is always available for whatever I need.

    Ooh I hadn’t thought of this! Good shout.

  • mistercharliemistercharlie

    @wim said:
    The wonderful thing about doing it this way around is being able to commit to audio then idle plugins to save CPU - important with my aging device.

    This is a great point!

Sign In or Register to comment.