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
You cannot prevent TC-DATA's midi from reaching an app that has a virtual MIDI port. But you can ignore the MIDI coming from it. Somehow you seem to have ended up with a ghost binding in Loopy Pro early in your process and @Michael may have some ideas about how to remove that. But from now on, as long as you don't create bindings for virtual midi events on the channel that you are sending on, it shouldn't influence Loopy Pro.
@espiegel123 , et al: Thanks again for the time and knowledge you all have contributed to my request. Alas, the fault was not in the stars, but in TC-DATA’s lack of virtual midi out channel options. I did learn a great deal about LP’s control settings.
Meanwhile, back at the ranch….
Another question, hopefully a more straightforward one. This is not an urgent request, just a request for info on a possible future project.
I use the Novation Lauchpad and almost exclusively base my projects on the 8x8 template, which triggers loop actions. Is there a similar template in circulation that does the same thing, but with one-shots?
If not, I may spend some time a bit later putting one together, and of course share it with the group in the appropriate venue.
I don’t know of one. Since launchpad (pro mk3, x or mini mk3) automatically maps clips, it probably wouldn’t take more than a few minutes to make one if you have one of those launchpads.
Make a column of empty one shots and copy/paste seven times. Select each column and apply a color and you are pretty much done.
If you don’t have one of the listed launchpads add a couple of minutes to midi learn the pads. The clip color is automatically set for supported iPads. For other models , you coild use the Novation software to set up the colors in a custom layout .
I’ve got the X but I get the gist and will give it a try.
Is it possible to toggle Overdub on/off with a button (as opposed to opening the clip settings then scrolling down)?
@espiegel123 : your suggestion worked like a charm. FYI, the clip colors mapped automatically on the Launchcontrol X.
What do you mean about toggling overdub by opening clip settings. Overdubbing doesn’t require opening clip settings. Can you describe what you want to happen? Overdubbing normally happens when you record in a clip that already had audio without needing to open clip settings.
In the After Record settings. Toggle between Play and Overdub in the clip settings with a button. Without having to swipe up or two-finger tap on a clip.
Setting the after recording option can only be done in the settings. There are no actions at this time that change any settings as they appear in the panels
You can overdub without changing that setting.
You can set up a widget or binding that has an alternate setting or set up a gesture to use an alternate setting.
Got it. Thanks.
Another (hopefully) simple question: I’d like to trigger loops using an external keyboard when I don’t have access to my Novation Launchpad. Where can I find how each pad is mapped in session mode by default? Assuming they are triggered by note in. Cant find the default map in the user manual. Thanks!
You could use a MIDI monitor to see what the Launchpad is sending. For example, StreamByter. Load it in a host, route the controller to it, tap the magnifier icon to open the monitor.
The automated bindings aren’t in profiles and are dynamically generated based on what is in the layout. You can use a midi monitor to see what the session mode pads send out. They would also be listed in the Novation programmer’s guide which you can find online.
The quickest path is probably to midi learn from your keyboard.
Didn’t see it in the programmers guide, but I’ll check again. I’ll probably go the midi monitor route. Thanks for the tips, all.
Hey, how do you guys get your relative encoders to work smoothly ?
I get only 10 steps using the 127/1 or the 64-centered relative MIDI conventions.
The relative knob is controlling a dial, but it's the same thing with an AU.
New project, latest update, ipad mini 5 17.4, mpk mini plus or x touch mini.
Just to confirm, you are configuring the encoder on your controller to match the relative mode in Loopy Pro?
When 64-centered relative midi was added, a bug was introduced that resulted in relative MIDI making coarse rather than fine adjustments. It is on the radar to be fixed.
I am not sure of the time frame for a fix. Michael is working like mad to get the MIDI Looping release (which has a lot more to it than just midi recording and playback) finished. So, the quick-turnaround point releases aren't going to be so quick for a little while.
Yes they're both configured at 127/1. On the x touch mini, there are 3 modes :
Relative1 = 127/1
Relative2 = 63/65
Relative3 = 65/1
The mpk mini plus is fixed to 127/1
Both controllers give the same result in Loopy. I don't have an other one on my hand, but maybe you can try the same ? It'd be good news if your result were different !
As you say, Loopy interprets the values as coarse, at 64 centered but also at 127/1, so I do hope I'm making a mistake.
And I figured Michael must be busy, and I wish him good luck in this complicated journey.
@Etienne : you aren’t making a mistake.
Oh okay, I thought there was a bug only with the 64-centered convention, instead it's a general one with the relative mode.
I was just trying to get this workflow :
Dial widget (linked to AU instrument parameter & mapped in relative cc controller)
-> Dial sending CC values to Drambo AU sequencer for recording automation and stuff
-> Drambo to AU instrument
So when loading a different instrument preset, there'd be no jumps (for example VCF cutoff) nor waiting to reach the new value in absolute mode. All of this for 8 different channels (1 instr / ch)
Writing this made me think I overcomplicated things due to my past with loopy inside drambo and can be done in a simpler way using midi feedback directly with my controllers.
(Although I don't know if I'm even making sense now)
@Etienne : unfortunately, there isn’t a workaround. It is coarse whichever Métis used at the moment.
Thank you for the info @espiegel123
In the meantime the coarse bug (probably introduced in 1.1.20) gets fixed, I kind of found a workaround. The main idea is to make the dial receive normal CC with my relative controller by other means, but keeping everything in harmony.
1/ The virtual midi port is assigned to the dial knob
2/ An other app (midifire in my case) is hijacking the virtual port.
In between in and out, drambo midi fx is receiving the CC changes (absolute) through the module CC Controller. My relative physical knob is midi learned to the same knob but with a different CC (if it's the same CC, drambo can't receive both CC from the input and from its midi learn function).
3/ The CC is sent back into virtual midi
Voilà
Nice trick. I think you could host the Drambo midifx in loopy pro directly and not need to run MidiFire or standalone Drambo. Route the you route the midi to Drambo as an AU and set up a binding from the AU to yhdd Ed parameters you are controlling.
Thanks.
I used the virtual midi binding because it has midi feedback, thus sending CC changes to virtual MIDI when changing an instrument preset.
Do you mean I'd get the same result replacing the whole dial section with a drambo AU bound to an Au instrument parameter ?
@Etienne : I hadn't considered the role that the MIDI feedback plays in your workaround. I don't think Loopy does MIDI feedback to internal midi sources. So, I may have been wrong about being able to use it.
@espiegel123 Right, seems logical since it's supposed to be a visual state feedback for controllers.
Anyway, thank you for your help, I'm satisfied with the current knobaround.
(sorry)
@espiegel123
So... after overthinking some workarounds for this endless encoder / relative / incremental knob coarse bug, I think I found the simplest solution there is.
Let's say you want to midi map a dial widget with your endless encoder :
Very clever! Great workaround...and sorry that you have to workaround it,
Thanks ! I hope it can serve others 🙂