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.

Question about using apps loaded in FX slots (eg Flux Pro / LFOH) as midi sources in AUM

GavinskiGavinski
in General App Discussion

I find something quite annoying about the way these are working for me. Basically it seems that any time you select apps loaded in Fx slots as midi sources to send out CC messages, any changes made to one lane will apply to the other. Sure you can get around this by changing the channels you're sending cc messages on. But why can't i just tell instrument 1 that I want it to receive midi from LFOH 1 but not LFOH 2, and vice versa, for example? I've never noticed this kind of problem when using actual proper midi nodes as midi cc sources.

Comments

  • wimwim

    Are you sure it has to do with the source being in an FX slot? I think that’s not the real issue, but the issue is you’re sending to AU parameters via AUM’s midi control system. AUM midi control system doesn’t have granular routing like that.

    If you were routing directly to apps that have their own midi handling, rather than to AUM midi control, then you could pick and choose midi sources.

    In other words, it’s the destination, not the source that is the limitation in this case.

    To see what I mean, you can put Streambyter in two input slots, then route two LFOH! instances to those individually. The results in the midi monitor will show that only one of the LFOs is affecting each channel.

    I hope that makes sense.

  • GavinskiGavinski

    @wim said:
    Are you sure it has to do with the source being in an FX slot? I think that’s not the real issue, but the issue is you’re sending to AU parameters via AUM’s midi control system. AUM midi control system doesn’t have granular routing like that.

    If you were routing directly to apps that have their own midi handling, rather than to AUM midi control, then you could pick and choose midi sources.

    In other words, it’s the destination, not the source that is the limitation in this case.

    To see what I mean, you can put Streambyter in two input slots, then route two LFOH! instances to those individually. The results in the midi monitor will show that only one of the LFOs is affecting each channel.

    I hope that makes sense.

    Thanks Wim,

    Hmm, I definitely thought i remembered that AUM did have this kind of more granular control - I'll have to take a look later, thanks!

Sign In or Register to comment.

© Vanilla Keystone Theme 2025