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
Sweet. Thank you.
Yes, everything is possible if you're willing to create menu settings for every different configuration (I could bore you with the difference between input devices and input data sources in iOS, but I won't 😉). I just want to support the 90% typical cases for most people in the standalone. The plugin will let you use it in all the other exotic combinations
thank you dude!
I got that. Yeah, I think I'm getting lost in speculating possibility and not so much focussed on 90% typical use as you say. I do that sometimes. I hesitated to even mention it at all to be honest.
ps. great update by the way! Gracias!
Thanks for the update. Love it even more!
Hoorah! Thank you, Bram!
This is great!.
Now, I know it’s cheating... but in some cases I’d really want to have the “rec” to start at precisely the beginning of a beat. With the rec being exposed, I guess there’d be a Mozaic script or something to be able to trigger the rec in sync and the beginning of a bar?.
One something would be a sequencer whose note or CC events are mapped to the record toggle.
But reading your message again, I think you're imagining a button in Mozaic that syncs the record trigger to the next beat.
If you place a single note in LK, keep Trigger Quantize on and set to 1 bar, and turn off looping for the clip, it makes a perfect Gauss Record trigger in AUM to start recording at the bar division.
(Of course you have to do the Midi Ctrl routing in AUM, too. Let me know if you need further guidance).
Yes, like press rec and have time to reach the note in a guitar... or sing or whatever. Also interesting in the case of drums if being super accurate is of importance.
Good idea!. I’ve never used LK with loop off. Sounds perfect. And good visual indication too. Winner 👍
Btw: when you do stuff like this in LK. Do you use the automation lane?. Cos i prefer notes in these cases, easier to see and manage. But then you’d need a converter...
@brambos Thanks man. Serious business and so so great. Appreciate your work.
No. I put a single note, and in AUM I map the AU parameter to respond to the same note.
In AUM, you can choose between Note, CC, or Program Change message types to match the type you are sending in.
Damn, that’s right!. You’re helping me out of the “making my life complicated” mode. Thanks!. Gonna try it right now
👍🏻
Super easy. You can do this with atom also. Hence my perfect loop comment.
@brambos You rock! (and roll)
Sweet! Thanks.
I gave a session this am with my nice headphones on and was quite surprised by the sound the record button makes when engaged. Brambos I love that app and truly think its fantastic!!!!! But what about that noise in a live situation? Going over some loud PA’s or Monitors that is very audible. Anything you can think of to lessen it?
Thanks for all the updates and I do love the app...... just curious about the 1 thing.
Cheers.
It's good @Gavinski mentioned this. The noise is there, it's minimal but it's there.
So there are two types of noise. Which one are we talking about?
a subtle 30ms low-frequency pffffft sound which masks major sudden discontinuities between monitored playback and recording? This one I can't do anything about unless someone invents a time machine to warn me in advance that the user is going to press that button (or add a 30ms latency to everything, which I'm not willing to do).
a nasty prprrprprr crackle the first time you press record? This one I thought I had killed. It's the undo feature, writing all the audio data to file before the recording gets overwritten and causing a timeout on slow systems. If it's still there, let me know what kind of device/iOS you're using - because this was supposed to be fixed.
So the noise I get is the Pfffffffffftttttt. I guess it surprised me a bit as I was isolated in the dark with my cans on. Thanks for the explanation. Once again thank you for all the work on this!!!!!
This is what it is like for me Bram, very noticeable if performing live.
(Unlisted vid)
Yep, nothing I can do about that. As I said, that's a subtle as it will get, unless you like latency.
Ok, thanks Bram
Imperfect workaround: audio monitor and Gauss in separate tracks [AUM]. Maybe set up a trigger that starts record in one track and mutes the monitor in the other.
Can you explain this? Do you mean use 2 busses?
A one-bar count in before record option would fix the time machine problem.
Here's a quick explanation of the problem: if you want to avoid these sound artifacts, you need to crossfade between the previous audio-stream and the new audiostream. Sudden discontinuities cause clicks, and a crossfade solves that.
Except the new audiostream overwrites the old audiostream as soon the user hits the record button. So there's nothing to crossfade between (you can't "store" the old audio either, because it's live-processed with effects and sequencer, etc. which are needed for the new sound instead).
The only thing I can do is take the last bits of the old stream and spread those out over the beginning of the new stream - essentially stretching the click to a low frequency pfffffffff sound, which is less jarring that a loud "TICK!".
It's a bit more complicated than that (due to monitoring behavior), but it gives you an idea...
Would Brusfri work live?