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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
High resolution 14-bit MIDI automation
Classically, MIDI only handles automation data with 7 bits (128 steps) of precision. It seems there are a variety of methods for surpassing this limitation. MIDI 2.0 provides a robust solution for handling 14-bit automation, but unfortunately very few applications have implemented support for MIDI 2.0 so far. Alternatively, there are techniques for implementing MIDI messages with more than the usual 7-bits of precision that do not depend on full MIDI 2.0 support. For instance, Non-Registered Parameter Number (NRPN) messages can be configured to provide 10-bit resolution in MIDI.
I am now looking into ways of using whatever tools are available to transmit high-resolution MIDI automation data on iOS/iPadOS, ideally using an AUM-compatible workflow. @woodman's WoodSynth and WoodTroller apparently support MIDI 2.0, so they could be one used for testing. ShowMIDI seems to be another app usable for testing, with the latest update providing "improved handling [of] Hi-Res 14-bit CC value logic". I haven't purchase all of these apps yet, so I cannot test them together. But based on the information available to me, I believe I would still need to find an app with support for recording/drawing in hi-res MIDI CC automation. Does anybody here know of an app that could provide that functionality? I'm also interested in learning about other ways of sending hi-res MIDI automation data that I should look into.
Comments
The stick in the mud is AUM. Even if you can send 14-bit midi, it can't make use of it for parameter automation. (The exception is pitch bend). Not many hosts can.
btw, 14bit midi doesn't need MIDI 2.0. It's been a part of MIDI 1.0 for decades.
For recording 14 bit midi, the most accurate are likely to be Midi Tape Recorder and Xequence 2, but most recorders should capture it fine, since 14Bit midi is just regular 7 bit midi sent and interpreted across two midi CC's (one for the coarse adjustment, one for the fine).
In other words, the problem isn't capturing 14 bit midi, the problem is being able to use it.
Show MIDI is free btw, but it's only useful for monitoring.
https://forum.loopypro.com/discussion/56679/can-aum-translate-14-bit-cc-messages-to-fine-control-plugin-parameters
https://forum.loopypro.com/discussion/39202/how-to-get-higher-res-control-when-mapping-parameters-to-midi-controllers
Wondering if you would know the answer: If I was using Xequence 2 for the MIDI and fed that to an instrument hosted in Loopy Pro would the instrument see the full 14 bit/MPE version or a stripped down variation?
Just asking for a friend.
It should see the whole thing. Whether or not the target app can do anything with it is the critical question. AUM's AUv3 parameter control system can't. Most apps' internal midi system can't either.
Here's a thread from the Beepstreet forum
where the focus is on 14 bit input.
http://forum.beepstreet.com/discussion/2217/14-bit-midi-input/p1
Earlier this month Jonatan Liljedahl from AUM confirmed that "14-bit MIDI cc is on [his] TODO list." So hopefully this stick gets cleaned up before too long!
In any case, I believe that even AUM's lack of support for 14-bit MIDI CCs shouldn't necessarily prevent 14-bit MIDI from being used in an AUM-based workflow. Some apps, such as WoodSynth, have built-in options for assigning incoming MIDI CCs to the synth's parameters, effectively giving us a way to circumvent AUM's MIDI mapping system. I think instances of WoodSynth hosted within AUM should be able to respond to 14-bit MIDI CCs (if everything else is configured properly) as long as you use WoodSynth's internal CC mapping system. But I haven't been able to test yet, since I don't have a way of sending 14-bit MIDI CC messages.
Just a couple of notes here.
The Moog apps, Model D and Model 15, can MIDI-map a 14-bit CC. You can MIDI Learn it, or just edit the mapping to enable 14-bit. Not sure about Animoog Z tho.
You can use Pitch Bend messages to get 14-bit control of an AUv3 parameter in AUM. You probably need a script (Mozaic or StreamByter) to generate PB messages. Route its output to MIDI Control in AUM. Then you can select PBEND as the modulation source for a parameter.
Thanks @wim for pointing to Xequence -- it can send (N)RPNs with 14-bit resolution, and indeed routing those through AUM to another plug-in hosted inside AUM should work independently of AUM supporting them or not, as it essentially should just be passing on the data unchanged to the plug-in.
So if the plug-in DIRECTLY supports mapping incoming 14-bit NRPNs to its parameters (NOT via AUv3 automation!), it should work with Xequence.