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
OK. So, I bought it. I haven't been able to repeat the AUv3 issue I had .. don't know, it could be interface related...anyway..onward. One thing I would like to see is the Solo and Mute buttons working in a better way. First of all, if I disengage a Solo all the Mute states are released as well.
Also, would it be possible to have multiple channels in solo at one time? I can sort of do this with a manipulation of the mute channels - unmute channels while the Solo is engaged, but as soon as a Solo button is disengaged all the Mutes that I want muted are cleared as well. It might be nice to have the solo buttons latch and then have a master button to release them all (like AUM and Auria Pro).
Maybe this is already sorted somewhere. Just something I noticed.
Loving the rest of it so far as it starts to make some sense.
Oh...and Happy New Year everyone....
Gonna see how this workflow comes together:
also for resampling ，LP can be load as au inside LP 。clips can than be copy and past to where you want， and may be one day you can even drag and drop it （i thought i read about it somewhere）
That's a really good idea. There should be some interesting ways to use that.
Are you aware that you can resample within the standalone without needing an AU instance. You can set a color as a destination for a color and resample that way.
Zenbeats could be seen as reference in sample/loop preview. It lets you listen to the file in context while you play your project. Can adjust the volume of the file being previewed plus it plays it in time with the current bpm. You can listen and go through drum loops or whatever and hear exactly how they’d work. One of my favorite features in ZB.
Another report on running Loopy Pro with an iPad Air 1: a couple of times, I've found that hosting an app in standalone mode gives me crackles when hosting the same app in AUM and running the output into Loopy Pro does not give me crackles. (The apps in question here were Moog Model 15 and Audio Damage Continua.) If there was a difference in settings, I haven't found. (Buffer size was the same in both, 256.)
I'm planning to buy an iPad Air 5 when they become available (early this spring, I hope). In the meantime, I'm grateful to Michael for supporting iOS 12. I can't tell yet how often I'll be using Loopy Pro as a DAW/host. But its primary function -- looping -- works beautifully. When my 7 day trial expired, I didn't hesitate to purchase the "unlock" IAP.
I'm not really a looper person, but I pulled the trigger on Loopy Pro as my free trial was ending. I'm buying it as much on its promise as on what it can deliver today. Gotta pay developers if you want to see more development!
I'm really looking forward to midi loops, and there are a few other things I'd like to see (access to AUv3 parameters for automation is a big one). But anyway, so far I'm having a blast with it, and I love that there's something that's almost as easy and flexible as AUM but with a more explicit DAW focus. 2022 is going to be a great year for iOS music, and LP is going to be a big part of that, clearly!
Awesome!!
Hopefully it will be available on Auv3 version. On future update.
Anyways to copy paste with the settings of donut pasted?
Hopefully what will be available in the AUv3 version?
make a momentary 'hold to set the send to >delay to max' button for some dub-style >delay action
Get off my use case! It’s my use case and no one else’s ;P
I'm trying to set up a retrospective looping template. In the metronome area, where it says "bars", I'm setting that to 1 bar...hopefully that's okay, as I would like that visual indicator surrounding the BPM readout to display the beat. Beat 1 is in the top right quadrant, like the face of a clock.
I'm also using a 1 bar blank loop to keep the metronome running.
It looks like when "Retrospective Quantization" is set to "Quantized", it grabs the correct portion of the audio (only the bars which have finished recording, and not the current bar) when I'm using 2 bars or fewer.
And when it's set to "Immediate", it grabs the correct portion of the audio when I'm using 4 or 5 bars, and probably more. Haven't tried it with 8 bars yet. But when I set it to 32 bars, there seems to be a glitch. Doesn't seem to work with 32.
The donut just glows without showing a waveform when I tap it, and then becomes unresponsive...if I pause the playhead, and then tap the donut, it records non-retrospectively.
Am I doing anything incorrectly? Are these known bugs?
You don't need to do that. You can just set "Pause Clock When Idle" to off.
Humm ... yes it seems not to be working as I'd expect all the time when using 1 bar at the master level then setting individual clip lengths. I've always just set it at the master level.
Oddly, when I stopped the transport during one of those cycles, the clip filled up, and when I re-started the transport, everything worked as it should.
I don't think this is a known bug. This will take some testing to find reproducible steps. It'll get reported in the beta channel when a little better nailed down.
@skyblazer: retrospective immediate with a clock of 32 is working for me (though quantized is behaving strange).
@Michael : i just tried this out and at 32 bars things behave funny for me when retro is quantized. If i make sure that at least 32 cycles have played, retro quantized seems to start a count out rather than capture what is in the buffer. immediate is working ok for me. I tried this both with a widget that retro records next tap and by setting clip settings to retro quantized.
Interesting. I wonder if perhaps it failed to allocate enough memory. Can’t remember if I actually report the allocation failure to the user or just fail silently. If it can’t allocate the buffer, it will continue to use the smaller size, which would explain the behaviour that you’re seeing
That could maybe relate to it behaving better after I stopped and started the transport. Maybe it re-allocated the buffer or something.
Could be.
It’s the downside of working with 32 bit stereo audio – tends to take up rather a lot of room
Haha! It’s great, isn’t it?! I haven’t even looked at the other functions like widgets and the timeline thing yet. So much fun!
Love seeing these custom templates appearing in u tube videos. Some really cool stuff being shown off. What a app!
..
Nice video thanks for sharing.
I’ve had some issues getting consistent performance from a couple foot pedals sending MIDI info. I tried an Airturn BT-200 S-4 (Bluetooth) and my voicelive 3 plugged in via USB. Both registered midi input when I was assigning MIDI…however, only one button on my Airturn pedal seemed to actually trigger when not in assign mode and my Voicelive 3 wouldn’t trigger either. Are there certain CCs that don’t work? I was able to get my IK Blueboard Bluetooth pedal to connect and trigger, but I wasn’t as happy with the soft pedals for looping (foot tactile experience).
Any ideas?? Help? Thank you so much…I’ve been setting up a huge looping template for a few days, but I’m getting hung up on this hinge point…
Check with a MIDI Monitor in Loopy to see what MIDI is being received. If you MIDI learn from the pedal, it is sometimes necessary to manually change the learned trigger (on, on/off, hold, double-tap). Sometimes Loopy will guess that you want Hold when you really want On or On/Off.
There are notes about how to insert a Midi Monitor in Loopy Pro here:
https://wiki.audiob.us/doku.php?id=loopy_pro_troubleshooting
Thanks for the recommendation! Unfortunately, it’s still not working.
I don’t think it allowed me to upload the above image, but basically, that’s what I did. I changed it to on/off from ‘hold’(and tried it the other way too). I put a midi monitor in to view what was passing. It shows the MIDI info and it’s assigned to a button(which works), but the pedal won’t trigger it.
@Jojo, how did you get to that point? I don't see any action such as "Press" and I don't see any CC type such as "On CC 16" or "Hold CC 16". I haven't figured out any way to get to a button setting that looks like what you show.
Yeah, I think what’s missing here is that you have to specify which widget action is supposed to be activated by your MIDI message.
In case @wim's clue wasn't enough. Do you see the '>' next to Action. You need to tap that and assign an action to tell Loopy which action. Normally, it automatically chooses 'Press'. I am not sure why it didn't.
Hmm, it seems to be accurate…
@jojo, it would be super helpful if you could state the steps you went through to get to those two screenshots. Particularly that first one. I just haven't seen a path to getting to what you're seeing in that first screenshot.