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
Lol the things I write. When read back. It sounds stupid.
Anyway.
Wonder if Bram could re-make Ripplemaker and Mononoke. Another paid app. With a patch point in between.
So you got the same UI.
but maybe the pads can morph audio. Or add texture. Moduation and vice versa.
I guess a Hainbach project.
If theres to be more modulation of audio texture. Modulation effects etc.
Got this thing long ago, because well I get all of Bram’s apps on release, but then it got forgotten in the “cool things to try later” folder.
Recently I’ve been interested in “west coast” sounds I knew little about, and I’m loving it, and Ripplemaker is such a great playground.
I’m just wondering if you guys have any tips or cool tricks to share, I love the envelope stages triggers for “automatic madness”, but I’m sure I’m just scraping the surface.
Also are there any presets that went under my radar?
I’m really enjoying just messing around, though, I have little notion what I’m doing but it’s so fun anyways I forget tomorrow is a working day
I dream of a sort of extended version with another oscillator and some clock dividers and or just the whole thing doubled up so the synths can modulate each other... Otherwise it's still the GOAT
Only user made preset bank I know was one shared by Doug Woods in one of his videos, and I think another one from here.
I’m working on some myself , actually. I freaking love Ripplemaker
@Fear2Stop the one from here you’re referring might be these?
https://forum.audiob.us/discussion/28390/ripplemaker-ki-explorations-preset-bank-v1-free
Haven’t tried them yet but seems interesting, thanks for the heads up
there is also a Preset Bank v2 (ki Techniques)
https://forum.audiob.us/discussion/28261/ripplemaker-ki-techniques-preset-bank-v2-updated-free/p1
Actually, I had the one @ZankFrappa just posted , not this one! Just added it 🤩 Thank you!!!
Have fun with these presets and modify them to your liking
Please share if you come up with cool sounds or new tricks. I really enjoyed fiddling around with Ripplemaker and would be happy about new impulses.
Here’s a Krell like patch I’ve been messing around with. It pretty simple I guess…
This is definitely the most lucid thing I’ve read you that quote you’ve written, and it’s a bloody splendid idea, I’m not sure MC @brambos takes requests though…
Plus one of these options and next GOAT achieved:
FWIW, here are nearly 300 Ripplemaker patches that I've made over the years. File name says it all ...
Anybody ever try driving Ripplemaker with the exposed AU parameters?
I never even thought of it, just always messed with the internal patching.
Having just taken a peep, there is a lot of exposed parameters.
There have been a few complex midi modulation AUs released recently. Could be a great way to expand this synth on your own, in a unique way.
I have an extremely embarrassing question to ask…what exactly does “exposed AU parameters “ mean? Does that mean it can be used as an effect or something?
I’ve been to ask that for a long time lol
It means you can send an external LFO (such as BramBos's Rozeta LFO) into Ripplemaker to modulate the "exposed" parameters. One creative use for this is to use a single LFO to modulate multiple apps at once, thus tying them together into the same LFO "rhythm".
I’m actually even more confused 😂. I take it that’s something that can be done in AUM but not GarageBand lol
I find it humorous that all that goes over my head, but I have no issues actually doing stuff with Ripplemaker, when for many others it would be the other way around lol
It is much like Midi CC that has been around forever, but this is the AUv3/AU host method. Only the exposed-to-host parameters can be controlled, though.
You are a GarageBand user, so this is probably not available in that host. Most other hosts can work with exposed AU parameters in some way.
Sticking with AUM for simplicity:
(Sorry, I don't feel like pausing to provide screenshots. Hopefully the explanation will suffice.)
AUv3 plugins almost always expose their controls as "AUv3 Parameters". What this means is they make them available for a host such as AUM to manipulate. The host then makes it possible for users to connect a midi CC or other control to manipulate the control. The important thing to understand is this is different than sending a midi CC directly to the plugin. In this case you're sending a CC to the host's mechanism for connecting that to a control.
That's probably already pretty confusing. Let's say for a minute plugin doesn't provide a way of manipulating something like a filter cutoff frequency. Instead it exposes an AUv3 parameter for that to the host. To map a knob of a hardware controller to that filter cutoff in AUM you route that hardware controller to 'MIDI Control' in AUM, then look for the AUv3 parameter for the filter cutoff. The most direct way to find this is by tapping the icon that looks like four faders at the top of it's AUv3 window. In Ripplemaker this is called 'LPG Frequency'. If your routing is correct, then you can tap on this parameter, then tap "Learn", then turn the controller knob and the link will be made. Viola! You can now turn the LPG knob from your controller.
Midi is midi, so it doesn't matter if you're doing this from something like a hardware controller or an LFO plugin that can send midi. Just keep in mind that if you're using midi learn you only want to have a single CC coming at a time, or instead set the midi channel and CC manually instead of using midi learn.
So. How is this different from controlling a plugin by sending midi CC's directly to it? And why would you pick one method over the other? Not all apps allow CC's to manipulate their controls, so AUv3 parameters are the only way. They also provide for more centralized visibility of what is mapped where. They can also offer much more granular control than the 128 values available from a simple midi CC. That's a subject I won't go into here though. Finally, they're consistent. Once you learn how to map controls once, it's the same for every plugin so you don't have to figure out if and how each plugin's midi control mapping works.
The downside is those mappings are specific to that host session! If you make a new session or move to another host you may have to redo all those routings. There are ways to reduce that hassle in AUM, but this is already getting too long. The choice of which method to use depends on what works best for you.
Wow, it scares me how much the above sounds like a chatGPT answer. It's for real, I promise. At least as far as I'm trust that we're not all actually bots - something I'm starting to question more and more. But anyway, I hope it helps.
Gotcha….that definitely would explain why ! I’m one of those who learns from just playing around and fiddling with knobs (giggity) so if something’s not available I won’t even know it exists
I guess sevenape idea better. Just a bigger ripplemaker rather than a sort of strega ( never really bothered checking strega really )
Why not both? An option to buy additional instances or other bram bos synths as iap to add as modules in a sort of bram rack or “blue easel”.
@wim . Good answer. Just two words to add, The Matrix.