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
Since modular may well prove too complicated for me, does this come with a decent number and range of presets?
Yes. I pretty much learnt how stuff works by loading presets and fiddling about. It comes with around 15-20 i think. But they're vastly different. And can create a ton of new sounds without changing any connections just fiddling with knobs.
The number is fairly small but the range is pretty decent to get you going, IMHO. There’s clearly a learning curve but the app is already helping me go through that curve.
Maybe forum members with modular experience will start sharing patches?
I intentionally kept the number low and the range broad. The presets are more for 'educational' purposes, since for most people the 'appeal of modular' in exploring what's possible and getting those 'geez, I didn't know this was possible moments'. So presets are a bit of a spoiler in that case ;-)
>
Ditto. I don't need another synth, don't make much in the way of electronic music, and would never buy something like Moog's Model 15. Too complex.
But I'm buying this. Nice one, Mr Brambos.
Thanks, I think I will have to pass for now then.
>
Or in my case, bust.
Just tried what you describe, and got hopelessly lost. Any chance of a video, or simpleton's explanation?
@brambos
I'm armed with iTunes card lol
But please tell me what the auv3 version doesn't have
The top-half of the screen is the AUv3, the bottom half is the standalone container. The AUv3 does have its own preset manager, so your patches (when you save them in the synth itself) carry over to every AU host you use.
When i save au preset, restart app and then load my preset - notes are displayed as initialy. But it does play notes correctly.
Is it ok?
Iphone7
What are you using to save? The AU plugin save/load (top of the the synth itself) or the pattern save/load from the standalone sequencer (bottom left)?
Open app
Randomize
Save au preset (upper right)
Close app
Open app
Load au preset (upper right)
Plays as it should but notes are reset
One can only have one master instance of the ripplemaker sequencer in AB3 right? As in the rest are copies? Just checking because I haven't used AB3 much.
This app and sequencer are magical. I can make everything with Brambos apps. Brambos is gonna be the next big genre.
Been able to mess with it as an AU within Garageband (on iPhone 6+, latest iOS) for about an hour this morning. Got a couple of wonderful press-a-key-and-let-em-go patches already. This is definitely bringing something I did not have in my arsenal at all.
When operating as an AU there's no sequencer aspect, right? I haven't played with it in standalone mode yet.
I did sort of lose one of my patches because I built it up in GB without having recorded anything yet. I think Ripplemaker was working according to its own 'clock' at that point. I had a kind of conga line drone going using the bandpass and with the slope modulating the LFO rate. But as soon as I pressed record in GB, the patch behaved completely differently (I assume because it then suddenly adopted the GB track's clock?) and even after stopping the transport in GB I was not able to get that patch back to where it was.
Also something interesting to report on the second patch I built. I recorded a three-bar loop with it in GB which I then filled a few dozen bars with. The three-bar loop involved a lot of note changes and short note values. Then I started wondering what a second instance of the same patch might do in another track with longer sustained notes that did not change in pitch much. So I saved my patch, called it up in a new track, and gave it a longer loop with very long sustained notes.
To my surprise, the first instance of this Ripplemaker patch changed its sound drastically, seeming to react to what the second instance of the patch was doing. It was interesting for sure, but I wanted the first instance to keep behaving as it had before, so I made some small knob turns in the second instance and saved that as another new User patch, in case that would 'divorce' the two instances from each other. But it didn't.
I ended up saving the version of the project with the double instances because it was so interestingly messed-up sounding, but I had to make a copy of the project and delete the second RM instance before I could get the original character of the first RM track to come back.
Are multiple instances supposed to talk to each other like this?
No, they certainly aren't supposed to talk to each other. And I can't imagine how they could because they're completely separate instances, but I'll try to reproduce it.
Edit: what could have happened is that a different tempo influenced the sound of the patch! The incoming clock signal determines the rate of the clocked random source, which could drastically alter the character of the sound... could that be it?
Saving notes in the synth (top right) saves the synth settings into the AU plugin, but without the sequencer data.
Saving from the sequencer saves everything (sequencer notes, synth data, mutation settings and tempo) but these patterns are only accessible from the standalone sequencer.
W/o seq data? How can it play what needed then?
Seen Doug's video, what's the other one?
Depends on how you intend to use Ripplemaker. If you mostly use it standalone with its own sequencer you only need to save the pattern (bottom left save/open feature). Then you'll always have the full package; sequence + synth patch + mutation settings + tempo etc.
If you want to take your own patches into other DAWs and AU hosts then you'll also want to save the synth patches into the plugin (because third party hosts don't have access to the standalone sequencer app, only to the plugin).
It's actually a brilliant save system to be honest. Any chance troublemaker could receive the same ? Would love to be able to use presets between multiple daws for the aux...
Just had my first real jam with it. Hit record in Auria and let myself go. This is very fun.
Always gonna have to have record on. So tough to recreate something exactly...which i love.
Thanks!
Heh, should have known it was Synth Anatomy
Huh, apparently the forum doesn't inline the m.youtube version of links, pasting the www one for the lazy
I really agree with this sentiment. I've had presets practically ruin synths for me because I felt everything had been covered.
Great app. I'm a little overwhelmed by the unfamiliar terminology, but still have managed to come up with some cool sounding patches in the first hour of learning it.
One thing I've noted from the videos for Ripplemaker is that the sequencer isn't exactly the same as the Troublemaker sequencer in that it doesn't seem to have the option for ties between notes?
As spoilers go, this is a pretty good one, in terms of the learning experience (and my background is as a technopedagogue).
Maybe not the thing for @BiancaNeve just yet, but maybe once we start sharing presets (which might become easier in iOS11?).
So, buying this app and trying it convinced me to also buy Troublemaker. You may found it strange but, until now, wasn’t that taken by examples of Troublemaker. Got the nostalgia thing but these sounds weren’t really for me and the pattern sequencers, while neat, wasn’t necessarily required for my stuff.
Having tried the pattern sequencer in Ripplemaker and played a bit more with the patches, it became pretty obvious that Troublemaker was also a good investment. To be honest, was kind of waiting for a sale. Did notice the previous sale, couple of months back, but wasn’t yet convinced. Now, Ripple sufficed to convince me about Trouble.
Funny how these things go. You might say that the prices are so low that it shouldn’t matter. You may also say that we should support our beloved indie devs as they do great work and are incredibly responsive. You could even yell at me for not getting how awesome those TB sounds were in the first place. Heck, even the Oscar Peterson picture should have made react more positively, as a Montrealer.
The fact of the matter is, though, that it took me until today to really understand the @brambos lineup. Had bought Phasemaker but haven’t used it much, in part because it requires MIDI CC to be rerouted and the initial sounds didn’t fit my needs so well. Getting into Ripplemaker, though, it all started to make sense.
What remains an issue for me is the fact that MIDIflow classic is a requirement to use those *maker apps with my wind controller. May sound like a small requirement, but it’s still an extra thing to prepare before getting things set up the right way. Since it’s not AB3 compatible, it also means that MIDIflow Adapter needs to be on and that MIDIflow classic’s state isn’t saved. You may say it’s a minor quibble and one which will be solved by future apps @JohannesD is likely to release. But it does make a difference in terms of overall experience (especially since MIDIflow classic was set for another app, so it wasn’t even sending CC messages to the right place, at first).
To fully understand the joys of AU, opened several instances of Ripplemaker in AB3 on my iPhone 6s Plus, and loaded a generative patch in each of them. The ensuing cacophony still sounded like something which would only need a bit of tweaking to come close to the stuff people are playing at SOSfest (Switched On Synths Festival). Not only is Ripplemaker like a semimodular synth but AU support means that you get multiple synths for the price of one. Very neat!
Same thing happens with Korg Gadgets and even with @AmpifyxNovation Groovebox. We may all take this for granted but there’s something really powerful about having multiple instances of the same synth.
You know what’s silly about this, though? Monophony was almost a dealbreaker. Even for me playing a monophonic instrument for the past 30 years, noticing “monophonic” in a description gets me to rethink my purchasing decisions. But, of course, the point is almost moot when you can have multiple instance. Now, sure, it’d be fairly cumbersome to set things up so you could simply play chords by sending each voice to its own monophonic synth. But you can still play chords by either generating them through an app or by using some MIDI FX to turn monophonic input into polyphony.
All this to say, the Bram Bos Approach is a very sound one.
Now, as for the patches embedded in Ripple... They really do serve well as training wheels and they’re diverse enough to cover several needs. The point of (semi)modular synthesis isn’t to play with presets, anyway. But the synth will still accrue a lot of value once people start sharing patches. (Not entirely clear how we can load them but even if that can’t be done directly, copying a patch by the visuals of the patching can work well. Some people have done it for the Korg MS20.)
With these releases along with some completely unrelated but potentially very good news for my professional life, today has been a good day.
TGIF!
I'd like to know this as well. Also, in looking at videos for Troublemaker and Ripplemaker, I can't seem to see any visual indication of which step is playing in the sequencer. Is there an option to enable this?
I'm about to snag Ripplemaker as my first Bram Bos app, and I'm guessing it'll be the gateway drug to the rest of them.
Yes that's something I hope may be added too eventually, I get lost as to when the sequence starts and ends as currently there's no indication.