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
It happens when rotating 180 degrees. The mixer returns to the proper orientation, but the layout does not.
Right, I didn't mean that it could fix a jumbled layout. I meant as a way of preventing it from happening again. That's good information about being in edit mode when doing the rotations. Have you seen the jumbling happen when you were not in edit mode?
Yes, after further testing, even when not in edit mode, it can get messed up when turning orientation lock on and then off and rotating (as shown below). It can get locked into an incorrect portrait mode orientation and into an incorrect 180 rotation. Until these rotation bugs get sorted out, I recommend locking to your preferred orientation using the ios control center.
Hey @Michael - thought I'd ping you about the orientation related stuff in the previous few posts.
@espiegel123 informs me control profiles can be shared, brilliant.
Can anyone please share a Launchpad Pro (not mk version) control profile for Loopy Pro.
Cheers!
I am starting to create a template with my favorite instruments all preloaded. I have 3 pages, each separated into strings, woodwinds and brass. My question is this: is it possible to have an auv3 instrument only show up as a button on the bottom of a specific page? For instance, my “strings” page would have only bass, cello, violin and viola. Then when I switch to the brass page, the above instrument buttons would not be visible, and the respective SWAM brass auv3s would be visible.
I don't believe this is possible.
I started to say that you could define your own buttons to switch to each page, but there are no actions that you could assign to the buttons to set the visibility in the toolbar. You can open and close audio anit interfaces with actions, but you can't toggle the toolbar visibility.
You could, I think add a button on a page to show open a particular AU. It wouldn’t be a toolbar icon but would accomplish much the same.
Yes, you can both switch to a page and open or close multiple AU interfaces from a single button. But that would just result in several open windows, probably covering up much of the rest of the page, and wouldn't save the toolbar clutter, which I read as the goal here.
Yes. Decreasing toolbar clutter is the goal. I plan to expand this beyond the 3 pages I have. The toolbar is necessary to turn off idle on the instrument I want to use next. The only way this works dsp wise is to keep all instruments idle until needed.
Is there a way to have a button that switches idle mode on and off for a specific auv3? If there is, then that would accomplish what I need, and I could simply hide all of the auv3s from the toolbar completely.
It works! Make a button to toggle mute/unmute of an audio source, then target the auv3. It idles when muted.
Yes, there are actions that can mute and unmute audio sources. Muting an AUv3 should idle it unless you've needed to turn that off for certain plugins. You can create a button with actions to switch to a certain page, mute plugins, and unmute them. But, you'll need a separate button for each page, and each button will need multiple actions assigned to it. It will be fairly cumbersome to set up, but should work.
I would test the idea on a smaller scale first to save yourself some setup time.
This would reduce clutter because on each page you would only have buttons for the things you want to access on the page. You would hide the icons for anything you don’t want visible from every page.
Here is an updated version. I haven’t removed the instruments from the toolbar yet, but you can see that everything is idled except cello and violin, which I have toggled on. I opened up the auv3 windows individually, and the idle button turns on and off with the mute toggle as well. Thanks for your feedback.
Oh, I see what you're saying now. Make them all not visible in the tool bar, but use buttons on each page instead. Good idea. Pain in the butt to set up, but workable.
Already done setting up for 3 pages
Loopy Pro has some nice copy paste features. I’m basically in love with this app. Took only a few minutes, and will save me way more time in the long run when starting up a session.
I should have been clearer. But yeah, that is what I meant.
I am attempting to have Loopy Pro receive clock data from a Novation Circuit Tracks. Loopy Pro is recognizing the tempo and “start” but Loopy Pros clock does not stop when I stop the Circuit Tracks. My understanding from reading the Tracks manual is that start and stop are communicated using “real-time” messages. For further reference, start and stop are the same button on the Tracks.
Oddly enough, when I feed the Tracks midi into a quasi midi interface (Yamaha Modx) and send the midi data to loopy pro on midi port 3 (this is a Modx default), loopy pro seems to recognize start AND stop.
Has anyone experienced and or solved such a start stop issue?
I have launchpad mini MK and set up a custom layout for keys. However, the keys are launching clips, I feel like before recent updates the session mode would launch the clips and the custom modes would only play midi notes. Other than setting different midi channels for the Custom midi notes can prevent them from launching clips?
I think this bug snuck into the release and will be fixed in the next update. The only workaround is to use a midichannel other than channel 1 when using notes or custom mode.
Awesome! I was pretty sure it wasn't happening before, good to know it will be fixed.
I found a few other minor things that I thought I'd let you know:
Don't mean to add more request, just thought I'd let you know. Thanks for all your wonderful work!
@Michael
Am I correct that there's no way currently to have one button widget press another button widget either side-to-side or up/down? I see the examples of Next/Previous Scenes but they all seem to play clips in a row or column--I want to do that PLUS mute and unmute AUv3s progressing through scenes controlled by Next/Previous buttons.
Can you explain why you need to use more than one widget to do what you're saying? You can have multiple actions tied to a single widget.
That said, yes, you can trigger other widgets from a widget. If you look into the list of actions, you'll see "Widget Actions".
I want the numbered Scenes to play clips AND mute/unmute different combos of audio sources. I don’t see an option to play widgets in a direction on the grid. I have two buttons that I want to MIDI map to the prev/next buttons to do stuff like:
scene 1: play row 1 loops, mute beathawk, unmute Poison
scene 2: play row 2 loops, unmute BH, mute Poison
scene 1: play row 1 loops, mute beathawk, unmute Poison
scene 2: play row 2 loops, unmute BH, mute Poison
scene 3: play row 3 loops, unmute BH, unmute Poison, send CC changing pattern in sequencer
I can do all these things at the scene level, no prob. I just cannot cycle through the scenes using two controller buttons.
That's all quite simple until you involve the previous and next buttons. Each of the scene buttons can have multiple actions to play the loops and mute/unmute the AUs.
The previous and next buttons are a problem. You can trigger specific widgets from another widget, but not in a formulaic way like you would need to do there. The next button would need to be able to keep track of which widget it last triggered. That isn't possible at this stage.
There is a way to advance scenes with those previous and next buttons, but it's indirect, using Groups and Select Clip Below/Above. I posted a template somewhere up-thread to do this.
I'll see if I can find that one. It may be that when the scene is triggered it will also fire any actions attached to the scene button. Or maybe not.
Yup, I found your template above in the thread; it was very helpful. The challenge is exactly as you describe regarding the previous and next button. This is trivial if I introduce LK but I was kinda hoping to avoid that. Maybe necessary until LP matures a bit more.
Can you point me to my earlier post? I'm having trouble finding it.
nvm, I found the template and tried it. The additional actions on the scene buttons aren't triggered when the scene plays. So that's a no-go.
Just to be clear though: it's the previous/next buttons that trip this up. The answer to your previous question of "Can one widget trigger another" is YES. It's just that it's not a variable relationship where one widget needs to trigger other widgets depending on which widget it triggered last. TBH, I wouldn't expect a feature like that to be added any time soon.
If you just forget the previous and next buttons and just tap the scene buttons when you need them, it's a piece of cake to do everything else you want to do. It's the same number of presses and there's ample visual indication of where you are in the progression.
Yep, OK. If I only have two buttons and I have four scenes, I'm about halfway to my goal. BUT! I can use old tricks to make this work. I can add Mozaic as a helper to "add 1" to the last note in order to fire off multiple notes to trigger multiple scenes.