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
I think it'd be more interesting to keep the volume/filter slider doing what it does now, to alter the LFO shape and output level. In that case it might make more sense to have separate filter and volume.
Such a simple but expressive interface. I like the fine grain control of pitch. Being able to tune pitches and save them for later use will be appreciated. Are there any preset features to save current settings?
I put it into a little cluster of may favorite reverbs:
FAC Alteza
Cascade
EOS 2
Then I decided i wanted some location morphing and added Binaural Locator and looked where it might add vale to the resulting drones.
Then I realized zeroing out all oscillators took 20 seconds to settle out.
And then I added one and waited 10 seconds… then another.
I’m now a certified ambient genius. Go figure. Worth the $5. Thanks.
Oh actually yeh that makes a lot more sense, I forgot about amplitude for a minute there
I don't think it could have a filter as it'd be a midi output effect (though the idea of a filter for LFO's does sound interesting)
Glad you're enjoying it. Oddly I've never thought to put something through multiple reverbs at once, gonna try that now lol
Presets are a bit of a dilemma for me. On one hand, I've often felt annoyed myself when I open the app in standalone mode just to make sure a feature is working, hit across a nice patch, and then know if I want to record that I'll need to try to remake it.
On the other hand though, it kind of forces you out of your shell a bit if you know what I mean, it stops you relying on the same old tricks you know work and makes you reinvent the patch each time. I know in a few apps I've barely ventured beyond the presets, and even though I know I should, the quick and easy option often wins out.
It's something I'm certainly gonna look into though, no harm in trying it out at least
EDIT: Ooooh, at low cutoff frequency, 3 saw-waves together produces an almost choral sound with this setup (all using the init patches): Shimmerverb -> Stratosphere Cloud -> Velvet machine
Hey, apologies for the delay, video uploaded!
Filters can make sense for shaping LFO's too. For instance, you can round off a saw wave to varying degrees, making something between a sine and a saw shape.
Never heard of that being done before, very interesting
Oh, just a quick question, does anyone have any recommendations for simple sources of audio unit midi cc modulation? I must admit I haven't done much with AU parameters before so it'd be good to have something I can use in my testing
Indeed, though word of caution: LFO filtering can involve steep slopes and crazy low normalized cutoff frequencies (especially in the above example of turning a saw into a sine). Filter architectures that perform very reliably at normal audio rates may struggle with preserving super slowly changing waveforms when configured at these "LFO-oriented" settings, and can introduce artifacts like big steps / stalls and minor jittering to parts of the signal that are clearly below the cutoff frequency and should be unaffected in an LPF setting.
So the important thing is to be aware of this when testing, and if there is a problem at all, you can choose from a number of possible solutions or could even steer the app's design in special cases.
Personally, I would also separate the two realtime LFO filtering cases: filtering an LFO in general and using a filter to control the shape of the LFO waveform where I expect that waveform to be constant regardless of LFO frequency (bandlimiting effects aside).
The latter puts much stricter requirements on the filters used (should perfectly shift its frequency response without any other changes following the LFO rate), and may be impractical in some cases or depending on your requirements.
Though that's not to say one cannot relax their requirements and create something more experimental.
https://apps.apple.com/us/app/gsdsp-mmm/id6443846329
https://apps.apple.com/us/app/gsdsp-mmmm/id6450306205
https://apps.apple.com/gb/app/mlfo/id1602306976
https://apps.apple.com/gb/app/midilfos-midi-modulator/id998273841
Normally AUv3 apps should save state, but this doesn’t. Most people using this as an AUv3s would expect that when they open a saved session (in AUM) for example, where they had a few of these set up and playing, when they open the session again, they will still be playing, exactly as they were left. But these open blank, and presets also can’t be saved inside the internal preset menu of host apps. Could that be changed please? 🙏 @tspring
I’ve always liked the way apeSoft apps like apeMatrix handle midi cc and LFO modulation
Yes
Perfect, will take a look at these, cheers!
I believe save state has something to do with AU parameters, so it'd make sense that they're not saving right now but yeh adding those in is top priority for the next update.
Presets I explained in an earlier comment, currently not sure about them for what the app is designed to be, though luckily I don't think they're needed to have functioning saving. But yeh, thinking about that.
Though I suppose the internal preset menu of host apps would also likely work off AU parameters as well, so could just be a consequence of adding them
Yep, that's right
Thnx for the reply. I don't think parameters need to be enabled to save state, because I'm sure I remember that there have been apps that either didn't have any parameters exposed, or didn't have all exposed, but saved state no problem. Maybe someone like @wim or @uncledave would be able to say what needs to be done to enable state saving.
Since you asked... It looks like you can implement state saving without exposing parameters by overriding the fullStateForDocument property, as described here and here. Basically, you put your data into a dictionary and hand that over to the host. The host will hand it back to you on reload.
Oh nice one, that should be relatively simple to implement then, though it appears that it might be possible that state saving happens "automatically" if I were to expose the AU parameters, but good to have a backup in case it does, cheers!
Is it standalone as well?
Yes
Yep, includes a standalone app too
Would be interested to know if people find that useful and why, to me right now it's there just because there's no reason to get rid of it, though now I'm trying to add AU parameters it's getting harder to justify keeping, so if anyone finds it useful it'd be great to know before it (potentially) ends up on the chopping block
Cool little droner looking forward to see how the app fully develops but like the simplicity. Automation of frequencies sliders via lfos with parameters exposed would be great. For the price of a coffee worth a go with this one.
@tspring Currently just tested on iPhone I’m not seeing the AU listed in Cubasis 3 or Audio Evolution DAWs or EG Nodes. It’s showing in Audiobus 3 and AUM. Latest iOS. Maybe because it’s a generator AU only. And doesn’t accept midi what iOS DAWs is it compatible with to make noise and do you have to route its audio out to an audio track ?
Shows up in ApeMatrix as Gen only.
Yeh it's because it's a generator, it doesn't take midi inputs so with apps that record midi, there's no way for them to interact with the app. I'm not certain if this could change with the introduction of AU parameters as they are technically midi, will need to test that further, but for now, yeh it's just a generator.
Any DAW which can regard audio rather than midi should work. Have got it working with AUM of course, Loopy Pro and Reaper on the Mac version.
So yeh basically any DAW that can record audio directly (and supports generators, of course)
@tspring Thanks for the reply I’m surprised it doesn’t show in Cubasis 3. It works well in Logic Pro though. Having an issue with multi use I sent you a PM on here.
2 reasons. I love sound, and I like just opening an app and losing myself for however long in just listening and manipulating. I also like any app that produces something I can jam or practice guitar to. I have a tendency to just noodle away, change the key and round and round it goes. Bought.
Fine tune mode for fat fingers?
Keep screen on?
In some ways this one reminds me of a long-lost fav app, Dr-OM . I miss that one. It's still available, but last time I checked no longer working.
+1 for keeping the standalone. I tend to easily loose focus in AUM due to all the posibilities, so love focusing on an app in standalone mode too.
Thumbs up for thinking way outside the box on this one. I like where you might go with this and other complex (under the hood) sound-generating apps.
It works for me on 17.5.1 (M2 Pro 11”). For the last few iOS versions you need to start it with the iPad in portrait and then rotate it, or the screen is messed up. Same applies to Noisemusick (same dev).
Thanks. Maybe I'll try again some time.