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
+1!
@josh83 and @SNystrom
Here are some of my workflow concepts, I’ve put lot of thought and work since two years in this approach (not only the taps configuration).
That MidiFire scene allows for 24 actions. There is a 60 ms timeout for single and hold taps, and 80 me timeout for double, single + hold, double + hold and triple taps. I will not go in deep explanation, but those timeouts work very well (too short timeouts = very fast foot taps needed = you will fail at doing some actions = unreliable live performance).
Single taps are the quicker and easier to execute actions while playing your instrument, so most important actions must be on those ones. On the opposite, the more complex foot movement is, the less /essential action you will associate with it.
And then there are 4 BlueBoard buttons, each one its domain: I use buttons A and B for GTL groups actions, C for looping/recording and D for effects triggering. That way my mind stay organized too, it’s like an actions/buttons map.
I use most of time 4 groups: Intro, Main 1, Main 2 and Outro. I use predefined instrumental loops (from my own prod) on slots 1,2,3, and slot 4 is for real-time sax looping.
My taps setup is like this:
A single tap : play/select Group Main 1
B single tap : play/select Group Main 2
A hold tap : play/select Intro
B hold tap : play/select Outro
A double tap : mute drum (loop slot 1) on selected group
B double tap : mute lead/keys/pads (loop slot 3) on selected group
Other A and B actions: allows to enable/disable effects in AUM on GTL output slot, or for custom GTL actions (for example un-mute drum, select group B, record slot 4 via a triple tap).
C single tap : record/overdub on selected group
C double tap : mute loop 4 on selected group
C hold tap : mute loops 1, 2, 3 aka solo loop 4 with CUEing
C single tap + hold : delete loop 4
C triple tap : undo loop 4
C double tap + hold : re-record loop 4
Single tap D : ascending round robin of F3, G3, A3 and B3 to trigger various effects preset
Double tap D : descending round robin of same notes sequence for same purpose.
Other D actions allows to individually enable/disable some effects.
The goal here of round robin is that with a single/double tap on a single button I can cycle some presets for my sax and focus on playing, not my foot.
You can use all of this to sync your presets triggering with GTL cueing, but that’s even MORE complicated. You will need something like Atom sequencer (for syncing presets triggering), midi learn Atom play/stop via AUM, note to CC conversion in MidiFire, and then midi control in AUM. But that’s doable.
That’s pretty cool, even if I prefer pure improvisation freedom as a general approach for most of my songs. There is something I love in all that instrument + foot playing, this puts me in trance by the mental effort it takes at first, and then with automatisms you will focus only on music again and this is pure magic juggling!!!
Wow, thanks so much for going into such great detail with your settings and board letter assignment philosophy. It sounds very efficient and hopefully will save anyone who reads this at least two years of experiments!
That’s not true, as my setup will not be fully transposable. Each individual will have to find how he/she wants to approach advanced live looping. This is also where BTW MidiFire is useful, because it’s modular and adaptable to anyone needs. What takes most of this work is this: how you will play your music with all that tools, how will you build your own setup, how do you want to achieve your musical goal? Scripting, routings, all this need to be learned and mastered, and for the most part that kind of live looping will take dozens if not (mostly) hundreds of hours of practice to achieve ease of playing and above all great musicality!! Your setup is there to achieve that: your music!!!
BTW MidiFire is also on MacStore, and you can share scenes back and forth between it and iOS version. I use it with Live, works really well too.
Some food for thought and take inspiration from:
@Janosax Thank you so much for explaining all the details of your BlueBoard/GTL setup!
So I played around a bit with StreamByter and Blue Velvet. I've come so far: I started my BlueBoard in MIDI mode 1 (by holding B when turning it on), then connected to it using the iOS Bluetooth preferences. Then I started AUM, added a MIDI channel, and loaded StreamByter as "Audio Unit MIDI processor". I then open StreamByter, select preset "Blue Velvet", press "Load" and then "Install Rules". Then I choose "iRig BlueBoard Bluetooth" as MIDI source. Now by activating the In/Out window (magnifier symbol), I can see what comes in and goes out. But how can I assign the signals that "go out" to GTL? In GTL, when selecting "iRig BlueBoard Bluetooth" as "MIDI Input Port", I only get the "clean" signals, not the ones from Blue Velvet. So how can I send those to GTL?
Another topic: During the last days, I read the manual for Mozaic (http://ruismaker.com/wp-content/uploads/Mozaic.pdf), and it looks pretty cool (and much easier than the programming language used in Midifire/StreamByter)! I feel intrigued by the idea of creating advanced combinations of tapping and holding, e.g. press and hold A, then single tap B, then release A => trigger some GTL action. Did you ever experiment with something like this? In my opinion, being able to create such sequences by stepping on and off buttons "in the rhythm" of a song is easier, than creating "off rhythm" tapping-combinations like Blue Velvet's. So for example when recording a 4 bar loop in 4/4 rhythm, I potentially have 4x4=16 times the chance to tap (and potentially hold) a button with a key. One could create pretty sophisticated combinations with that. Do you think this could be useful?
@josh83
I don’t use Streambyter AUV3 here but MidiFire. In your case you will have to use two instances with this routing:
In first Streambyter you will have Blue Velvet, and in second one you will copy paste this code (which interprets Blue Velvet instructions resulting in outing midi messages):
A=C3/3C, B=D3/3E, C=E3/40, D=F3/41
single taps (CH3)
N2 3C = X0 3C
N2 3E = X0 3E
N2 40 = X0 40
N2 41 = X0 41
double taps (CH5)
N4 3C = X0 48
N4 3E = X0 4A
N4 40 = X0 4C
N4 41 = X0 4D
triple taps (CH7)
N6 3C = X0 54
N6 3E = X0 56
N6 40 = X0 58
N6 41 = X0 59
hold (CH2)
N1 3C = X0 60
N1 3E = X0 62
N1 40 = X0 64
N1 41 = X0 65
single taps+hold (CH4)
N3 3C = X0 6C
N3 3E = X0 6E
N3 40 = X0 70
N3 41 = XX 71
double taps+hold (CH6)
N5 3C = X0 78
N5 3E = X0 7A
N5 40 = X0 7C
N5 41 = X0 7D
Then just midi learn actions in GTL :-)
I’m not sure to fully understand what you want to achieve, and unfortunately (or I could say this is also where is the fun in fact!) you will have to find your own path more or less alone as it’s really difficult and lot of work to achieve those kind of setups. You will have to understand and master midi routings and global logic, and basic scripting.
If you want to sync some of your midi actions with the bars, you can use GTL CUEing or you will have to use a midi sequencer (lot of work to know how to work with the second one). You can also for sure use some scripting to allow note on for some actions and note off for others. You can also use a pedalboard with more buttons, as 4 buttons lead to some latency when you want them to being able to respond to multiple taps.
This is also why I said it’s so personal, what works for me will not work for others, it’s all about what you want to achieve, and with what kind of approach you feel comfortable with to make your music. My philosophy is to improvise sax looping with a compact BT pedalboard for mobility, using mostly CUEing for sync. But I have also MIDIFIRE scenes where I use single taps only with some buttons for instant recording. It all depend on the song.
Here is how you can use for example GTL custom actions. Imagine you’re on theme A, drum is muted, and you want to switch to THEME B with unmuted drum and loop 4 starting recording, all with a single action (all actions will be triggered at the same time, in sync with group/loop CUEing:
Select group
Play group
Record loop 4
Unmute drum
Hope this helps
@Janosax Loads of inspirations there! I see the simplicity and power of GTL (and instantly saw it when first used the app, which triggered an immense wish to be creative with it), it's just great to have this little "savant" in my pocket all the time.
The reason why I think that "tap + holding" sequences of different buttons is maybe more promising than Blue Velvet's approach, is exactly the timing thing: Blue Velvet always needs to check whether there is something more coming after a tap, thus delaying the triggered action for some milliseconds. When "tap + holding", I can control exactly when I release the last key, and my script knows immediately when to trigger the action.
I will report back as soon as I made my first experiences.
I’m really interested to known how it will work for you!! And that can be a good approach even for me, and I will be curious to try it
Always happy to share knowledge and experiences.
Have a look to THE [C] CONFIG (coming soon ! I will share the whole setup)
––––––––––––––––––––––––––––––––––––––––––
THE [C] CONFIG
UNLEASH THE POTENTIAL OF THE iRig BLUEBOARD
(for Bias FX 1 or 2 mobile and many other apps)
Features
24 actions
iRig BLUEBOARD mode
Apps required
App not to be used anymore
The BlueBoard app that requires to choose between PROG or CTRL CHANGE.
You can now do everything simultaneously!
Limitations
––––––––––––––––––––––––––––––––––––––––––