Loopy Pro: Create music, your way.

What is Loopy Pro?Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Multitracker and Audiobus Transport Control

Hey folks, I’m trying to achieve something like the following:

  • Multitracker app (or something similar, tbh) running backing tracks, clock and transport, and sending program change events.
  • Audiobus listening to clock and transport and running some MIDI generators, scaler, some softsynths and VS, relaying the program chain events between songs.

While I got Audiobus to listen to Multitracker’s clock and BPM, I’m having a hard time getting Audiobus transport to start/stop when Multitracker’s does. I’ve tried doing the Learn functionality and futzed around with the manual mapping but couldn’t land on that.

Any help much appreciated! Thank you!

PS: I noticed that I cannot load up Multitracker inside Audiobus which probably complicates what I’m trying to achieve. This would be somewhat ideal though, since then my Audiobus hosted synths and the backing tracks would be on the same mixer.

Edit: On iPad M1 Air with 17.5.1

Comments

  • wimwim
    edited July 7

    @nobbykneeson - sorry to say there isn't going to be any way to load Multitracker inside Audiobus. Multitrack is a fully standalone app and doesn't have either the Inter-App Audio (IAA) or Audiobus extensions to enable it to do that. This will be true for any host, not just Audiobus.

    I'm not sure that the type of signaling that Multitracker sends for transport control is compatible with Audiobus. What Audiobus and most iOS apps I know of that work with midi clock generally respond to is MIDI Beat Clock. You may need to see if there's some way to get MultiTracker to send specific midi messages on transport start and stop.

    This is just going by the App Store description. I don't have app to test.

    There could possibly be an app out there that responds to MMC and can output either Ableton Link or MIDI Beat Clock to provide a link. That might provide an alternative.

    @Michael - if you see this, the App Store description for Multitracker says that it sends MIDI Time Code (MTC) and MIDI Machine Control (MMC). Are either of these supported for Audiobus transport?

  • edited July 7

    Thank you!

    Made some progress going the other way; Audiobus start/pause gives me Start/Stop in Multitracker. The issue with this setup is that while I send Clock from inside a multitracker “song” and Audiobus is set to listen to MT’s clock, Audiobus BPM does not update to reflect that (whereas when starting from MT, Audiobus’ transport doesn’t respond, but BPM is updated).

  • I’m afraid not - those are a bit more obscure. AB/LP understand MIDI clock only.

  • wimwim
    edited July 7

    Thanks for the confirmation @Michael.

    @nobbykneeson - I've not been able to find any apps that can bridge between MTC/MMC and midi clock. You might have more luck with other such apps like Camelot Pro and KeyStage that can either host your instruments or can sync with Audiobus using MIDI Clock or Ableton Link. They're pricy but would help with your mixing goal as well. (KeyStage has a Lite version to try for free.)

    You should be able to find some background info on those two apps using the forum search.

  • edited July 8

    Thanks friends! I’m in the app, and there is a MIDI Clock option alongside MTC & MMC. With this setup, Audiobus transport controls Multitracker but the track-level BPM is not set in Audiobus.


  • @nobbykneeson said:
    Thanks friends! I’m in the app, and there is a MIDI Clock option alongside MTC & MMC. With this setup, Audiobus transport controls Multitracker but the track-level BPM is not set in Audiobus.


    With midi beat clock, tempo is derived from the received beat clock.

  • wimwim
    edited July 8
    1. You have clock out from Multitracker going to Audiobus, but you have Audiobus clock source set to Multitracker. The two ends must agree. If Multitracker clock out is going to Audiobus, then set Audiobus to listen to "Virtual MIDI" (This is what Audiobus calls its "Audiobus" port internally. If you have Audiobus set to listen to Multitracker then you need to set Multitracker to whatever it calls its own port.
    2. Turn off Audiobus midi clock send out to Multitracker. Clock should only flow one way or you may introduce instabilities.
  • Midi ports can be confusing. You might think that each app should be set to the app other app. But really, they have to be in agreement. If one app is sending to an app's named port, then the receiving app needs to be set to listen to its own port. If the listening app is set to listen to another app's virtual port then the sending app needs to send to it's own virtual port, not the other app's port.

    The situation is further confused by apps such as Audiobus referring to their own port not by name, but by something like "Virtual MIDI" or other designations.

    Once you get a feel for how it works it won't seem so confusing.

  • Thanks u/wim! Having disabled the send from AB to MT and using Virtual MIDI port within AB I am able to sync BPM, but ABs transport doesn’t respond to commands coming out of MT.

    MT is sending some CC on STOP, but according to MIDISpy, there’s nothing coming in on PLAY.

    I feel like I’m nearly there, just missing something simple.


Sign In or Register to comment.