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
That’s something that has surprised me too.
Agreed, although it would also be nice to capture and loop generative phrases when you stumble upon something particularly good. Sort of like Turing Machine or Marbles.
My only gripe with EG Nodes is that I keep forgetting to toggle on the nodes, and then I think it's not working. That's definitely a me problem though, nothing to do with this brilliant app!
I believe there's something planned for that somewhere down the road based on a discussion earlier on Discord.
I do that too.
Getting used to it though. 😂
I have the same problem, and I think others do, too. I wonder if it isn't largely caused by a too subtle difference in color between 'off' and 'on'. Would be easy to fix. Seems a shame to have an aesthetic decision like this cause aggravation in actual use.
Thanks! I don't use Discord anymore, so appreciate you sharing that it's on the roadmap.
Hmm, maybe it's not so much a me problem then? There must be a way to make it more obvious, without ruining the overall aesthetic (which is great, imo). I'm all for non-distracting interfaces that look nice, but only if they're still easy to use and readily display key information.
That said, I'm also very good at tuning out all the garish flashing lights on my Eurorack, so a great big red 'off' button wouldn't be an issue for me.
I don’t think it’s a UI issue really. There are other indicators than color, such as the play button, the flashing node countdown, and the rotating animation on the playing scene.
I think it’s simply that nodes default to off. That’s the only time I get caught off guard. No big deal to me. I just chuckle at myself over it.
To me it sounds too random, but I might be spoilt by Scaler2
Cooking.
Wow. Huge update! Thanks.
In case you missed it, @ElliottGarage :
'The Rhythm node doesn't seem to have a mapping for SEGments (which is weird, as it's another EG joint!). When loading the node it defaults to 'ElliottGarage', but none of the lanes will play any notes. I had to change the mapping to 'Splat-to-...' for it to work. None of the other mappings in the list would work.
There is also a slight UI issue on iPhone, as some of the text in drop-downs within nodes is too long to be shown in full. One example of how this can be a pain is that longer scale names like Harmonic Major and Harmonic Minor can't be read. In most cases this is OK because you can still figure out what it is as long as you have encountered the name before, but not in this case unless you know the order of the scales list! (I ended up going to the main project scale list in order to work out which Harmonic scale name came first...)'
Have you tried changing the root note in Segments’ midi settings. I had to move it down to C2 I think
It’s also still missing mappings for Koala, Borsta, Fractal Bits and SDS-x
@Michael_R_Grant I didn't map sEGments because you can have different option for it in the app as @FordTimeLord. So you can simply use the 'From 36' rhythm map in EG Nodes and map it in sEGments.
@01XMO Koala is already there. If you send me the other MIDI maps at [email protected] I'll be happy to insert them
Thanks for the offer but that’s not the Customer/Seller relationship I subscribe to 😊
The 16 Pads in Koala do not correlate in any logical way to the 16 lanes in the Rhythm Node. No more than 4 trigger 🤷♂️
@ElliottGarage Thank you.
Out of the box, taking the top row of Pads in Koala as 1-8 and the bottoms row of Pads in Koala as 9-16. Then a diagonal row of steps in the Rhythm Node starting top left, Step 1, Row 1 and finishing Step 16, Row 16, bottom right. Rhythm triggers 3, 10, 2, 9 and 1 only. Hope that helps, perhaps others can verify.
@01XMO as you can imagine I cannot buy all the app in the App Store to add support to them...and some dev don't answer when you ask for a promo code. If you know the midi map is very fast to send me and add them to the app...otherwise it requires more time, just that. About Koala I inserted the standard MIDI map, but I know that it's configurable, so maybe you changed it?
@JohnnyGoodyear @purpan2 @CapnWillie thanks!
Koala mapping works great for me in portrait then stops working in landscape sometimes (iPhone) but this is a koala issue, not a nodes issue. It seems to have something to do with whether you start in landscape/portrait mode but I’ve never been able to work it out.
Are you using Koala in landscape mode? Koala’s default midi mapping is for the portrait layout of the pads where everything is stacked in a 4x4 grid. In landscape the mapping doesn’t go left to right in two rows. It splits them into 2x4 blocks. That could be why pads aren’t firing as you’d expect.
Yes landscape on iPad. Regardless, I’d still expect all 16 Pads to be mapped/triggered, regardless of which Dev/App is at fault. Got to wonder who’s testing and communicating this stuff 🤷♂️
They are all mapped and triggered though, just now how you expect 🤷♂️
It's a long-standing Koala issue. There's nothing that Nodes can do about it.
As I have said, they are not all mapped and triggering, just the ones I mentioned.
Only other thing, In Koala Settings>MIDI I do have ‘Use MIDI mapping’ turned on but no custom mapping, it’s default, out of the box 🤷♂️
Strange. Do you definitely have a sample on every pad? Could it be triggering an empty pad? I’ve just tested in Nodes and all the pads trigger (edit: pads 1-16 that is)
Yep, simple test was to record saying each number 1 through 16.
The only thing that changes in portrait mode in Koala is the Pads are:
Row 1 = 1-4
Row 2 = 5-8
Row 3 = 9-12
Row 4 = 13-16
The pads are the same and should trigger regardless of orientation. They don’t. Perhaps more testing can be carried out. I don’t see this being unique to me.
Ah ok, could be a bug then I guess. Works fine for me doing the same test
Ah, just noticed this. Have you tried turning use midi mapping off?
Try these settings:
Right, with ‘Use MIDI mapping’ switched off in Koala Settings>MIDI all pads trigger but in the order below:
8,7,6,5,4,3,2,1,16,15,14,13,12,11,10,9
(When using a diagonal row of steps in the Rhythm Node starting top left, Step 1, Row 1 and finishing Step 16, Row 16, bottom right).
At least all pads are triggering and there is some sort of order (backwards), just not one that makes sense or is particularly useful - yet no one else questioned it? Perhaps users aren’t triggering existing Koala kits or are just happy and relieved when they find a sample on a lane and just go with it 😂
I think more testing and feedback by others is needed.
Same result with those settings (everything turned off) Greg - this sort of thing definitely kills workflow
The issue is with Koala not Nodes. It’s just the default mapping in Koala. What you are calling pad 8, koala views as pad 1.