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.

Apps and MIDI

Many apps do not implement MIDI in the way I would expect.

In the hardware days I had a sequencer and I could send MIDI to 16 different devices on each of the 16 MIDI channels. Depending on the MIDI interface (with separate MIDI ports) you could send to 32, 64 or even more devices. That pretty much covered most scenarios!

I wonder if some of todays devs never had hardware so they don't get how MIDI worked back in the old days? There usually wasn't any need to re-channelize the MIDI stream as seems to be the answer with a number of todays apps. Anything with MIDI should have a way to set a send and receive channel.

The way MIDI works is actually pretty simple but it seems the implementation of it in many iOS apps is unnecessarily convoluted.

Comments

  • edited December 2015
    We're going to fix some of this with Audiobus 3.

    In the mean time: The reason for this is the structural design flaw of CoreMIDI in iOS, which requires every app to have a MIDI configuration section, which means there are almost unlimited ways to set things up. That leads to misconfiguration by users and also misinterpretation by developers.
  • edited December 2015
    Auria Pro comes out and the next day Audiobus 3 enters my mindstream, endless anticipation...
  • We're going to fix some of this with Audiobus 3.

    In the mean time: The reason for this is the structural design flaw of CoreMIDI in iOS, which requires every app to have a MIDI configuration section, which means there are almost unlimited ways to set things up. That leads to misconfiguration by users and also misinterpretation by developers.
    Thanks Sebastian

    I think MIDlfos and MIDIsteps have one of the best implementations of MIDI routing. Very straightforward.
  • edited December 2015
    All have thier own specialty in terms of midi apps, depends on situations
  • edited December 2015
    @anickt said:

    I think MIDlfos and MIDIsteps have one of the best implementations of MIDI routing. Very straightforward.
    Indeed. This is the case with all of @artkerns apps. That's the UI the world should emulate (and many do have similar UIs).

    But to sebastians point:
    In the mean time: The reason for this is the structural design flaw of CoreMIDI in iOS, which requires every app to have a MIDI configuration section, which means there are almost unlimited ways to set things up. That leads to misconfiguration by users and also misinterpretation by developers.

    So. Very. Particularly the case with virtual ports. It's absurdly easy to send/receive double MIDI messages on iOS. I'm not sure if within my first ~20 pre-iOS MIDI years I'd ever run into the "double clock messages = double the tempo in the receiving app" thing whereas it seems to come up here on the forum once a week.

    I'm looking forward to whatever you guys have up your collective AB3 sleeves. Can you let reveal if it will be MIDI routing generally or sync focused only?


Sign In or Register to comment.