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
You can trigger loops via MIDI messages. So, you just need to find a sequencer of choice, tell Loopy which MIDI messages trigger which loops, and send those messages to Loopy from that sequencer.
What do you mean by re-sequence? There are quite a few good tutorials out there. It might be worth your while to check them out. Sound For More has a pretty comprehensive set.
How would you stop loopy spinning? Midi to stop?
I think I will setup for looping anyway. Then go from there.
Thanks. Will check vids.
What do you mean? How do you stop Loopy's clock or how do you stop individual clips from spinning?
Also are you asking how to stop/start them via MIDI or generally?
These are pretty vague questions.
It depends on how you want to do it. One easy way is just a toggle. Send a midi message to start the loop if idle, send the same message to stop it if playing.
But it's completely flexible. For instance, you could send a Note-ON to start playback and a Note-OFF to stop it. In a sequencer this would look like one long note for the duration you want the loop to play.
I know you're used to thinking out loud in threads, so I'll leave-off offering more suggestions unless you indicate that you've experimented and are stuck on something in particular.
When session recording puts a clip on the timeline it adds a fade-out at the end. How can I avoid this?
When I stop a clip early during a session recording I still get a complete clip in the timeline if the first time through that loop, and a partial clip if past the first time. Is this expected? Can I change it?
There shouldn’t be fades on your seg unless you have fades applied to those loops. Do the clips have fades turned on?
If you only play part of the clip, only the portion played should be record. If that isn’t happening, it would probably be worthwhile to screen record a demonstration.
It seems fades were applied on loop & global. Turned both off, works now. I don't think I ever set that up, didn't know it existed.
Here is screen video of the whole clip being put onto timeline by Session Record.
Huge thanks for your help yet again, @espiegel123
How did you stop the clip? Did you stop it by tapping on the clip or by tapping the transport to pause?
What is the play/stop quantization setting?
Pressed (red) Record button to stop. I've also stopped by tapping on clip, same result.
Play/Stop quantization is Master. Is that the problem?
Where should someone new to looping & Midi etc. go to piece together a sufficient mental picture of all the terminology? These seem to be second nature to the more experienced but quite a hurdle to me.
Even with quantization set to master, as long as you leave the transport running, it should only record to the sequence what actually plays.
Here is a quick example where play quantization isn't set to master.
But I just checked and master will record partial clips. It'll record whatever you perform.
If you stop the transport, it probably adds a full clip if a clip is still playing. Stop the clip then stop the transport.
Can you post a demonstration of a case where you leave the transport running and stop the clip before its end and the full clip is added to the sequence?
Does "transport" mean the record / play head in the timeline?
Just tried this (tap clip to stop, then tap red record to stop transport) and it behaved correctly this time. Since I previously had the fade-out set, perhaps that probably it to keep going after tapping the clip.
transport means the play/pause button at the top of the screen. Fade-outs happen after you tap to stop the clip from playing. It is like a synthesizer's release time.
Got a bit further, then hit this puzzler. A clip has Speed=2x, everything else unremarkable (to my eyes) but all settings shown in below video. Session Recorded an initial snippet from the clip, and the timeline shows a different portion of that clip with a strange blip resembling the end of a clip, and plays a different portion followed by silence.
It looks like you stopped recording before stopping the clip's playback. Does the same thing happen if you stop the clip's playback before tapping to stope recording?
Yes. Here's a version where I tap the clip to stop it, wait a sec, then tap the red Rec to stop recording.
@Michael
I also just removed the Speed=2x setting and still get the weird (but slower) Session Record result.
do you get the same result if you save and reboot the app?
Crashing loads in aum. Just mapping a system. Seems to be when deleting a loopy au. Crashes all loopys.
Yes
Please send the crash logs to @Michael. Info on how to do that:
https://loopypro.com/manual/#reporting-crashes
What does "just mapping a system" mean? Can you describe steps or make a screen recording?
Aum. 8 audio channels of x 2 loopy per channel = ( 8 loopy unmapped. 8 loopy mapped. 7 donuts mapped, per mapped loopy ) 56 launchpad buttons of just play/stop per donut = 56 play/stop mappings.
When deleting a loopy it crashes all loopys. Latest crash. Midi mapping the notes from launchpad x. Crashed as soon as I tested mapping.
Loopy. Or aum. Or launchpad x. From hst 2 of audio4c. Via aum matrix.
Hst2 to each mapped loopy. Plus hst2 to aum midi control.
Will try to map. Then record if it crashes. I keep having to route the midi via aum matrix after crashes though.
Would you mind finding and sending me your “Loopy Pro AU” crash logs? https://loopypro.com/manual/#reporting-crashes
W.> @Michael said:
Sure. Thanks. Mapping further now though
Are you saying that you have 16 instances of Loopy loaded in AUM?
That is a lot of Loopy instances.
What is AUM providing as a host that Loopy wouldn't?
Not sure. Thought maybe mapping effects to a controller and synths. Make channel templates. Copy node settings to channels.
16 instances seems like a lot of instances of any AUv3. Have you considered using Loopy as the host given how many loops you are trying to load?