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.
I understand Beatcutter now
Feels like a great achievement! The hardest things I've done in a long time and the only reason I got there was that I was sick in bed for 4 days. It was not an enjoyable process and at times I felt great frustration and almost gave up. Great thanks to Almost Aviation for helping me get unstuck in a few places. He was so generous with his time and actually posted a video for me. Also, great thanks to Leo at SoundForMore for his very great tutorial series. Really helped a ton.
Comments
I really need to check these tutorials out. I love Igor’s apps but this is the only one I haven’t been able to click with even though I’ve tried. Glad it’s working for you. I may work on this tonight now 😎
I seem to remember that Jade did a useful video on the app:
I wonder if anyone will ever be able to write a workable understanding of it into less than a thousand words.I’ve gone through a similar compressed but intense learning process with this a few times now where I’ve understood it enough to use it, then been so exhausted from the worry that I’ve not used it again until I’ve forgotten everything again 😂
I'm thinking of trying to do one myself but it would be daunting cause of the sheer number of parameters and connections in the app. I still have some unanswered questions. Wish I could talk to Igor directly
I'm sure u could email him, he's very friendly and passionate about his apps
Ha, I didn't even think of that! I must be putting him on a pedestal. Thanks for the idea!
It’s definitely a much more straightforward tool to use once you figure out to start with something simple then build on it. What makes it daunting is having way too much going on at the same time, but it’s not really too hard to get to grips with the essence of how it functions.
Yeh, I think that is true. I had to start with one track and just test out every parameter. I should have taken the time to read the whole manual, but in the beginning when you are trying to grasp the fundamental concept, it's hard for anything to make sense. Reading it now is really helpful cause I understand how it's all interrelated. One thing I'm still trying to figure out is how it internally processes the input audio. If I load a file, does it continually scan and loops the audio file when you START it? It sounds like it keeps resetting them periodically to the beginning because I hear bits from the beginning and not throughout the whole length of the audio file. I'm talking about audio files that are minutes in length.
I meant to do a follow up vid to my original Beatcutter tutorial after I properly understood it, but never got round to it. It's really useful to just put in a sustained one note drone and start playing from there, systematically adding things and avoiding adding any modulation. This is a great aid to understanding the app. If you start by feeding it complex input it is hard to grasp. The manual is really tough going though, for sure, initially at least.
My brief experiments show that it harvests the sounds from wherever it has gotten to in a linear play-through of the source file. I verified this by setting a single input and output bus, loading a very long file and letting it run. If you turn up the 'direct' slider on the INP page (but keep it quite low volume so you can distinguish it from the mangled output), you can hear the input file being played while watching the playback position on the waveform at the top of the screen. You will hear that the mangled playback slices gradually begin to catch up with the direct output.
This behaviour may be obscured according to what 'repeat' and 'skip' settings you have on the CTRL page. These will be more or less unpredictable if you are using randomized templates or tweaking blindly.
(MarkH a.k.a. Almost Aviation)
That would be good to hear. I think a lot of people struggled with it at first, but second run through seems to have a lot of good results.
Thanks so much! Yeh, that's a great idea on how to test it! I think you must be correct about one of those settings cause they are off the initial values. I probably inadvertently changed them messing with the template. That is one reason i wish everything were visible on one page. I guess all the important parameters are kinda if you are relying on the template page.
Looking forward to spending time with Synthscaper next. Sounds absolutely amazing on first listen…
Very helpful thread as I’ve been wanting to learn the app properly for sometime. Definitely gonna do this my next off day.
Thing is... I just don't really enjoy using this. Same goes for Glitchscaper. Just not the kind of app interactions that inspire me musically
Thank you so much for this. Really helps break through the confuzzlement.
FWIW, I wrote directly to Igor about a question I had. I wasn't sure how the audio files were played back under the hood. I assumed they were looped continually from beginning to end. I said I wasn't sure cause I kept hearing bits from the beginning of longer audio files, like it was restarting the playback. Here is what he said:
"In fact, the BeatCutter just plays the file from beginning to end (in
a loop). You can hear it using the Direct control on the Input panel.
The trigger starts recording when the signal exceeds the threshold set
by the Sensitivity control in the Trigger panel. Playback of the
recorded cell is started by the sequencer. The Repeat and Skip options
in the Control panel define how many times a cell will be played
before it becomes available for recording again. The case you describe
can occur when the triggers are very sensitive, the speed of cell
playback is slow (params Octaves, Cents, Steps in the Control panel),
the number of repetitions and skips is large. All cells will be
recorded when playback starts, then they will repeat the playback of
recorded piece."
I’ve thought that about so many instruments though, and ended up with really satisfying results after persevering with something. Mind you, I’m also the kind of masochist that will work their way through a 19th century book of piano exercises…
Im probably buying an ipad just for mainly beatcutter. I can actually just use 2 other ipads. A background aum ( and theres a Drambo drums ) sends to other ipad. Or with that feedback app. An aum to a Drambo via same ipad becuase of the feedback app.
It seems you get more cpu when using another host with a host. I can actually just use beatcutter how Iv decribed.
But just cant not have a beatcutter ipad now.
I guess I gain functionality and cpu. Not faffing with all sampling apps and effects on a synth only ipad.
Weird setup though with the feedback app and another ipad. Its aum. Feedback app to Drambo. Headphone out to line in and to another drambo lol.