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
that is right, I had to change the manufacturer id for the mac version to add capital letters,, it was for passing validation tests. I fear though if I were to change it back and release that version that it would be the same issue. If you can send me your set I could possibly export what you had in a preset and send it back.
In my case it’s not really worth it, I’ve only used the app in a few test projects. Thank you for the offer, though.
This is exactly what happened with Rymdigare, Erik Sigth had to change the manufacturer ID for the same reason. He included a legacy version with the original ID so people’s existing projects weren’t broken. I could understand you not wanting to do that with a newly released app, though.
Same for me. Have you tried starting the standalone app? It crashes for me and can no longer be opened. Uninstalling the app, reinstalling it and restarting the iPad didn't help either...
Hmm I could add that if I hear more of the same issue. I will also gladly transfer project by saving a preset with it and loading that into the newer version.
I will go ahead and add a version, with init ID in the description.
ok I built a new version with an additional entry for each called (Init ID) and tested with older sessions and works.
This will be 1.0.3
1.0.3 was approved and should be in the appstore soon.
Thanks for the quick troubleshooting, GlitchStep works for me again and loads in AUM 👍
Works for me now...great job!
Glad to hear it!
Thank you, that’s fantastic.
You're welcome!
Bought... Pretty nice... These are the apps that makes iOs music creation special...
Modulation?
Thank you..
You are very welcome, thank you for the kinds words.
Are you asking if you can modulate the controls? You can modulate everything with AU Parameters.
Alex
just got this and its wild for sure!
it would be kool if we could change the length of the looping cycle or have a way to trigger it from the beginning. Im trying to use it live and play a part, loop it for a few seconds, then keep playing , the loop another part. almost like a sustainer
To control stuff like ‘Cutoffs, Reso, etc.’ on Synts, Instruments.. unless I missed it..
Check https://matheusound.net/glitchstep for a user guide, you can change start and end, and also cycle in reverse. There are tutorial videos there as well
No there is no cc control in the sequencer it is for note control only. It is meant to be used with modular environments like aum where you can use lfos to drive cc exclusively
Is it just me, or are the Minor Pentatonic scales in GlitchStep a little off?
My bad I was using GlitchCore
This was my reference
https://www.pianoscales.org/pentatonic.html
I took the semi-notes from that page and are
Semi-notes: 3 - 2 - 2 - 3 - 2
or in my code
{3, 2, 2, 3, 2}, // Pent Minor
Entirely possible that it’s error on my part, but when I set GlitchStep for C Penta Minor, for example, I had expected the note choices to be limited to C, D#, F, G, and A#. Instead, I’m allowed C, D, D#, F, G, G#, and B. If I randomize notes, notes are drawn from the second set of seven notes, instead of the first set of five.
Loving the app, BTW. Rare that an app with this power is so transparent and easy to learn!
This is the correct interval order for a minor pentatonic, counting from the tonic (bottom) to the tonic an octave above (A-C-D-E-G-A', for example). 👍 I haven't tried GlitchStep yet, though, so no idea how it actually behaves.
Thank you I will check that and confirm.
Hmm you are right, I must have a bug on specifically pent minor quantization. I will make sure to get this fixed in the next update.
The new note selection method is showing the correct notes, but not random or dragging the knob
Love the app, I believe it's the first time that a sequencer clicks with me.
I noticed that the harmonic minor scale was wrong, so I went through a couple of the minor scales.
It ended up taking way longer than I thought it would, and after writing down all the intervalls for the scales with issues that I noticed, I realized that some of the scales are simply flipped around:
Pentatonic minor in Glitchstep is the harmonic minor scale
Melodic minor in Glitchstep is the pentatonic minor scale
Hamonic minor in Glitchstep is the melodic minor scale
Or with all the intervalls written down:
For pentatonic minor Glitchstep has harmonic minor scale with the intervals
2, 1, 2, 2, 1, 3, 1
when, as you wrote, it should be
3, 2, 2, 3, 2
For melodic minor Glitchstep has the pentatonic minor scale with the intervals
3, 2, 2, 3, 2
when it should be
2, 1, 2, 2, 2, 2, 1
For hamonic minor Glitchstep has the melodic minor intervals
2, 1, 2, 2, 2, 2, 1
when it should be
2, 1, 2, 2, 1, 3, 1
I also noticed that when assigning a midi controll to one of the knobs, the scale and interval settings are ignored, and you simply scroll from C-1 to G9, is that intentional?
Otherwise great work with the app, I'm realy enjoying it.
Great diagnostic work!
Oh that make my work on that so much easier . Thank you so much!
I am also looking into the AU Param scale change
Thanks again for that, I found where the issue was, it was in the UI, for the scale picker, its underlying data pointer was pointing to the wrong data, I had shifted those around but missed a spot to change the ordering. I was able to fix that really quickly with your diagnostics.
Alex
This was not intentional and I am looking into this next.