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
Yup!
Thanks
I must be daft cause I can't figure out diddly from this video other than I am being encouraged to buy a blueboard. Where is the manual?
Yeah, that was a promo video.
Here are the MIDI controls:
There is no manual. You can find the info to set up MIDI in the App Store description, make sure to expose all of the app description and you'll see the controller info down toward the bottom. I would copy and paste but that doesn't work in the app description. Some of the MIDI info for pad setup is in the MIDI setup page of the app itself.
Thanks yowza....This helps;
--- MIDI CONTROLS ---
-- Notes Mode
Play / Stop - Midi Note G2 / Program Change 13
Midi CC 0: Rhythm
Midi CC 1: Jam Intensity
Midi CC 7: Master Volume
Midi CC 11: Swing
Midi CC 32: Bank
Midi CC 91: Reverb Gain
Select Soundset: Program Change (Notes Live Pad Mode)
--- Live Pad Midi Controls:
PC 0 to PC7 : Select Pad
PC8: Fill
PC12: Fill for the next Pad change
PC10: Fill for every Pad change
PC11: Fill & Start / End
PC13: Play
C3 to G3 : Select Pad
C2: Fill
D2: Fill for the next Pad change
E2: Fill for every Pad change
A2: Fill & Start / End.
Midi Note C2: Preview Song
Midi Note D2: Next Song
Double press to edit a part or song
Long press to move parts or songs
Does anyone know, in song mode, why is 1 bar actually 2 bars?
Mike here 👇
Well... it happen when the groove is 8 beats length. It started like this in the first version and we have not changed it so as not to spoil the saved songs.
Seems independent of groove length here and I would change it rather than have an error in the app. But if that's how it is at least I know why. Thanks.
did this fix the issue of not being able to trigger drums via midi? I still can’t get it to trigger when it’s in sound module mode. it’s almost like it doesn’t see any other midi sources beside network connection.
I’ve tried everything too but I don’t think it works. Anyone have success driving Luis’ apps as a sound module mode?
Do the other Lumbeat apps have this bar length error?
maybe i version 5.2?
The MIDI implementation in this and the other Lumbeats apps seems really clunky to me. Sometimes some things work. Just setting it up is really weird. I hope the developer fixes this stuff up. All I want to do is to be able to trigger fills with my foot controller and it is an exercise in futility.
No, you've made me doubt and I've been testing it. It only happens when the groove length is 8 beats, not with 4 beats grooves ( take a look to the video), depends how you think about it, it could be correct if you think 8 beats grooves as 8 / 4 measure. But if you prefer, we could change it to count them as standard 4 / 4
I´m testing it just now and works perfect
What foot controller are you using and what problem do you find ? Gonna try to solve these issues these days.
@LuisMartinez Can you please show us how to use Lumbeat apps as sound modules in AUM? No one can get this to work.
yes please 👍🏻
Thanks for your hard work Mr. LuisMartinez
OK I was having difficulties with the MIDI control and decided to Use a Korg nanoKontrol for testing instead of my Boss GT-1000 as a foot controller.
I used the MIDI note settings provided;
C3 to G3 : Select Pad
C2: Fill
D2: Fill for the next Pad change
E2: Fill for every Pad change
A2: Fill & Start / End.
Pad select worked fine but The fill pads did not work consistently. Then I noticed that if I pressed certain notes a red control notes overlay appeared.
I reprogrammed my Korg nanoKontrol and then pressed learn on the Rock Drums and success! Now all pads are working properly.
I am still in the process of testing ;
Play / Stop - Midi Note G2 / Program Change 13
Midi CC 0: Rhythm
Midi CC 1: Jam Intensity
Midi CC 7: Master Volume
Midi CC 11: Swing
Midi CC 32: Bank
Midi CC 91: Reverb Gain
Will report back.
OK So CC 0 Rhythm assigned to either a slider or a button crashes the app.
CC1 Jam intensity works fine.
CC11 Swing does not work at all.
CC 32 Bank works but can also cause crash.
I am testing as a plugin running inside of Quantiloop.
The Jam intensity works (vertical x y pad slider) but is there no control for the horizontal x y pad slider?
I also get the same results with Funk Drummer.
Thanks @BladeRunner
CC2 for Intensity ( y pad slider )
CC11 Swing works, but the slider doesn´t update. Fixing ...
@yowza Also fixing some Midi In issues ...
I just checked and it doubles the bars played regardless. Just tried 4 bars (plays 8) and 2 bars (plays 4). But that is only with factory rhythms. User rhythms work as expected. I would prefer it changed to 4/4 because it seems a needless problem when using both user and factory rhythms in song mode. Plus, and I could be wrong, but I imagine it is the behaviour most people would expect.
I suppose it could be correct just as if I said I am playing A Aeolian and proceeded to play C Ionian.
I guess if you think it could be an issue with other users then a poll might be in order. I'm selfishly thinking of new users like myself. This is my first Lumbeat drum app. To me though it's not even a decision whether to change it. To me it's an error because there is different behaviour depending on the rhythm I am using. Thanks for your reasonable consideration though. I appreciate that.