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
Wow.
Cant wait Jan.
Thanks.
I've released version V1.3 on the App Store today.
The following features have been added to this release:
(The manual has not yet been updated, but I'll spend some time this weekend to work on that)
Ooo that portrait mode rules! Nice work 🙌🙏
@janm31415 great updates, thanks for being so responsive.
I believe it was @Gavinski that suggested you made use of beta testers, and I agree. It would be very beneficial and make the updates more robust.
I’m a bit lost regarding midi automation, I believe it might be due to the latest update. I can’t seem to find the correct parameters to automate. In the screenshot I’m trying to automate the Hihat decay (open Hihat). I thought it’d be drum #9 cymbal decay, as it’s what the Hihat pad number seems to be… but it’s not. What’s the logic behind this?. How do I find the correct parameter?. Thanks!
@janm31415 What a treat this drum synth is, and paired with the sequencer... Chefs kiss 😘
My only wonderings are:
Thank you for the fantastic drums!
Really like the new random button in the sequencer.
Hi Tahiche,
Following your screenshot you should use drum #8 cymbal decay (the counting starts from #0), as the pad in the screenshot is pad #8.
Hello Tentype,
I'll add your suggestions to my list.
@janm31415 thanks for the update.
The midi learn is working quite well. Do you think it could be extended to the rotary controls?
I assume you mean the controls to modify the synthesizer sounds (like decay, low pass or high pass filter et cetera).
I was already thinking of adding MIDI for this, but in the following way:
You can assign MIDI CC for any of those knobs, but they will always control the "active synthesizer". So the MIDI CC assigned with "Decay" will control the decay of the Hihat provided that the hihat is the selected synthesizer. It will control the decay of the Ride if the ride is selected. So it will be different than assigning a MIDI CC knob to a parameter in AUM, as is shown in the screenshot by tahiche above. (there will not be 16 MIDI CC slots that you can assign to the 16 decay parameters, but just one CC to control the active one).
I'm also not clear yet whether I should combine MIDI assignments for the membrane and cymbal synth or not. For instance, both the membrane and cymbal synth have a filter knob (low pass for membrane, and high pass for cymbal). They could be controlled with the same MIDI CC knob (as the membrane and cymbal synth of the active synth can never be both active at the same time). So you'll need less MIDI knobs on your device, but it might get a bit confusing. The other option is to have a MIDI CC for the membrane low pass filter and another MIDI CC for the cymbal high pass filter. But I'm kind of leaning to the first option.
The issue with controls only working when selected is that if the app is being sequenced by another sequencer (in my case Drambo) I do not actively play or select individual sounds. In fact often Percussive would be in the background. @janm31415
Is there a technical reason for you wanting to go the ‘selected sound’ route?
No technical reason. I was a bit afraid of the abundance of controls that you would get
I agree with @supadom. I don’t see the point of midi automating an app that has to be “actively” in the foreground. If you’re automating from Drambo, a daw or any host, chances are that the host is what will be in the foreground (thus “selected” won’t make sense).
As for combining midi assignments, I would say yes, the list is way too long and cutting it by 50% would really help. In the case of the high/low pass filters for membrane/cymbal… Just call it “filter”?. And if there’s any other messages that change between engines just try to mention both like “Timber/Overtone gain”.
BTW: bravo 👏 on the noise envelope, it’s really opens up the sculpting options!.
Thanks @tahiche for chiming in.
@janm31415 I don’t think people will get overwhelmed. Just make sure that they’re clearly labelled.
I can’t wait to be able to assign decay or pitch bend to velocity or pitch to pressure on the boppad.
This is turning into a monster app!
Thanks @janm31415
@janm31415 Excellent update! Thank you for taking so many of my (and others of course) suggestions!
Here’s a few more “beta testing” thoughts.
I agree with your thought about the “active” synth having its own controls (like AUTO channel on hardware) but I also think you should make it possible to midi control params individually. To make things less unwieldy, from my POV, just naming the auv3 params as param1..paramN would be fine and have them index the knob position… like top left knob=0. Use them for both voice types, and just ignore params that don’t “match” Formexample. Cymbal has less knobs so param12 wouldn’t do anything for cymbal voices.
If you do the “active” voice only, then having a au param to select the voice would be important.
This would also make it somewhat “future proof” if you ever want to add new algorithms.
I wouldn’t get too hung up on it being “confusing” or whatever because anyone nuts enough to dive that deeply into mapping is used to that kind of “pain”.
One thing that now seems even more weird is the hard link for the voice names… Especially since it’s now possible to have a “snare” be a “cymbal” voice…
My suggestion would be to replace the hard coded names with just “Channel1, Channel2 … Channel8”
Change the mixer columns to just “channel1..n”
Maybe even have the option to give custom names to the channels? Longpress mixer columns to name them, those names show up in the voice drop down and the sequencer selection. Thoughts?
edit Actually, that may not make sense since I believe the voice names/types are tied to the mutate algo, right?
I agree with the above suggestion that for voices a randomize/mutate option would be cool. Something that allows full randomization down to small variations to current value.
On randomization… Having a toggle switch or something for the mutate section to apply to the active voice or all voice would be nice. Then I could have a cool groove with say and hat, but then just use mutate on the snare. Or maybe something like a lock icon on each voice to exclude it from the mutate? That may be more versatile, and there’s lots of ui space in the title area for each channel in the sequencer. Maybe a long press pop up to lock/unlock the voice?
I’d also still like to see a mod matrix some day, so I could morph multiple params with mod wheel, modulate multiple params with velocity, etc.
For the sequencer, being able to assign cc output values to the “lanes” would be useful for external devices.
As we can now have individual outputs, I’d like to see it possible to have the same voice “name” assigned to multiple pads. For example… having 3 pads as snares each going to its own output would allow for mixing or crossfading between sounds.
Finally, I’d love to see a voice preset system. The ability to create, save, and load just voice preset would be huge.
Soooo much progress on this thing in such a short time! You’re to be commended!
Have you mapped more than 127cc in Drambo, using an mfx ( which is needed for sequencing drums )
Seems with midi feedback.
You only get 1 midui channel worth of cc, when using cc generators to exposed parameters.
No one really replied to this.
+1 it would make sense to treat different settings for a kit piece like a preset. Just like you can preview and load different snare samples on a sampler drum machine, you’d preview and load your favorite saved settings of a snare as a preset.
I doubt there are more than a handful of people in the planet who have mapped even 127 midi CCs in Drambo. You are somewhat unique. In a good way. 😎
Thanks for the great update @janm31415
The noise envelope especially makes a huge difference!
What a great and much needed app.
Man, those fonts on the drum pads are tiny though. Even with the plugin maximized I can barely read them.
Knobs are better, but still small. I wonder if it would make more sense to move the knob labels to below the knobs. It seems like you have room in the UI, at least on the Synth page.
Thanks wim.
Will find out when I rebuild an mfx for percussive synth.
I think the mfx isnt like the main for midi routing at the mo.
This app is really starting to grow on me. It seems faster to me to tweak the sounds I need than to hunt through hundreds of samples. Add just a tiny bit of brain for some variation (I don't like a lot) and some pretty serviceable drum parts come together quickly.
Is it possible to turn off the sequencer when running as an AUv3?
What’s killer with midi out is to trigger another drum/sample app like sintala and layer em…
Like FDK but with two apps…
@janm31415 Does not seem to be saving state in AUM. I arrange the pads, save the AUM project, exit AUM, reload AUM… All pads, routing, sequencer, etc all come back as default…
Also, the midi pad assignments are not getting saved/recalled by presets.
Lol, time to start those betas for sure @janm31415!
Currently the "Settings" parameters (MIDI assignment + Bus settings) are a global setting, and are indeed not saved by presets. But this can be fixed in a next release.
About the other thing with saving to AUM. Here is a bit of a technical problem. To save the sequencer I have to expose the sequencer values as a parameter in my AUv3. In this way AUM and other DAWs can discover them. They can then map MIDI or save them or .... The issue now is actually a bug in Logic Pro for iPad, which will crash when you have more than 1000 parameters exposed. (1000 is my guess. In V1.0 I had over 2000 parameters exposed and that crashed Logic Pro. Removing the sequencer parameters reduced the number of parameters to below 1000 and fixed the crash). So to save the full state in AUM you have to expose the sequencer parameters, but then Logic Pro won't work anymore.
That doesn't sound right to me. You can save much more than just AUv3 parameters in the state. Samples, non-parameterized settings, graphics, and just about anything can be saved in the AUv3 state. In fact, apps like Drambo don't expose any parameters at all, but save and restore highly complex configurations in both presets and in the host's automatic session save state.
I'm investigating it now. It seems indeed that there is another way to communicate data with AUM (other than the parameters), as evidence suggests that it is possible, but I haven't found it yet.
Edit: I found it. I was a bit confused with the sequencer state not being saved, but that seems to be working for me at this moment. The Midi mappings and Bus settings are indeed not being saved, but that can be fixed.
Even if mappings can’t be saved in presets, they need to exist between sessions. I change mappings and order of pads and it’s like the app is in its default state every time the AUM session loads…
+1 this is an important one. At least now we have a “clear” button for patterns, but you should be able to have the sequencer not play when inserted in a host/daw,