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.

How to get Taipei to control another Gadget?

No problem using Taipei on external gear or other apps, but can’t get it to work within Gadget.

Have tried lots of things including routing via audiobus but it seems like the obvious should work:

Taipei: MIDI Output set to Gadget/ch.1 (also setting midi input to off in case of feedback loops)
Would-be receiving Gadget: MIDI Input set to Gadget/ch.1

But nothing...

thanks for any tips

Comments

  • Why would you want to do that? When you can control the gadgets within Gadget already?

  • edited November 2019

    @ExAsperis99 said:
    Why would you want to do that? When you can control the gadgets within Gadget already?

    so you can swap from using a gadget, to using an external synth, and back again by changing the MIDI routing.
    You can swap by changing the gadget itself, but you lose any preset or parameters you may have changed in the gadget...
    Another alternative is to create duplicates of all tracks, have one copy routed to a Gadget, and the other to the external MIDI....but then you need to echo any edits you make to the patterns....

  • @AndyPlankton said:

    @ExAsperis99 said:
    Why would you want to do that? When you can control the gadgets within Gadget already?

    so you can swap from using a gadget, to using an external synth, and back again by changing the MIDI routing.
    You can swap by changing the gadget itself, but you lose any preset or parameters you may have changed in the gadget...
    Another alternative is to create duplicates of all tracks, have one copy routed to a Gadget, and the other to the external MIDI....but then you need to echo any edits you make to the patterns....

    You can also just swap the gadget on the same track whenever you want.
    (Function > Change)

  • @rs2000 said:

    @AndyPlankton said:

    @ExAsperis99 said:
    Why would you want to do that? When you can control the gadgets within Gadget already?

    so you can swap from using a gadget, to using an external synth, and back again by changing the MIDI routing.
    You can swap by changing the gadget itself, but you lose any preset or parameters you may have changed in the gadget...
    Another alternative is to create duplicates of all tracks, have one copy routed to a Gadget, and the other to the external MIDI....but then you need to echo any edits you make to the patterns....

    You can also just swap the gadget on the same track whenever you want.
    (Function > Change)

    Yes, I said that already

    You can swap by changing the gadget itself, but you lose any preset or parameters you may have changed in the gadget...

  • edited November 2019

    @GoesTo said:
    No problem using Taipei on external gear or other apps, but can’t get it to work within Gadget.

    Have tried lots of things including routing via audiobus but it seems like the obvious should work:

    Taipei: MIDI Output set to Gadget/ch.1 (also setting midi input to off in case of feedback loops)
    Would-be receiving Gadget: MIDI Input set to Gadget/ch.1

    But nothing...

    thanks for any tips

    You're almost there but you forgot one thing: Loop back the MIDI data!
    Like in real MIDI world, the two cable ends won't find each other automagically unless connected to each other.
    I'm using MidiFire for this but any app that will loop back MIDI should work.

    Edit: Yes, FreEWI is still available too from our top notch developer Audeonic :smiley:

  • As for why - Arp, LFOs, XY pad on Gadgets that don't have them...

    @rs2000 said:
    You're almost there but you forgot one thing: Loop back the MIDI data!
    Like in real MIDI world, the two cable ends won't find each other automagically unless connected to each other.
    I'm using MidiFire for this but any app that will loop back MIDI should work.

    Are you saying another app is necessary?

  • @GoesTo said:
    As for why - Arp, LFOs, XY pad on Gadgets that don't have them...

    @rs2000 said:
    You're almost there but you forgot one thing: Loop back the MIDI data!
    Like in real MIDI world, the two cable ends won't find each other automagically unless connected to each other.
    I'm using MidiFire for this but any app that will loop back MIDI should work.

    Are you saying another app is necessary?

    Yes. If you send to the Gadget MIDI port, the midi data will leave Gadget on its MIDI output.
    If you receive from the Gadget MIDI port, data sent to its MIDI input will be catched, but what will link output to input? Gadget would need an option to do that because normally, you don't want MIDI loopback (like when using a MIDI keyboard to record and control external gear at the same time).

  • @rs2000 said:
    Yes. If you send to the Gadget MIDI port, the midi data will leave Gadget on its MIDI output.
    If you receive from the Gadget MIDI port, data sent to its MIDI input will be catched, but what will link output to input? Gadget would need an option to do that because normally, you don't want MIDI loopback (like when using a MIDI keyboard to record and control external gear at the same time).

    Perfect - thanks! I ran gadget to gadget in audiobus midi and all good

Sign In or Register to comment.