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
Sorry if this has been mentioned already (so many Fluss threads , it's hard to keep up!), but is there a way of recording automation in the "scan speed/fliter" box, so that just a subtle movement is recorded and then repeated? I have to say, I don't really like the fact that with friction turned to zero, any movement of the blue circle will continue on that trajectory until it hits a wall and then bounce off it. I want to be able to just make a small circular movement to get some subtle filter modulation, without the blue ball wandering off. Is this possible @brambos ?
I would like that option!
As a workaround, you can of course do it with lfos
It sends out automation, so if your host support it, you can use that to record AU parameter movement and repeat those.
In my senior year high school history class we had a team assignment to create a short educational film about some issue or another. Most of the teams did documentary type films but some got rather creative.
The winning team named themselves "Great FLICKS Productions" (The Best FLICK films in town). Their titles had close kerning between the L and the I. The class was in stitches. It was all the teacher could do to keep a straight face and pretend that she was oblivious to the joke. 😂
I wish I could @Gavinski , but try as I may, I just cannot get my head round using LFOs in the iOS environment..... Just can't figure out how to do it.
I don't really understand what that means, but I will investigate it. Thanks man!
Well, for example (not necessarily the only way): in Cubasis you can record all movement of knobs and pads and sliders of my plugins. If you fiddle with the XY pads while recording and loop that bit, it will do what you're describing.
Maybe this will help @Kashi the lfos are covered at the start of the vid. Same basic principles will apply to other lfos. If you're not very familiar with midi in general, Pt 1 vid is also worth a watch
Drambo does this beautifully. A couple of instances of Fluss and Spacecraft, everything recorded and automated, is my current favourite thing.
Excellent tip, thanks! Mental note to self: I need to dive into the automation possibilities of Drambo.
Great! Thanks @Gavinski @brambos and @monz0id . Really appreciate the help
@monz0id any chance of a quick video, demonstrating this?
Or if not, then a clear step-by-step explanation of how I would set something like this up? Would be eternally grateful!
I use the parameter lock option, so it records everything - pitch, speeds, etc. - just activate p-lock, click record, and start twiddling! I then put it through a couple of fx (again lots of automation), create a few tracks with different bar lengths, and you get a lovely evolving ambient thing.
(Edit: actually you don’t even need p-lock to record automation with Fluss, just hit record)
I found Doug’s vid helpful for p-lock:
Doug’s vid is a good place to start with p-lock, but I’ve just tested Fluss without it, and it recorded all knob movements anyway - same with Spacecraft. I’ve had Drambo since it was released and only just now getting into it properly, so one of the others might know a better way! Doug’s beginners vid was also really helpful to me for getting started.
LOL, brilliant!
Bram/BeepStreet collab confirmed.
Side note to the other self: There are two ways to make AUv3 parameters available on the AUv3 container module.
1. Hit "MAP" and tweak the respective control on the AUv3
2. Hit the (n) field to show a list of available AUv3 parameters.
LFOs are used to move knobs, or sliders, or etc on an app automatically, thus the term automation. It’s an amazing way to add movement and evolution to any sound, midi fx or audio effect to make it come alive and sound different over time. You can set a range, a waveform, etc… to dictate exactly how and when you want the know to move. Or make it go crazy random all over the place.
Simply put it’s a way to move any parameter (ie knob) on an app without touching it. The lfo does the knob turning for you.
Hope this helps.
Na ah. Really?
Can someone please share a screenshot of all the parameters exposed in AUM? Thanks in advance.
Oh also… if anyone can help that be great. Im on the verge of buying it but want to make sure my iPad can handle it. I’m guessing the app is over 400mb because of the audio files included? How is it on DSP/CPU?
@brambos Any plans to accept mp3 or other audio files other then WAV?
You can see the size on the app store. It's very light on dsp, I've found. I've had tons of instances running no probs. Someone else will have to send u that screenshot but I can tell you that I think almost everything is exposed, except the record knob, which I'm sure some ppl would like to automate on / off for
The 3rd method would be to skip the manual assignment, hit record and tweak until you're done
This way all recorded parameters will get a knob in the AUv3 container module... (This is the way I do it, I'm lazy).
possibly the best app of the year. immediately helped with so many songs i’ve been working on.
was wondering if it’s possible to control the speed of the grains. looks like you can control the amount of grains but there is this inherent speed that they’re always going at that i would looooove to control. plz tell me i’m just missing something.
Super great to hear!!
Do you mean the interval between the grains? That's pretty much tied to the amount/density of grains.
The other "speed" is of course the pitch of the grains (the speed at which they're being played) which can be controlled using the pitch/octave XY pad.
Is that what you mean?
Basically Everything is exposed, super light, typical Bram greatness, get it now, lol. Awesome thanks for that info I wanted to confirm.
I did see the size, I was just wondering if maybe it was that large because of loaded presets with audio files?
Yes, basically. There’s a whole slew of presets using samples from Hainbach’s vast array of stuff, and I’m pretty sure elsewhere in all the brouhaha (possibly in the chat for Gav’s video premiere) Bram confirmed that that’s where most of the size comes from.
Very interesting. Thank you for the suggestion.
thanks for the response!
meaning like when i reduce the grains to just one there is a tempo that the one grain is going at that i can’t really seem to change. i know you guys were trying to get away from the quantized and sync paradigm, which i totally respect! it would just be cool if there was a way to make the grain go like reaaaalllly slow or reallllly fast. messing with the pitch seems to give an ever so slight change to this built in tempo but nothing that extreme. like i said, maybe i’m missing something? either way, if this doesn’t exist, still an amazing app that i will probably use forever.
oh also, maybe another colored skin for a future update? something a little darker for those hermit music makers that like working with all the lights off
I noticed some strange behaviour while playing with this today.
Using a plucked sound with only the volume on the first play head. When it reaches near the end of the wave the grains separate and jump to the start.
When the play head reaches the end it loops the the start and joins the grains again but retriggers the start of the sound again.
You wouldn’t notice this in the normal granular chaos but it looks like a bug.
I also had something where I found weird behavior - spread was at zero and I only had one playhead active, but the grains were in a completely different part of the buffer from the playhead