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 use koala in portrait on my phone a lot of the time which works fine. If I do start in landscape it sometimes plays the wrong pads, but I just turn to portrait and I’m good, even if it goes landscape again. More a minor annoyance than a workflow killer - so minor that I haven’t bothered reporting it to the koala dev.
Edit: forgot to mention, I’m hosting nodes and koala as auv3 in loopy pro, so ymmv.
Minor annoyance to you Greg, workflow killer to me.
Helpful to report all these things, no matter how minor, else nothing gets done.
Wouldn’t touch LP.
On what planet is Pad 8, end of Row 2 in Portrait or end of Row 1 in Landscape, ever seen as Pad 1?! 😂🤣
Perhaps Marek is from a place that reads right to left? 🤔
@elf_audio
Got to park this here, wasted enough time on it. It’s simple and just needs to be fixed.
My bad, I was thinking of pad 9 😂. Sorry to muddy the waters
No worries. Points still stand, on what Planet is Pad 9 seen as Pad 1?! 🤷♂️🤣
To conclude, to get Koala Pads to trigger 1 - 16 in the Rhythm Node you need to use this mapping and have every setting turned off in Koala > MIDI.
I think it’s just a relic from when Koala was a portrait only app. Pad 1 is bottom left, pad 16 is top right of a 4x4 grid. In landscape mode the top 2 rows of that grid move to the right. It’s an MPC style pad layout shoehorned into a landscape orientation.
The thread above was based on the premise that the Pad order in Koala was (logical to a non MPC user):
If it’s based on the MPC order you suggest, it’s an illogical mess in the landscape orientation (see pad numbering).
And you need to use the grid below in the Rhythm Node just to play Pads 1-16 in order
One would imagine correcting this mess might create some pushback from the Koala Community for their historical projects? Perhaps that’s why it’s never been properly addressed and fixed?! @elf_audio 🤷♂️
It is what it is. Koala has been like this forever. You can remap the pads in Koala’s settings. It doesn’t take long and then you’re all set
Can some others please sort Borsta, Fractal and SDS-x?
You can, but not if you want to trigger them in Nodes because you’d have to turn ‘Use MIDI mapping’ back on 🙄
Ah yeah, forgot about that. We’ve come full circle 😂
OK I’m out. I’ve said and done enough. It’s over to the Devs to do their job now. Hopefully to create a better user experience, one way or another.
Except that it's unlikely the Koala developer will see this discussion and it's impossible for EG Nodes to address. If you really want to add your voice to those asking for it to change then you'll need to contact the Koala developer. The two main communication channels I know of are:
https://www.elf-audio.com/contact.php
https://discord.gg/VCBUBNSXq9
Tagging @elf_audio - but I have no idea if or how often he checks in here.
Of course, if it's not worth your effort, you can just wait for it to be changed. But don't hold your breath.
This:
Does this for me:
If I then turn to landscape, I don’t get the same as your diagram @01XMO . It plays the bottom row left to right, then the top row left to right.
The only anomaly is when the weird landscape thing happens from time to time at the beginning of a session. Once I’ve sorted that by going to portrait then back to landscape, it does the above for the rest of the session.
Anyway in the time it took to make those numbered graphics, any of us could have emailed Marek. I’ll email him now and point him at this thread.
Koala is a mess. If you use MIDI mapping and midi learn all the pads, the same MIDI notes will trigger the same pads regardless of landscape/portrait orientation. If you don't map the MIDI then the note to pad mapping is different.
The behavior is different depending on whether MIDI Mapping is on or not.
When MIDI Mapping is off, the orientation matters. The note played by MIDI Note Offset is the lower left pad and each half step up moves one pad to the right until the row end is reached and then continues with the left hand pad. When you rotate the ipad from portrait to landscape, what was the lower left pad is now the fifth pad on the lower row -- so, played by a different MIDI note.
When midi mapping is on (and all pads mapped), the same note triggers the same sample regardless of orientation.
When MIDI mapping is on, portrait mode number from from top row to bottow row is:
13 14 15 16
9 10 11 12
5 6 7 8
1 2 3 4
Landscape is:
13 14 15 16 9 10 11 12
5 6 7 8 1 2 3 4
These might not seem logical but they are what they are. And it is a Koala issue not a nodes issue -- but Nodes could have two Koala maps i, one for portrait and one for landscape and applies only to Use MIDI Mapping off.
Octachron has two mappings for Koala a 2x8 (landscape) and 4x4 (portrait) so not impossible at all.
The 2x8 (landscape) offers logical and elegant diagonal steps pad 1 = top row to pad 16 = bottom row. If pad 1 had been the bottom row and pad 16 the top row it would have been equally logical and elegant, in a single upward diagonal, to play pads 1 - 16 in order.
The 4x4 (portrait) is less logical and elegant imho and should have been implemented following the same top left to bottom right single diagonal logic.
That said, it would of course be helpful for @elf_audio to acknowledge the issue and fix the problem before @ElliottGarage, @TasTax, or anyone else implements any improvements to Koala mappings.
New Interoperability/Connectivity Standard
This interoperability/connectivity problem (Nodes/Koala and almost all other Devs) really highlights what an amazing job Dave Smith et al did collaborating on the MIDI Standard. It’s illustrative of how much we need a new leader and group of Devs who can collaborate to establish new standards in the multi app, modular iOS world of creating and recording we are now in. Rather than Devs just doing their own thing so we end up with statements like, it is what it is and, it’s impossible to fix. No. It. Isn’t.
Having two maps is a good workaround. Maybe @ElliottGarage will consider it.
Tell me, is it possible to launch clips in EN from the controller (Launchpad)? I haven't bought this app yet, but thoughts are already emerging.
I'll tell you with a page from the manual ( at https://www.elliottgarage.com/user-manuals )
Thanks I've already bought it and almost figured it out. Everything is set up manually. I just had problems with Solo and Mute. They don't work with launchpad (I tried momentary, toggle, trigger). They are pressed, but the channel continues to sound or does not go solo. Maybe I'm missing something.
Easiest thing in the world is to be cynical and just give up 😉 Interoperability on iOS is a constant problem that needs to be better addressed
Suddenly not impossible? Don’t you love it in life when a person who consistently behaves as if they know everything, is wrong, but acknowledges it and apologises 🤔🤣
Should be easy enough for @elf_audio to acknowledge the issue and confirm if they will or won’t address it in Koala, before anyone else attempts to improve their midi maps to Koala specifically
In general, I figured it out) It turns out that Egnodes solo and mute CC do not accept ordinary ones (more precisely, they accept but do not activate mute and solo), Midinote is needed. I'm not that good at midi, but why doesn't it work?) But I would like to hear the opinion of @ElliottGarage. Maybe I didn't finish something.
And one more question. In Rhythm Node, you can raise the Contr note above D#3-63. It's just that Playbeat has 3 fixed notes starting from C3 and ending with G3. Again, maybe I didn't see something. It would be great if it were possible to create your own templates in Rhythm Node (as they are currently pre-installed). And there is not enough looping in SongMode.
@ElliottGarage
Feature request: 2-3 letter naming column in the rhythm node so we can give the rows a name would be cool, i.e. BD, SN, BD1, SNR….
I’m really liking Nodes so far, has inspired me to finish whole tracks more than any other iOS app to date, so thank you!
This behavior is known to the dev...if you want it to change, you should be in touch with him directly. While there are exceptions, it is often more effective to contact a developer directly about an issue than to @ them on a forum.
Already done
Can I just take a step back and say there have been 14 updates since its launch in January. Shout out to @ElliottGarage for the hard work so far.
+100
Upvote here: https://eg-nodes.canny.io/feature-requests/p/custom-mapping-in-rhythm-node