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.

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.