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.
Modstep template tutorials?
Downloaded it and so far it's exactly what i needed. Only area that still has me scratching my head is taking advantage of the templates and assigning stuff to knobs etc. At the moment i am just able to use the xy pads. Any tutorials or better explanation on this?
Comments
+1
Downloaded it from where???
Haha. As in bought it
haha.
I assumed it was a continuation of your thread title. The Template is the last of the uncharted waters of my Modstep journey. Beware: There be monsters.
It's been a while since I want to talk about Modstep templates, the ones already in the library. A LOT of them just don't work, or partially work. I just don't understand ; I hesitated to talk about it so far because I thought it had to me who screwed up things but I have no problems at all building my own, and they work just fine. I totally understand the difference between midi CC and AU midi commands but well... Modstep is an awesome app so I don't want to sound like I'm bitching about it, this would be an awful misunderstanding. It's more a disappointment, you see these maps for apps you've got and boom, nothing... and building a map from scratch is not difficult but it takes so much time. Anyway, I'm just gonna take the case of Ruismaker (both) maps, because that's the kind of app which really deserves a midi map, so much fun. I build my owns, but one thing drives me nuts : with the instruments commands, it's almost obligated to define a restricted range, not like it is on the library map. For example, let's say instrument 4 is your tom, you want your midi cc between 70 and 84, in order to stay among the tom's "family" when you play with the x/y pad, at least it makes sense to me. As for the snare, I set the midi cc range between 34 and 36. And that goes for a lot of other app fonctions, all the switches for example, where you have 2 or 3 position, like in iSEM. All Modstep build in map let theses parameters set with a maximum range, 0 to 127, which is absurd but not a big deal if you can correct it. But even when you set the correct range, the right incrementation, like " I want that the X axis (on the Modstep Cc control x/y pad) all amplitude only represents 2 values for a switch on iSEM", it never works. As a result, you barely touch the pad and your switch responds, rather than have half the x axis for your switch on, and the other half for your switch off.
So if anyone knows how to deal with this issue, it will be the beginning of all new relation with Modstep!
Yeah @cyril777 something is a little off. But it's a great app. I know there some power users so it's probably just coming to grips with quirks.
I guess the templates contain the right CC numbers and maybe correct labels for the respective device's parameters. But I've never used this feature myself yet.
Haven't messed with templates much yet, but the Ruismaker ones seem to work just fine.