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
In my very humble opinion the filter should be controlled by Y-Axis instead of the current X-Axis.
What's the logic between sliding left to close the filter and sliding right to open it?!
Up/Down would make so much more sense no?
And is it just me but it's practically impossible to latch the same note on multiple octaves?!
So if for example F is latched on octave 2 I can not latch the F note on octave 1 and octave 3 as the note remains 'lit'?!
The latched keys don't 'scroll' when changing the octaves to indicate which octave they were latched on.
Cheers!
Yes, that's the consequence of wanting to keep all active notes (across all octaves) visible at all times. It's a tradeoff, but one I very consciously made to make the fader-control paradigm possible.
It's easy to just load up KB-1 and control Salome in a more conventional way if that's what's needed.
congrats man, love the hilda filters!
maybe bring a advanced filter au as a separate app?
Y axis controlling filter cutoff is a very common mpe assignment, many people would appreciate an option to assign it that way, I reckon. You can modulate the lfo rate with y axis currently, but that's different from being able to directly modulate the filter cutoff, yes
The main reason is that I figured it made most sense to control volume/pressure independently from filter cutoff. If you put filter cutoff on the y-axis, it would always interfere with volume so I opted for the horizontal mapping.
Got it,
A combined volume and filter-sweep on the y-axis could be quite practical in some cases?
I find it very hard to 'perform' a filter-sweep on the x-axis especially if I already have pitch-bend assigned to the x-axis.
Pan makes perfect sense on the x-axis
I know what you mean, yes, normally people would use pressure for that on physical MPE controllers but that's not an option on ipad
@brambos does salome support sample streaming from disc (i.e. can load and handle really big .wav files) or is it a purely ram based sampler (better for shorter .wavs)? did a search but nothing popped up
From memory only (90 seconds @ 48KHz, or the equivalent size in other sample rates).
awesome good to note, ty for the reply!
does using mono double the time?
No, for optimisation reasons it will always be stereo internally. The app wasn't meant for long recordings, so that wasn't a priority in the way the architecture was set up.
i hear you..
so then if we really want to use it as an “audio faderboard” as mentioned in the blurb , we need to use seperate au instances ... which means it would be perfect to have ( as someone suggested previously ) some way to make the ui window only show 3 or 4 of the faders so we could set up ... say 4 instances each in a 1/4 of the screen real estate each .. to fade in & out
or maybe this is already possible?
i don’t have this yet as i can’t figure out a way to access multiple sources/loops on one screen easily , though the talk of different loop points for different notes/faders is encouraging , the ram limit you have means only perhaps about 4 differing loops of 22 seconds from a specifically constructed audio file could be played “freestyle” at the moment ( as far as i understand the limitations )
Hmm, I still don’t get the octave up/down thing….
If I want to play a sample at C1 and C2 simultaneously, for example, then do I have to open another instance of the app?
Yes, I think I would prefer it if it acted differently but several instances is the workaround
I think this must be a 'bug' since the latched notes don't 'move' when switching the octaves up/down which they should in order correctly indicate which notes are latched.
No it’s not a bug. Active notes stay visible at all times. That was how it is designed.
That means only one C can be playing, but it will remain always in view, to allow the “Faderboard” control method.
Bummer, it's sometimes handy do drone a 'sub octave'
Ok, thanks @Gavinski @brambos and @Samu
I’ll do the multiple instances workaround
For the DIY type, you can convert Y Axis to a CC with a StreamByter one-liner:
DX = BF 4A X2 +C
DX detects Channel Pressure codes
BF substitutes CC codes on channel 16 = F (actually it’s 15 but MIDI makes channel 1 ‘0’)
4A is decimal 74 in Hexadecimal. Change this to the CC number of your preference
X2 copies the original Channel Pressure value over into the CC value. I had to Google for this solution.
+C is optional to add this new command into the input stream or you can just send these CC’s out from StreamByter for AU automation purposes and MIDI learn ease.
The Original Streambyter One Liner when the previous rev defaulted to CC74’s on each MIDI channel was:
BX = BF +C
Hi @Stuntman_mike !!
How can I connect my external Bluetooth or USB keyboard on Standalone Mode I can’t find the MIDI Input Menu on the App
Thank You
.
You need to load it as a plugin. The standalone doesn’t have connectivity
One option is to switch up or down an octave, then use the note next to the one that’s being latched and use the per-note pitch bend to add the octave note.
Thank You @brambos
!!!
I remember someone brought up drag and drop, Bram. Any chance of that? It is useful to use an app like samplecrate to demo samples, as the Apple Files app doesn't allow us to do that, then drag directly onto the Auv3 you want to load them in. AAASamplePlayer and Sitala spring to mind as apps that can do this, I have no idea how hard it is to implement.
In this new version I am having trouble with the sample start / end points. If I adjust them in Salome loaded in AUM, the sample window in Salome keeps freezing on me, I can no longer adjust the start and end points, and I need to quit it and load it again. But then, after some seconds of fiddling around with start and end points, the same thing starts happening again. The sample I am working with is short, about 1 or 2 seconds long, the session is tiny, dsp load insignificant.
Edit: device restart seems to have fixed it
Yes, I am already working on drag/drop, but iOS won’t let me use iCloud files which are not downloaded yet (with the little cloud icon). Is that normal with other apps too? (I never use drag drop because it’s so clunky)
So I can’t say for certain but I wanna say when you click on the sample that’s in the cloud it automatically downloads and then can be uploaded into the app. That’s how it’s always been for me anyway. Unless I’m misunderstanding what you mean.