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
@xglax @sinosoidal I’m sorry to report but midi mappings are lost again on AUM session load:
Strange. Just tested that and mappings were successfully loaded. Can you try making a new aum session with a simple LK patch and check if the problem persists please?
That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.
Sorry for the work
@xglax @sinosoidal Another request: I’m trying to sync properly LK and Koala midi loops. I use LK clip actions (playing actions midi notes sent to Koala loops, which are not synced to bars but immediate). It seems that slight midi delay make Koala not playing first loop midi notes. Could you add a +/- delay slider for each midi action (at least playing and stop modes). Like on this screenshot, this will make my life so much easier
The latest build have a problem with scene chaining.
When clicking on the the a scene, LK never trig the next one.
If I double click the first scene then it work and then other scene are chained correctly
Thanks for this complete analysis. CHORDER needs a overhaul for a LONG LONG time. We have it as an issue on our long todo list. Let's see if we can make it happen in this trimester. Thanks for your incredible and detailed analysis of the problems you are expericening with CHORDER.
Thanks for raising this up. We need to investigate.
Great! 🤟🙌🙌
I also had the question about the similar “note bar” on the side of the chorder module. How does that bar work?. Can you set a scale for it?.
Keep up the great work! 👏
On the CHORDER module, those "note bars" on the left/right represent the notes of the current selected chord, in different octaves, in ascending order. Everytime you press a new chord, the notes are updated.
Example. If you're playing a C Major chord, you'll have C1 E1 G1 C2 E2 G2 and so on.
Ohhhh. That was obvious, wasn’t it?. Not my brightest moment, I’m sure…
Thanks for your patience!.
The latest beta fixes this problem.
The problem with the midi assignments in AUM has been resolved in the latest beta.
Any feedback regarding these two fixes is much appreciated
I just tested latest beta of AUM and LK and had no troubles regarding the recall of the MIDI assignments.
That works properly now thanks!!
The problem I experience is not related to midi.
Here is what I’ve done that produce the problem.
First it only happen when Lk sync is set to host else it behave normally.
I touch the scene I have want to be played then I hit AUM play button.
The scene play but never trigger the next scene.
If I touch the scene button while AUM is already playing then it work.
Hope it’ll help.
Is the problem still happening with the latest beta released yesterday? Can you please confirm? Because we have acted upon your feedback.
Yes the problem is still present on the latest build released yesterday.
@Jeezs
Did this problem appear in these new betas (1.12.0) or was present before?
What is causing the issue is the following. Scene trigger actions are only applied when a scene is triggered when the song is playing. If the song is paused and you press play, even if a scene with follow action plays, it will not occur since the play state of the song will clear the follow action status.
The workflow you're reporting leads me to think that this is not a new issue. You're manually triggering a scene, but since the song is played afterwards, the follow action is not applied. If it was applied, when you press play, it would automatically triggered the follow action scene everytime instead of the scene you want to play.
It appears with 1.12.0, it always work before
Can you allow to select notes directly by single tap or drag over in that automation view? It’s necessary for now to toggle notes/automations views to do selections, it’s really not fast for change velocities for example. And because there is that message prompt to select notes, that is counterintuitive to have to toggle views just to be able to select something. Tools allow only to select all/deselect all.
Double tapping a keyboard key selects the notes in that pitch.
Such a great app… Looking forward to the update..
Thank You.. ❤️
Nice!! Isn’t it possible to implement simple taps to select directly on notes? Too difficult? Should be so simple and efficient. You don’t always want to change all velocities of a same pitched note (this almost never happens in real life except perhaps for drums).
I can confirm that this is a new issue. In previous versions, when I would select a scene and press play in AUM, the scene would be launched with follow actions applied. Now it only happens if I press a scene while it's already playing
You use Shift button to tap-select multiple notes (double tap Shift if you don´t want to hold it down while selecting). When selected, you can adjust velocities individually, or you can change all selected velocities by again holding Shift. Works very well, I´d say.
´
If I do that that will only duplicate selected notes. I don’t see how to do what I do in video in a alternative easier way:
Congrats on the new layout, buttons and specially on the automation improvements. It’s a lot clearer and easier to work with.
The problem should be fixed in build 278
I think a proper solution requires more time to mature. There are many edge cases that prevent us from implementing now a tap to select while in this mode. For now we simply updated the labels to instruct user that double tapping the piano roll key selects all the notes from that pitch
Thanks for your feedback!