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.
Can someone explain MIDI on the iPad?
I'm using AUM, Modstep, AB3, Gadget, Module, Animoog and some hardware units - getting some very strange behavior when I try to record MIDI into Modstep (and other configurations). I think part of the problem is that I just don't understand how MIDI actually works with all of these components. Do I route MIDI in each app and also through the MIDI router in AUM or in just one of those? It seems like some of these work fine just routing MIDI in AUM, but others require me to set up the links in the apps themselves (and sometimes in AUM as well). When setting up the apps, to I use the Network Sessions or the apps' MIDI ports? It's all very confusing . . .
Comments
Midi is far from standard on ios. You have 2 midi systems explained here..... https://forum.audiob.us/discussion/7338/virtual-midi-vs-coremidi-midibridge-getting-apps-to-talk-listen
In the apps sometimes you connect to the apps output port or sometimes you connect to the hosts port. Lots of host apps require that you make the recording channel 'active'. Only have one midi clock source or the clocks start doubling etc. Midi sync has lots of advantages thats why, (I cant imagine any other reason), they dont want us to be able to do it. Then there's Link and then there's Autobus 3 will solve all the above (when the developers conform to the standard)
Midiflow is a killer app buy it and read the manual and you will be enlightened.
Today I woke up with an amazing idea and then spent 3 hours debugging weird audio glitches and midi timing errors while trying to sync external gear. I sent two support emails and in the end got a 2 min jingle down. It aint easy
Your last statement kinda sums it up...MIDI (on iOS) can be very confusing. MIDI is a standard but the implementation for iOS is not. That's what Audibus 3 is trying to alleviate...but it's early days yet.
I haven't used ModStep much, but for me, I use Cubasis for all my MIDI recording...sometimes the input is from an external keyboard, sometimes from a synth app (that obvisouly has MIDI output...not all do), and sometimes I use the Cubasis keyboard...and usually I do one track at a time.
For MIDI routing, there are so many ways to go via AUM or AB3, or a DAW; and rather than attempt an explanation (others here will probably do that), I'd suggest working with a limited set of apps and get that working and expand from there. I've gone through a lot of trials and errors to get somewhat comfortable with the midi, but I still get baffled when an app doesn't work they way I wanted/expected.
This may not be helpful at all, but mostly I wanted to chime in and let you know that you are not alone; it can be a frustrating experience.
Sigh - I was afraid these were the answers I was going to get :-) I'd really like to minimize the number of apps I have running, but it looks like there's currently no easy way to do this with one simple solution (hopefully more apps will conform to the AB3 MIDI standard soon).
I forgot to mention that I'm using Navichord and StepPolyArp as well . . . more complexity.
Good suggestion to strip it down and build up the complexity as I get components to function.
The bad news? No. The good news? It's getting better. @TozBourne has some good suggestions to break through the wall of WTF, as per usual
Thank you kindly.
I should mention that with AB3, I've had a lot of fun recently using MIDI. I have a keyboard that can send on up to 3 midi channels (split and dual settings)...add that with the MIDIFlow Splitter to drive even more apps, plus the audio out from the keyboard; and I've had a bunch of sounds stacked up all at once...kinda like my own version of that Layr app I guess. But before AB3, this is something that I just couldn't get to work.
Maybe this calls for a video series on midi iOS. strokes beard
So strange that recording egoist midi into cubasis results in a corrupted Cubasis project file.
What's helped me the most is searching out the various Apple documentation. Randomly - there's Core Midi for iOS, and Os, which hav differences, there's IAA Midi, Network, Bluetooth, USB - so too with Audio protocols - and that most the protocols allow variances for developers, who as well can make other choices that are confusing. I decided to take the long approach and learn them best as possible - another is to settle on a few with the functions you need and master their workflows to a reliable extent for your goals. Either way, I try think of it as learning to play the instrument, and there's ample ways to be creative and unique, and have requisite Midi meltdowns along the way.
I haven't tried it yet but http://www.midiflow.com/audiobus/adapter/ might help you get older apps to conform to your AB3 set up.
Hmm, missed that one. Looks like it could come in handy with AB3
That be cool. One based solely on Apps ( no external hardware or audio interfaces ) would be helpful. Nothing against the hardware gear, but having it out of the picture might make it easier to understand ?
Or a series of shorter videos where each adds a layer of complexity to the same set up, sort of like @TozBourne's solid advice. Using the same setup will allow viewers to follow along and likely introduce non-contrived complexity to work out in real time. You could then add MIDI hardware later without it getting in the way of the initial core concepts.
I think the OP's apps are probably a good set to with.
You can get into routing in AUM, recording into Modstep, routing Navichord or SPA to an app and recording it into Modstep, MIDI clock and/or LINK... several of these apps also have both virtual and core midi support.
@Kiki_90291 Here's an approximate approach, open for criticism, and appreciating/anticipating the take of @gmslayton ...
AudioBus3, Aum, Modstep, midi keyboard and external controller.
In ab3 midi window, connect navichord to midiflow adapter, mfa to beathawk auv3, steppolyarp to mfa;
in the ab3 audio window connect BH au to Aum and insert modstep as input source, without an output in this case.
In Aum, setup sends & buses. (See https://forum.audiob.us/discussion/18749/your-favorite-fx-in-ios#latest)
In Modstep, select the midiflow adapter inputs & outputs, keyboard and controller on seperate lanes. Here I chose [mfa1 out] coming from navichord on say ch. 7, [mfa2 out] coming from steppolyarp on ch.8, to go out to [mfa3 in] sending on ch. 1, which is the beathawk au.
Modstep can record/replay navichord as well as the keyboard, steppolyarp and controller performances notes and cc messages.
The arbitrary cc's 34 and 20 have been assigned in modstep to the mod area, and midi-learnt from a controller knob movement in audiobus/beathawk on the filter (cc20) and in Aum (->select midi sources: Aum Destination and virtual modstep port, go to -> midi ctrl, chan.4, reverb parameters, midi-learn wet=cc34).
For this the only routing in Aum that will be done is by connecting the virtual 'modstep' output port (upper row=inputs) to 'midiflow adpter 3' and Aum 'midi control' (side=destinations) as well as the 'Aum Destination virtual port' to 'midi control', because the external controller is rerouted in modstep virtually, and thus can affect several destinations, the instrument au in ab3 (through midiflow adapter out 3) and the effect au in Aum (destination).
Another way of relaying a cc control message (cc1) is going directly from steppolyarp (modulation) to the instrument au. Tap a key on its internal keyboard or latch the arp.
If you would like to manipulate an iaa effect parameter like aufx:dub f.e., connect the virtual modstep port to 'Aufx:dub midi @ chan.2' destination.
Greetings & cheers
I guess I need to break down and purchase AB3 and Step Poly Arp. I have some of the other apps or I can supplement.
@heybail I like the idea of no external midi to start with
@syrupcore I really like the idea of a series, building up the setup with each video.
@ccs2 I will need to get AB3 and explore it. I have done some pretty complex midi routing without the need for an intermediary app but AB3 looks to simplify things. Even open things up to more complex midi routings.
@gmslayton Yeah, also Audiobus3 and Aum are going to be updated soon with improved integration and compatibility.
Thanks for all the input - this has been really enlightening.
@ccs2 - a couple of questions about your example: why do you run your keyboard controller into Modstep directly - couldn't you just run it into AB3?
And if I understand how you're routing MIDI, it look like your basically using MIDIFlow adapter to tap the MIDI signals into Modstep and record them (i.e., SPA, Navichord and the keyboard) and while also sending MIDI directly to Beathawk? Or am I missing something? I think the MIDI routing part in AUM is confusing me. (I don't have MIDIFlow Adapter yet, so I don't fully follow how it works).
Thanks again to all - I'm learning a lot!
@Kiki_90291 going into some details,
I loaded the apps in question into the audio-inputs of Audiobus3
with the outputs directed at Aum, both going into bus1 and that into bus2, (the send amount cc controlled, see below)
modstep being the midi-hub, the keyboard goes in on ch.1, the bcr on ch.2, both outputting to aum; navichord and steppolyarp pointing to two gadget synths, (the channels and ports being set in-app)
'aum virtual destination' is the counterpart input port, which will relay the keyboard and controller from modstep to the destinations you can see selected here, animoog (virtual), gadget (virtual), the internal midi control and steppolyarp, because in this use-case I'd like the keyboard play animoog, a gadget instance and also input notes to steppolyarp
animoog receiving on ch.3,
steppolyarp receiving on ch. 3 too, source set to 'modstep'
the destination steppolyarp will send to is gadget on ch.4
gadget is receiving with its own gadget(virtual) ports on its channels 1 (darwin from navichord), 4 (chiang mai from steppolyarp via keyboard) and 3 (salzburg from aum via keyboard)
navichord's chord voices are triggering on ch.1 over its virtual output port
the send amount from aum's bus has been midi-learnt by moving a knob on the controller
also I'd like the filter eg amount in chiang mai being steered by steppolyarp's modulation (cc01)
it goes out on ch.4
Now, it's different from the ab3 & midiflow thing, and not the most visually appealing with the ab sources in Aum not being represented, but you can name and mix the tracks accordingly, and everything's linked and you can record the midi, start/stop from ab side-panel and state-save ...
I think I understand the data flow now, but I have to say that I find it all very disappointing - MIDI on the iPad is a mess! The various apps seem to work ok on their own or in simple combinations, but once you get to more complicated setups, they get really flaky. Hopefully the apps will become more stable over time, but having to use 3-5 apps (that don't necessarily play well with each other) just to handle MIDI and audio data is not worth it - I'm spending 15-20 troubleshooting every time I try a different combination . . . I'm finding myself just defaulting to using Modstep and hardware sound sources throwing in the occasional StepPolyArp or Navichord (but never loading them in Modstep). I've also been killing Ableton Link as it doesn't let you assign a master clock.