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.
Comments
@eustressor I'd love if everyone used MIDIbus. However, the MIDI layer of Midiflow is a lot more complex than what MIDIbus offers, that's why it is no option for me. However, I recommend the SDK as often as I can since my apps suffer from bad MIDI implementations in other apps. I'd also like to contribute to the SDK myself and have been in contact with the dev some tome ago because I have some ideas.
Yes, a global clock would be convenient, but it would also break the simple structure of the app. E.g. how should the monitoring of the clock signal work (where would it be visible)? That's why I have a different approach in my mind: There could be a node called "All" in the destinations list. Once selected, the routing would send to all MIDI out ports. This could be used for all kinds of MIDI data, not only for clock.
@Johannes One clock to all destinations works for me!
Looking good. I like the individual clock lanes. I also like the 'all' idea as an addition.
Is that top center bar with a drop down arrow indicating presets??
Yes, Midiflow 2.0 has a lot of new features, including presets. It's currently "waiting for review".
@JohannesD Sorry if this is redundant, but I'm curious if you have a published feature list for 2.0. If not, I can wait.
That's very good news! Thank you @johannesD. I'll give it a shot.
Midiflow 2.0 will have the following new features
Wow. Well done! Are all of the new features from Velocity Filtering on downward stored in the preset?
Velocity to CC sounds really intriguing. If it's note-per-CC, you could make a synth loose it's fucking mind with that—in a good way! Being able to use text files/numbers is a really nice touch.
Purchased. Looking forward to the update.
Yes.
I'm not sure what you mean. Well, you can remap the note number to a controller. With a monophone synth, you can use that to add a pan effect depending on the note, for example.
Got you. That's still a neat feature as many synths don't support direct control of it. Similar to aftertouch.
I was imaging the velocity from note 37 could map to cc37 and from note 38 to CC22... A simple melody could make a synth go nuts. It would of course be pretty random. Not a request! Just clarifying what I thought you meant.
And hurray for saving all of that in presets.
Ok! You can still do that with a couple of routings, one for each note
If I can secure the right drugs and a night without children, I just might try that.
Wow, that is a nice feature list.
@JohannesD for someone using iMIDIPatchbay to control apps and not external hardware, is MIDIFlow more suitable? It seems to be getting features that iMP doesn't have (yet).
Thanks for the awesome apps! I just did my first gig with iMP and it worked flawlessly
Sorry for the late answer, I don't know why I this forum sometimes won't send me a notification about a new reply...
Good question!
iMIDIPatchbay is best for you if you have the following situation:
one or more master keyboards
you want to assign different sounds to key zones on those keyboards
you want to use controllers (pitch bend, sustain, etc.) for those sounds independently from where those controllers are physically attached to (e.g. you want to use one sustain pedal for alle the keyboards)
you need quick control over which controllers influence which sound (e.g. when layering two sounds, only one of them should respond to sustain)
you may want to organize songs in a setlist
you may want to attach pdf documents to each song, e.g. sheet music or notes
Midiflow is for all kinds of MIDI tasks, not only for keyboardists. Over time, I'll integrate the new remapping features to iMIDIPatchbay, too. So, the two apps will be different in the workflow, not in the pure functionality.
Just wanted to let you know that Midiflow 2.0 is out now!
https://itunes.apple.com/us/app/midiflow/id879915554?mt=8&uo=4&at=1l3vbAX
Congrats on the 2.0 @Johannes. Looking forward to kicking the tires.
Thanks for hammering away on your development, @Johannes. Just read the new features ... So if an app only supports Omni mode (M3000 comes to mind, IIRC), it won't work with MidiFlow?
I don't know the MIDI capabilities of those apps, but yes: If an app receives on all channels and ports, Midiflow cannot address it independently from other apps.
One question, will it allow me to send clock to Gadget from apps it won't work with in AB?
@JohannesD thanks for the info! It sounds like MIDIFlow probably suits my purpose better (all software synths) so I guess I'll be buying that when I get home
Also important for connectivity is if an App is promiscuous or not. "Promiscuous"" means it grabs and listens to all ports with no options for selectivity. Korg Apps tend to this pathology, for example. An omni only App that nonetheless has port selectivity is not totally useless, though depending on the rest of your setup might be tricky. For example, with iMini (prior to the latest update), FreEWI was commonly required to allow it to be played by other Apps such as Beatmaker 2; FreEWI has channel filtering so that could be used to compensate. MidiFlow also has channel filtering, so will be useful for non-promiscuous Omni only Apps, as long as they have fnctional Virtual MIDI In ports (iMini still does not).
Midiflow lets you create virtual ports so I guess that would help?
Can anyone confirm about Gadget? Also could Gadget send clock to Lemur via midi flow? Can you pretty much freely send midi and clock between most if not all apps that will receive it? Thanks!
Midi flow starts Gadget, no problem. Gadget can't start Lemur as it doesn't send clock. I think you can send clock,to both Gadget and another app, such as Lemur, but I haven't tried Lemur and clock sync.
Thanks. Yeah Gadget is a bit closed off in that respect. Anyway Gadget shows up in Lemur so it should work in principle. Great thing abvout this app is it allows to use any app that sends clock as the master, i do find some combinations not to work well together in AB.
@soundklinik i got that impression but i can see the similarities with being able to save and recall configurations, once i've got a few setup and saved should be as simple as opening AB and midiflow to make the connections.
JohannasD thank you for being such an active and open developer! I'll be purchasing Midiflow 2 in just a moment!
Lt030