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.

StepPolyArp as a MIDI Filter

124»

Comments

  • AndyPlanktonAndyPlankton

    @gonekrazy3000 said:

    @AndyPlankton said:

    @gonekrazy3000 said:

    @AndyPlankton said:

    @Carnbot said:

    @AndyPlankton said:
    I gave up trying this as I couldn't get Gadget to receive any MIDI coming from AB3 even through the MIDI adapter

    Plus I got distracted trying because of Future Drummer...
    I cannot get the Midi flow randomiser to work when in standalone mode and between FD and Gadget either...I get MIDI into gadget, but it is not randomised.

    I did have minor success using the MIDI Randomiser, MIDI adapter and ModStep......but the state saving not working in the adapter or randomiser meant I wasn't going to do all that again.....

    AB3 and Midiflow plugins are back on the shelf awaiting fixes for state saving

    ok right, I've not been using Gadget much so haven't tried this.

    I don't know where the issue lies, but I don't think it is SPA, seems more like Gadget receiving MIDI where AB3 is involved.

    I will do some tests for you. So what exactly are you trying to do ? Future drummer=>midiflow randomiser to mess with timing and velocity for more human feel=>Gadget ?

    Yes...exactly that

    I already did it. Look above your last post :) didn't use the standalone. The ab3 midiflow adapter works fine.

    Yes this works.and I'll use it for now, perhaps...What I don't understand is why going directly to gadget from AB3 midi adapter does not work....Not everyone has ModStep (although in my mind they should have, for exactly this sort of thing if nothing else)

  • CarnbotCarnbot

    @AndyPlankton said:

    You could probably use midiflow main app to redirect the midi too other than Modstep.
    I don't think in Gadget you can choose a port to receive from so you can only send to it.

  • AndyPlanktonAndyPlankton

    @Carnbot said:

    @AndyPlankton said:

    You could probably use midiflow main app to redirect the midi too other than Modstep.
    I don't think in Gadget you can choose a port to receive from so you can only send to it.

    You can choose ports and channels in Gadget when in the Advanced MIDI mode. I don't own the MIDI Flow app.

    I am not getting the nice comforting fuzzy feeling that these issues are or will be looked at.....just suggestions of workarounds. :(

  • CarnbotCarnbot

    @AndyPlankton said:

    @Carnbot said:

    @AndyPlankton said:

    You could probably use midiflow main app to redirect the midi too other than Modstep.
    I don't think in Gadget you can choose a port to receive from so you can only send to it.

    You can choose ports and channels in Gadget when in the Advanced MIDI mode. I don't own the MIDI Flow app.

    I am not getting the nice comforting fuzzy feeling that these issues are or will be looked at.....just suggestions of workarounds. :(

    That's weird, should work then, yes I can see now that you can select a specific port and it can see the MF adapter port.

  • AndyPlanktonAndyPlankton

    @Carnbot said:

    @AndyPlankton said:

    @Carnbot said:

    @AndyPlankton said:

    You could probably use midiflow main app to redirect the midi too other than Modstep.
    I don't think in Gadget you can choose a port to receive from so you can only send to it.

    You can choose ports and channels in Gadget when in the Advanced MIDI mode. I don't own the MIDI Flow app.

    I am not getting the nice comforting fuzzy feeling that these issues are or will be looked at.....just suggestions of workarounds. :(

    That's weird, should work then, yes I can see now that you can select a specific port and it can see the MF adapter port.

    Yes, and then no MIDI is received....same in AUM I think.

  • gonekrazy3000gonekrazy3000
    edited May 2017

    @AndyPlankton said:

    @Carnbot said:

    @AndyPlankton said:

    @Carnbot said:

    @AndyPlankton said:

    You could probably use midiflow main app to redirect the midi too other than Modstep.
    I don't think in Gadget you can choose a port to receive from so you can only send to it.

    You can choose ports and channels in Gadget when in the Advanced MIDI mode. I don't own the MIDI Flow app.

    I am not getting the nice comforting fuzzy feeling that these issues are or will be looked at.....just suggestions of workarounds. :(

    That's weird, should work then, yes I can see now that you can select a specific port and it can see the MF adapter port.

    Yes, and then no MIDI is received....same in AUM I think.

    It's strange. It seems specific to futuredrummer and certain apps. Maybe the midi is something that AUM and gadget doesn't recognise natively ? Modstep seems to work every time though so I'm happy regardless. I'm actually creating a splitter chain now so that I can get multichannel midi into gadget from futuredrummer using midiFlow scales to filter notes per layer. Still early days yet though......

    P.S:- AUM refuses to accept midi from ZMors modular but works when routed through modstep. So it's not necessarily a problem with ab3 or midiflow adapter since in that use case neither was used at all....

  • AndyPlanktonAndyPlankton

    @gonekrazy3000 said:

    @AndyPlankton said:

    @Carnbot said:

    @AndyPlankton said:

    @Carnbot said:

    @AndyPlankton said:

    You could probably use midiflow main app to redirect the midi too other than Modstep.
    I don't think in Gadget you can choose a port to receive from so you can only send to it.

    You can choose ports and channels in Gadget when in the Advanced MIDI mode. I don't own the MIDI Flow app.

    I am not getting the nice comforting fuzzy feeling that these issues are or will be looked at.....just suggestions of workarounds. :(

    That's weird, should work then, yes I can see now that you can select a specific port and it can see the MF adapter port.

    Yes, and then no MIDI is received....same in AUM I think.

    It's strange. It seems specific to futuredrummer and certain apps. Maybe the midi is something that AUM and gadget doesn't recognise natively ? Modstep seems to work every time though so I'm happy regardless. I'm actually creating a splitter chain now so that I can get multichannel midi into gadget from futuredrummer using midiFlow scales to filter notes per layer. Still early days yet though......

    P.S:- AUM refuses to accept midi from ZMors modular but works when routed through modstep. So it's not necessarily a problem with ab3 or midiflow adapter since in that use case neither was used at all....

    @gonekrazy3000 said:

    @AndyPlankton said:

    @Carnbot said:

    @AndyPlankton said:

    @Carnbot said:

    @AndyPlankton said:

    You could probably use midiflow main app to redirect the midi too other than Modstep.
    I don't think in Gadget you can choose a port to receive from so you can only send to it.

    You can choose ports and channels in Gadget when in the Advanced MIDI mode. I don't own the MIDI Flow app.

    I am not getting the nice comforting fuzzy feeling that these issues are or will be looked at.....just suggestions of workarounds. :(

    That's weird, should work then, yes I can see now that you can select a specific port and it can see the MF adapter port.

    Yes, and then no MIDI is received....same in AUM I think.

    It's strange. It seems specific to futuredrummer and certain apps. Maybe the midi is something that AUM and gadget doesn't recognise natively ? Modstep seems to work every time though so I'm happy regardless. I'm actually creating a splitter chain now so that I can get multichannel midi into gadget from futuredrummer using midiFlow scales to filter notes per layer. Still early days yet though......

    P.S:- AUM refuses to accept midi from ZMors modular but works when routed through modstep. So it's not necessarily a problem with ab3 or midiflow adapter since in that use case neither was used at all....

    I initially discovered this when sending midi from ModStep through MidiAdapter to Gadget......FD direct to gadget works fine.....the problem only happens when putting AB3 and Midi Adapters in the middle.

Sign In or Register to comment.

© Vanilla Keystone Theme 2025