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.
Loopy Pro Questions
This discussion has been closed.
Comments
Some are just static. Loopy isnt much dsp. Do you think its not ideal even 8 loopy au?
Loopy is light on DSP, but there is also memory overhead to consider.
Thanks. Mapped without crashing. Will use loopy host if need be.
@sigma79 : up-thread you asked some launchpad led configuration questions, but I am not finding the post. With the Loopy host, it will automatically set up matching colors and reflect loopy clip status on the launchpad if using one of the launchpad models it supports.
Have anyone used loopy with the new Ableton 11.2b update?
Loopy isn’t available on Mac is it?
Is it possible to configure a loop so that when started the first time it starts at the top, but when stopped, its position / playhead remains right there until started again? i.e. a "pause-able" loop?
I don't know of a way to do that for loops independently. There is a way to pause and restart the clock without resetting but that would apply to all clips.
an overkill way of doing it would be to embed the loopy au and putnyour independently pausable loop there.
Thanks. Instead, I exported that loop and used an external app to split it into 2 audio files at my pause point.
But now when I import those files Loopy changes their playback speed
and I just want them to play exactly like the original. Have tried some loop config changes with no luck. Any ideas?
It sounds like you had time-stretching turned on when you imported. Make sure you turn off time stretch when importing. Otherwise, when it imports it will time-stretch the audio permanently. Once you have a loop in Loopy, you can make sure that no additional non-destructive time-stretching is done by turning off the time-stretching option in clip settings.
The other thing worth mentioning, you can duplicate the loop in Loopy and change the trim points for the two copies so that one is just the first part and the other the second part without needing to export and reimport the audio.
You were right (of course). The audible change was huge when I had time-stretching on. But I had some trouble even with time-stretching turned off, will try it again.
Ah, thank you !! I assume I do a loop-copy and not an audio-copy?
There shouldn’t be any alteration if time stretch is off in the import dialog (if there is a demonstration would be useful so Michael can investigate).
There should especially be no change if you also have time stretch off on clip settings.
I am not sure what you mean. Both should work fine. There are many ways in loopy to copy loops/audio. It shouldn’t make a difference for this.
All of my clips suddenly started appearing as white areas in the Sequencer window. This is happening for all of my projects. I think it may have started with the 1.0.12 upgrade, but I'm not 100%. An iPad restart does not fix it. Anyone else experienced this?
I am seeing it and others have reported the issue as well.
Ah, good to know. Thanks. As long as Michael is aware of the issue, I know it will be resolved quickly. FYI to all, even though all clips are white, they all still play and behave normally.
How to config a loop to have a few seconds fade-out after reaching its end?
i.e. fade away over the first few seconds of the next repetition of that loop.
use a fade out and set the play quantization to 'loop'. The fade out will happen when 'stop' happens. So, it will get to the end of the loop and keep playing for the fade out duration.
Doesn't that also change the start-play quantization?
You can use any quantization that would stop the loop at its end. The fade out will always start from when the loop "stops". So, any action that would loop to stop at its end will have the same result. Try it.
Thanks! I now better understand this in normal view. Can I get fade-out on clips in the sequencer / timeline?
I don’t remember. Try it out.
Thanks, but I was not able to get it to work in sequencer, hence my (badly phrased) question. Don't know if it is supported there and just not yet documented, or more operator error on my part
It may not yet be working in the sequencer. @Michael ?
It does work.
I tried it last night with the current beta and just now with the App Store version. All other settings at default, just add a fade out under playback settings for the clip. The clip begins the fade before the end of the clip so that it reaches zero volume by the end of the clip region.
@des1303, there must be some other setting preventing this from working for you.
The fade out behavior is different in clip mode than it is in the sequencer. In clip mode the fade out happens after the clip stop event. In the sequencer it happens before, so that it's complete by the end of the playback region.
It makes sense to me to have it this way, but it might confuse some people.
Thanks! Wow, and I kept trying to get it to "work"
... it confuses the heck out of me, I play a loop in clip mode and get a fade after "Stop", and I expect "Stop" in Sequencer to be where the audio blob ends. I hope it's a bug. Or that some visual "fade" indicator can be added. Or both ! 
I don't know, it makes sense to me. That's the way any DAW would work if you have clips in the timeline and put a fade on them. And, I can't really envision the clip behavior "pre-fading", even though that would be more consistent between the two. A visual indicator of the fade time in the sequencer would be helpful I guess.
This is an interesting question to put to @Michael , I think.
Interesting point, although I think manually setting a fade curve feels different, and includes a fade indicator (at least in Reaper). An orchestral conductor would indicate when the fade begins (and not just when it ends ... I know nothing about conducting orchestras :-) Yes, Michael has likely thought through this.
The more I think about it, the more I feel like it should be consistent between the two views ... even though the way it works now seems to intuitively make sense to me in both views.