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
I tried just on the iPad with bleass alpha hosted in loopy pro. I could post a video later.
I haven't tried the android version connected to a pc, yet, but will try that later, too.
@tyslothrop1
Thx. I really appreciate your feedback.
No problem, I really appreciate your app and all the work you’re still putting into it.
Here’s a screen cap of the iPad version and the problem I’m having, I’ll check android later.
The Android version works really well, love all the new additions:)
Hey @tyslothrop1 . Thx for the vid. I tried to replicate it on my iPad with Bleass Omega, since I don't have Alpha, and it works for me.
Could it be a problem with Alpha and external Midi? Have you tried a different instrument?
I've also used midispy to log CC messages and it seems seamless when looking at the log afterwards. Very strange indeed 🤷
Edit: I remembered you are using loopy Pro. Maybe the issue is there?! I was just directly connecting to Bleass Omega. I might play with Loopy as well to see if I can pin it down.
Edit3: Still works through Loopy for me as well. Not sure what I can do if I can't reproduce this problem. Sorry 😐
Hey @anzbert, sorry about that, tried bleass omega and it's all working. Next time I'll try more than one synth, but I'm pretty sure, it used to work fine with alpha.
I played a bit more with the android version and synths in Ableton. With many it works very nicely. from what I tried Ableton wavetable, some cherry audio synths and dawesome abyss work flawlessly.
With others like surge xt, vital and Tomofon, I get many stuck notes. With surge and vital they disappear, when I open the options screen in midi poly grid, with Tomofon not. Actually with Tomofon a couple of times, it was the first played note that stayed. Tomofon works nicely with midi poly grid on iPad by the way.
I'll play a lot with this, thanks again for this cool controller!
Glad to hear it's working now. Regarding the stuck notes, I'll also play with the app a bit more with different synths and see how to troubleshoot and pinpoint that behaviour. MPE is very weird in how it requires a lot of midi channel management. It really feels like a tacked on solution to the ages old midi protocol in how it is implemented.
I wonder what midi 2.0 brings to the table in that regard. But judging by the pace of adoption so far, we can probably start using it in our setups in about 20 years with our devices haha
Multiple choice with MIDI 2.0, remains to be seen which bits catch on. At least 3 different options for this stuff in a MIDI 2.0 setup:
1) Same MPE that we are used to, except with MIDI 2.0 in general you can have 16 groups of 16 channels each, so MPE eating up lots of channels is much less of an issue.
Or
2) MPE Profile for MIDI 2.0. Does some auto-configuration stuff because with MIDI 2.0 communication is bidirectional. Allows multiple 'MPE Zones' rather than just a lower and upper zone, so you can have more than one keyboard split. Sticks to MPE things like individual MIDI channels for each note, but we have the aforementioned much higher number of channels to play with. Same use of pitch bend, channel aftertouch and CC74 messages as in traditional MPE, although there is an option to switch two expressive dimensions to use registered parameter number messages instead of channel aftertouch and CC74, increasing the resolution of those dimensions of expression to 14 bit.
Or
3) Full blown MIDI 2.0 per-voice parameters. Doesnt rely on multiple channels like MPE does, much higher resolution (32 bit if I recall correctly), far more different expressive modulations per note possible. I've not looked at all the technical documentation for this option yet, unlike the first 2 which I have read up on properly.
Option 3 is the most powerful but is a significantly bigger leap for developers. Option 2 is a sort of half way house bridge between two worlds, between two eras of MIDI, and will be easier to implement for developers that already have MPE built into their device but are looking to start to add some MIDI 2.0 stuff without breaking all the old paradigms.
Hard to predict the pace of adoption for options 2 or 3. Option 3 may require other sources of momentum to make it worth adopting, eg if hardware expressive controller and synth manufacturers start to make designs that use more dimensions of expression, and/or use much higher resolution. 2024 should start to see an uptick in the pace of available devices that support certain parts of MIDI 2.0 (delays till this point include waiting for Windows support) but when any MPE/expressive-relevant parts of the spec get baked into products and apps is hard to predict. A lot of the bigger companies are likely to focus on the auto-config aspects of MIDI 2.0 to start with, its less clear how quickly they will start to take advantage of other stuff. So far aside from the auto-config stuff, its mostly been Roland touting a keyboard that has much higher resolution note velocity messages. As I'm not an insider I dont know if events like Superbooth will feature more exciting MIDI 2.0 products or not, and even if there are some its going to take time for the ecosystem to emerge.
Thanks for this app and for making it open source. I just bought it to try on an an ipad mini, and I will probably look at the source code at some point too.
Thx @SteveElbows for the detailed info on midi 2.0. at some point I'll also have to get into the spec as well. And thx for getting the app. I am not really making money with it, but any purchase helps to cover the yearly apple developer fee. I don't mind though, since it's just a labour of love project anyway
My hourly wage for the dev time must be something like 1$/h at this point 😂, and that's ok!. I am a firm believer though that not every hobby needs to become tainted by needing to be profitable! And I'd like to give back to the community with it being an open source project. I've benefitted from generous open source Devs all my life and I am happy to return the favour.
I made the app initially just for myself, since I always wanted to have a lightweight midi input device for my laptop. That's when I was at uni and procrastinating in the library with Ableton, instead of studying.
Nowadays, I like to use it with my iPad mini as well. Not really as an inter-app controller, since all that app switching annoys me a bit. But more like a midi controller for external aynths with a USB C to Midi din cable, or via USB C to the MacBook to control VSTs in Ableton.
New update:
Live on Android now and will be live on iOS in the next 24h.
Enjoy!!
Another update that will be live in the next 24h:
I've added the program change layout so i can change patterns on my SP404MK2 to not have to switch to the pattern screen while i am messing with FX and samples. works well for me
Hope its useful for others too in some way!
Thank you @anzbert
Hey guys. long time no update.
I released a number of small patches over the last year, but now there is a major new feature. Bluetooth Midi support!
Thanks to @Gavinski for testing and lots and lots of great suggestions!
Have fun
Thnx Andreas, really appreciate your work on this wonderful app!
Thank you @anzbert! It’s a great app, glad you’re still working on it.
I wonder if it would be possible to make it split screen/slide over compatible… Probably difficult to implement?
Oh cool, so I don't have to activate Bluetooth in another app anymore, when using 2 iPads, will check it out later.
@anzbert would you consider adding Splitview? It would be so cool to have midi poly grid next to loopy, especially once the midi update drops. It can already be configured to layouts for melodic playing, that would be very usable, if you just cut the half off. And drum pads would work like a charm.
I have no idea, how much effort would be necessary, or if that would carry over to the android version, but that would be so useful to me.
Thx @Jer4 and @tyslothrop1 . I would love to have he floating window split screen as well on iOS. Unfortunately that would require auv3 support, as far as I know. And I just can't do that with Flutter
It would also be my favourite addition though. Maybe one day if google adds it to the flutter framework.
The upside of Flutter is that it's multi-platform by default though. That's a big benefit too though 🤷
At this time I would have to port the whole thing to Swift. I just don't have the time.
Totally understandable! It would surprise me if it would require AUv3 support though, a lot of non-audio apps work as spit screen/slide over, they are definitely not AUv3
@tyslothrop1 @Jer4 Ahhh now I know what you mean. Yes actually split screen would work easily!!! I was thinking of that nice plugin floating window. I guess I could enable that.
I just wonder if it will mess up the layout haha. i'll try it out
That would be so cool! Fingers crossed!
Awesome, that would be so cool! If there's something to test, I'd gladly help, if I can
Thanks guys. I briefly tried it and so far it just crashes when resizing the split or window 😆. Can't tell how that will go yet
Too bad! Hopefully it’s something easy to fix, but also totally understand if you don’t want to spend time on ✌️
A pity, hope you figure it out. Otherwise still my favourite controller app:)
I can always use loopy in slide over mode on top of midi poly grid and it works, but a fixed layout, that doesn't need to be rearranged all the time and bigger controls on loopy would be so much cooler.
Come join the premiere in a few hours if you’re free! I spend quite a lot of time in this vid discussing the merits and demerits of different layouts etc, should be interesting to anyone experimenting with that kind of thing. I think there could be some interesting discussion during the premiere, and would love to hear about people’s favourite setups. See some of you there hopefully!
@Gavinski thx so much for testing the app at it's limits and all the helpful suggestions. Thanks as well for introducing others to Midi Poly Grid. You are a real champion and a legend!!
Ill be asleep when this video premiers but I'll definitely watch it tomorrow first thing!
My pleasure Andreas, and thanks for being such a responsive dev and seemingly very lovely person!
That's great, thank you!!
How do I advertise Midi Poly Grid as a Bluetooth device?
Sorry I couldn't find it yet.
U advertise the device you want to connect it to, and then you connect midi poly grid to that device, inside midi poly grid's settings