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.

The Audiobus Forum is now the Loopy Pro Forum!

In case you didn't see the announcement thread, I have some big news: Audiobus – the app – is going to a new home. Francesco and Andrea are developers and musicians who are keen to pursue Audiobus’ further potential, keep it updated and enhance the experience for users old and new – and unlike me, they have the resources to do so! They’re full of ideas and energy, and I am confident that Audiobus will be in good hands.

The Audiobus Forum, however, is staying right here with me. After some consultation with the community here about what to do, I've decided to rename it to the Loopy Pro Forum, at forum.loopypro.com.

It has a new name and new colours, but otherwise, it's the same place, and nothing else will change.

Cheers,
Michael

MIDI Routing

slicetwoslicetwo
in Loopy Pro

Right now, I use AUM as my host for LP as an AUv3 due to AUMs amazing MIDI routing capabilities (filtering channels, connecting hardware directly to each other, etc.). Is this something that Loopy Pro is a contender in yet, or is AUM still my go to?

Comments

  • wimwim

    Loopy Pro can do all the midi routing most people would ever need. It's not as intuitive or quick to set up as AUM, but you get used to it. It doesn't have the more advanced filtering of message types that AUM now has, and it doesn't have midi busses.

    tbh, I don't especially enjoy setting up midi in Loopy Pro but it gets the job done.

  • espiegel123espiegel123

    @slicetwo said:
    Right now, I use AUM as my host for LP as an AUv3 due to AUMs amazing MIDI routing capabilities (filtering channels, connecting hardware directly to each other, etc.). Is this something that Loopy Pro is a contender in yet, or is AUM still my go to?

    It depends on which filtering options you actually need. AUM has some built-in options Loopy doesn’t have. If you make use the the options loopy doesn’t have, you may have a midi AU that can be used to work around that … but most people probably don’t use the missing filtering.

    Which filters do you need?

  • slicetwoslicetwo
    edited January 5

    @wim @espiegel123 I struggled to find where in the app I could do the MIDI routing directly from one hardware port to another. In AUM we have that lovely matrix.

    Filtering wise, it's all over the place depending on the device - channels, notes, transport, clock, etc.

  • wimwim
    edited January 5

    Routing from one hardware port to another shouldn't be a problem. You'd need to use something like mfxConvert, Mozaic, or Streambyter for filtering other than just by channel.

    Humm ... that gives me an idea for a quick and flexible Mozaic filter script. Think I'm gonna play around with that today.

  • espiegel123espiegel123

    @slicetwo said:
    @wim @espiegel123 I struggled to find where in the app I could do the MIDI routing directly from one hardware port to another. In AUM we have that lovely matrix.

    Filtering wise, it's all over the place depending on the device - channels, notes, transport, clock, etc.

    Add each device that will be a source to Loopy’s mixer using Add Midi. To send from one port to another, add the port you are sending to as a destination of the source.

  • espiegel123espiegel123

    Tap on the add destination icon, to add any available MIDI destination for the source.

  • slicetwoslicetwo

    @wim @espiegel123 Ok. So literally every single channel needs it's own mixer column in LP? Colors, MIDI, Instruments, etc? Are the channels collapsible or groupable, or do you just have an endless scroll of channels in a big project?

    Thanks for the tips!

  • espiegel123espiegel123

    @slicetwo said:
    @wim @espiegel123 Ok. So literally every single channel needs it's own mixer column in LP? Colors, MIDI, Instruments, etc? Are the channels collapsible or groupable, or do you just have an endless scroll of channels in a big project?

    Thanks for the tips!

    What do you mean by “every channel needs its own mixer column”? Each source device needs a column. Not every channel.

    Currently there isn’t collapsing channels.

  • wimwim

    @slicetwo said:
    @wim @espiegel123 Ok. So literally every single channel needs it's own mixer column in LP? Colors, MIDI, Instruments, etc? Are the channels collapsible or groupable, or do you just have an endless scroll of channels in a big project?

    Thanks for the tips!

    Yes. But you never have to visit the mixer unless you're ... mixing (or adding plugins or inputs). All your apps can be sitting at the bottom of the loop screen to be opened/closed or disabled with a touch. You can also make your own mixing screen with widgets if you like. Once you've recorded to a clip, each clip's volume can be controlled without opening the mixer screen. It's a different way of working, and not for everyone.

    Mixer channels are grouped by Midi source, colors, and busses. They're not collapsable.

    The mixer isn't my favorite place to be for sure. But I generally keep it closed and don't need it.

  • espiegel123espiegel123

    It is not the case that every midi channel needs its own mixer column. Perhaps there are use cases where that might be true but it isn't generally true.

  • wimwim
    edited January 6

    I don't think Midi channels were what was being asked about. "Channels" in AUM are generally referred to as what we would call "Inputs" in Loopy Pro. I think the question is whether every input and color has to be a mixer channel, which is true. Also every midi input and every send.

  • espiegel123espiegel123

    @wim said:
    I don't think Midi channels were what was being asked about. "Channels" in AUM are generally referred to as what we would call "Inputs" in Loopy Pro. I think the question is whether every input and color has to be a mixer channel, which is true. Also every midi input and every send.

    I asked for clarification because it isn't clear to me what was meant. The question was "every channel needs its own mixer column", it sounded to me like he might have meant midi channel.

  • slicetwoslicetwo

    @espiegel123 said:

    @wim said:
    I don't think Midi channels were what was being asked about. "Channels" in AUM are generally referred to as what we would call "Inputs" in Loopy Pro. I think the question is whether every input and color has to be a mixer channel, which is true. Also every midi input and every send.

    I asked for clarification because it isn't clear to me what was meant. The question was "every channel needs its own mixer column", it sounded to me like he might have meant midi channel.

    In LP, it seems that all channels/instruments/mixer lanes/etc are individual "mixer" columns, where is in AUM, it's all kind of separated. Y'all have basically answered all my questions, for now, I think :)

    Thanks!

Sign In or Register to comment.