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 input apps not available as targets?

rototomrototom
in Loopy Pro

it seems that apps in midi input slots are not available as targets for actions. (effect actions)
i tried zoa, which exposes its parameters nicely in aum for example.
same for streambyter or mirack.
nix, niente, nada...

Comments

  • espiegel123espiegel123

    @rototom said:
    it seems that apps in midi input slots are not available as targets for actions. (effect actions)
    i tried zoa, which exposes its parameters nicely in aum for example.
    same for streambyter or mirack.
    nix, niente, nada...

    Not sure what you mean. I use streambyter and miRack without a problem. If you want a midi AU available as a destination, you need to add it to the mixer with Add Midi. After that it will be available as a destination.

  • wimwim
    edited February 2022

    @espiegel123 said:

    @rototom said:
    it seems that apps in midi input slots are not available as targets for actions. (effect actions)
    i tried zoa, which exposes its parameters nicely in aum for example.
    same for streambyter or mirack.
    nix, niente, nada...

    Not sure what you mean. I use streambyter and miRack without a problem. If you want a midi AU available as a destination, you need to add it to the mixer with Add Midi. After that it will be available as a destination.

    The AU parameters of the Midi FX? As targets for a widget or clip action? How? Where?

  • espiegel123espiegel123
    edited February 2022

    @rototom said:
    it seems that apps in midi input slots are not available as targets for actions. (effect actions)
    i tried zoa, which exposes its parameters nicely in aum for example.
    same for streambyter or mirack.
    nix, niente, nada...

    Oops. I just realized that i mis-read/intepreted your post. Currently, AU parameters are only visible for effects and not instruments/sources. Support for AU parameters for sources/instruments is coming. (So, miRack's parameters as an effect are addressable currently but not when loaded as an instrument.

  • rototomrototom

    @espiegel123 said:

    @rototom said:
    it seems that apps in midi input slots are not available as targets for actions. (effect actions)
    i tried zoa, which exposes its parameters nicely in aum for example.
    same for streambyter or mirack.
    nix, niente, nada...

    Oops. I just realized that i mis-read/intepreted your post. Currently, AU parameters are only visible for effects and not instruments/sources. Support for AU parameters for sources/instruments is coming. (So, miRack's parameters as an effect are addressable currently but not when loaded as an instrument.

    sorry for being unclear.
    i'm still confused by all this new loopy terminology:)

Sign In or Register to comment.