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
Wait what! Is these the guys who made the hammerhead drum machine? I used to use that in highschool
that is awesome if your the same guys
Yes, that would be me. So this is not my first drum machine ;-)
so which date should we mark in our calendars?
Yeah I remember Hammerhead too back in 1997.
I'm still shooting for second half of June. Just finished the advanced user guide (overview of all parameters and instruments) for the site... So it's slowly nearing completion.
Take times, we going to love it when launching the IPO. Skyrocket shooting high...
Have a stock code name for quote? How about 'RUIS'!!!
Do we get a 'sneak peek' at the Ruismaker user guide before release?
(This is what I usually do with all hardware I buy, especially Cameras).
As for Ruis we'll see what kind of 'porridge' we can cook with it
Translation of the Finnish word Ruis when translated to English is Rye and to Swedish it's Råg...
But in the case of this apps origin it's apparently 'Noise'...
Do we need a Patterning Pan with rye cookery recipe ?
Hosting both in AUM should do the trick
The parameter and instrument list is on Ruismaker.com (check the bottom of the page). It's not a full-blown manual, but more like a MIDI cheat sheet and a description of the currently available list of sound models.
Let me know if it would make sense to elaborate on certain aspects.
Had a quick peak a the manual and I do wonder what lead you to choose the note-assignments for the sounds?
This will be a major pain as controllers need to be re-programmed to have a preset matching Ruismaker and also it will make it pretty daunting task to use midi drum-loops that use a somewhat default note-assignment for drum sounds. Please do re-consider this and use a chromatic scale for the notes starting with note #36 for kick-drum.
As I've understood each pad has a 'drum-type' that has a set number of adjustable parameters.
That's nice, but is there a way to save 'kits' or 'sounds' that can be easily recalled at later point?
(I mean other ways than to save all the edits as midi CC in a sequencer?).
How is the sound selection made? Select a pad and 'swipe' the number display?
Also I could not see any way to 'bypass' the reverb per pad, seems like all sounds are fed thru the reverb?
Other than that it looks pretty clear to me.
Hmm... I'm puzzled... The Middle 'number' is the 'kit' and sound-type is selected by 'personality?'
So if say all 8 channels have 'personality' set to 11 all pad will play a kick-drum?
And in order to see the value of a parameter it needs to be changed? (or is the middle display updated with the parameter value when touched?). Or is there a way to toggle value display on/off (like tapping on the logo?).
And also I was quite amused that the instrument names were not in numerical order in the tables
I'm aware this is unconventional. However, it was a very conscious decision: it will make our lives much easier when programming notes in piano-roll environments as the correct keys for triggering the drums instantly stand out visually in the piano roll.
What I can do is make a switch in Ruismakers iOS preferences pane to override the black-key assignment with classic MIDI key-assignment.
This is what AU hosts are supposed to do support according to Apple's AU documentation (confirmed in a discussion with Apple's Core Audio team). AUM already does this beautifully. They basically take a snapshot of all AU Parameter values and save it as a User Preset. So I fully expect the other hosts out there to do this in the near future.
No, you get a little pop-up widget that lets you choose from a list. I figured the number display would be a bit too hardcore ;-)
Indeed. The plate reverb is there to add a bit of a natural presence to the overall output signal, to give Ruismaker a character of its own rather than a completely flat 'unnaturally' sterile sound. Most hosts have full blown built-in reverb/echo effects that offer lots of control, so this is not trying to duplicate that sort of effect functionality. All the sounds in the demo track I posted earlier have this minimal effect applied, in case you're wondering about the impact on the sound. It's subtle enough to not be noticeable, but adds just a little bit of character to the sound.
No the LCD display just shows the value of the last parameter that was changed (or the channel that was selected, etc.). It's just a little visual help while tweaking parameters. But real musicians do everything by ear, right? :-D
If you tap a channel button you get a little widget that shows (and triggers) the currently selected instrument (and if you tap that, you can change the instrument).
Hahaha.. they weren't all created in a logical order, but rather in a "hey, right now I really feel like adding another snaredrum/kickdrum/cowbell"-order.
This is interesting, does this mean that presets are not shareable between hosts? Or are the user presets somehow persisted within the AUX?
Right now they aren't but as AU developers this is a strong wish we have requested from Apple and they have hinted they're internally considering it.
Okay glad to see there is engagement and dialogue with Apple on AU. Looks like it's something that will evolve nicely.
@brambos Thanks for the clarifications, guess I got a bit exited and forgot to 'think' haha
I'll be looking forward to spending a latte or two on Ruismaker when it hits the AppStore....
@brambos, very interesting approach to the midi mapping...
Is everything on midi ch. 10?
Do I understand correctly to think that CC#22 with values between 10 -17 will switch between kicks,lows?
Does it mean that CCs 22 to 29 can dial any sound on their respective channel? Like if I use cc29 (open hat) and dial value 33 I get fm snare? Or are the 8 channels blocked to their ranges? Like kick =10-17 cc#22 only?
Obviously CCs 30-94 have values 0-127 pan volume etc...
Which would mean I could draw pitch with CC30 for kick? In ModStep for example?
Spot on! And instruments are not locked to ranges. If you want to put a cowbell on channel 1: more power to you ;-)
Ruismaker listens to all midi channels (not just channel 10). It's the responsibility of the host to send the right midi commands to the right plugin/instrument. But this is never an issue in real world situations, because for now Audio Units can't do MIDI THRU. If it ever becomes an issue then implementing a channel filter is fairly trivial.
^^^^^That is interesting......since they are AUs and you can run several of them, does it mean if I make 3 tracks and assign MIDI channel to each like 10,11,12 each Ruis will listen to its channel and not mix everything, playing its own sounds...They are not "MIDI promiscuous" are they?
THANKS for previous reply.
And the other examples or questions were theoretical, just to know and be sure, what is possible...
I don't need to change BD for HH unless I make a percussion kit?.... However doesn't this limit you to only 128 sounds for the whole drum machine if you used all values 0-127?
Which is enough if they can be tweaked...
Looks like an interesting drum machine, just after I swore no more of those
If your device is powerful enough you can have as many Ruismakers running simultaneously as you like. Each listens to its own host channel (which is not necessarily linked to any midi channel) and has its own engine, completely separate from all the other instances of the plugin. That's the beauty of the Audio Unit concept.
For now this limits me to 128 instruments, but the MIDI protocol has a workaround (called "bank select") raising the limit to ~2 million instruments, should I ever run into this limitation.
Wow.
This is what I needed actually.
Many reasons why.
I would love to see Zmors mod as AU also...........
Looking forward to this one. Despite having many good drum apps very few I have can be automated remotely via CC on release (even though they are planned). Plus being AUv3 this ticks many boxes so far
I really wish more developers of drum apps would put CC control priority over song modes, which I use in drum apps rarely now (although I'm sure other people use them more). full midi control makes it so much more useful on iOS and also desktop to iOS use as drum module. It seems to be the last thing on the list for most, although I can see why: it makes the app more sellable in the short term since you don't need another app to use it.
This might be a silly question but is the automation of parameters continuous?
I'm thinking about pitch-bending toms and other sounds with longer decay.
But anyways, it will be a nice companion to other apps and it might even end being used in favour to the others thanks to the automation posibilities
Who will be the first one to make a 'ModStep' controller-template for Ruismaker?? (I don't own ModStep yet).
The CC guru, @gonekrazy3000 .
If I'm limited to 2M instances, I'm out!
>
Good to know
Regarding ModStep, Is there currently a way to substitute a value with text?
(This would come in handy since in Ruismaker CC values can be used to select instruments, so selecting instrument by name instead of referring to a list of numbers would be really nice).
The 'number' to 'text' feature would be handy for off/on switches, so instead of 0 or 127 it would read off or on.
This would also make it easier to create 'patch-lists' for program change commands allowing easier bank/patch-selection.
Back to Ruismaker
Well, you can always do it in Ruismaker's own UI, which gives you a normal human-readable list of instrument names. You only have to deal with the numbers if you insist on doing it via midi commands :-D