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.
Gauss - How to erase a loop via MIDI CC?
Hi all.
First time poster, long time lurker.
I entered the world of iOS music making about a year and a half ago without much music making experience. Over that time, I’ve learned so much from all the wonderful musicians, devs, dabblers, educators and creators who contribute an endless stream of valuable content to this forum, and elsewhere in the digital sphere. I am sincerely grateful that I have access to such a diverse, knowledgeable, supportive and accepting iOS music community. I’m guessing, like many of you, I visit this forum multiple times a day. For me, it is a source of new ideas, news, and exposure to a vast trove of musical treasures.
This week, I began building a 4 instance @brambos ‘s Gauss (3 second) phrase looper (with overdubbing) in AUM. I used Fugue Machine to send infrequent notes using slow BPM to a single instance of Lo-Fi Piano. I then bussed Lo-Fi Piano audio to 4 effected Gauss looper channels, which are sent to the master bus alongside lightly effected field recordings and heavily effected fractal bits.
I used midiLFOs to send CC values that occasionally modify Gauss’s TAPESPEED, VOLUME, and toggle RECORD TRIGGER (in each instance’s MIDI Controls). As I’d wanted to clear each instance of Gauss’s loop (independently) every so often, I attempted to trigger each Gauss instance’s ERASE TRIGGER by sending a CC value of 127 at varying intervals. This did not work. I believe it may have to do with Gauss requiring a “double-tap to clear the loop” but when I sent 2 CC values of 127 in quick succession to ERASE TRIGGER, this does not work either.
Does anybody know how to trigger Gauss’s ERASE TRIGGER via MIDI CC? I attempted to use zelikovich‘s / @slicetwo ’s awesome https://patchstorage.com/gauss-8-track/ and then built my own simplified Mozaic UI with only the ERASE TRIGGER functionality brought over from Gauss-8-Track script, but neither worked.
My work around was to send Gauss’s LOOP DECAY CC value of 127 for a few seconds, every so often, so that each loop is effectively cleared while the state is 100% loop decay. After this, I reset loop decay to 0% by sending LOOP DECAY a CC value of 0. The goal is to have a template for a multichannel micro/phrase looper on which I can build effect chains (as can be seen in the attached screenshot of part of my AUM project). My workaround is fine but I was hoping somebody on the forum would know how to delete a Gauss loop by MIDI CC properly. Hopefully, one of you can help me crack this puzzle.
Below is a sample from my experiment:
https://on.soundcloud.com/uMxmvzXboeW18VK18
Thank you for your assistance!
Josh
Comments
Hiya Josh - welcome out of the shadows!
I'm not having any trouble at all using
erase trigger
AU parameter. I tried first by sending a note thinking that might be the problem. Then I switched to CC 20 and that worked fine too.I'm not sure where to go from here.
Thank you, @wim ! I appreciate both the welcome and the lightning fast test and response.
The issue must be user error on my part. I just loaded up zelikovich‘s / @slicetwo ’s https://patchstorage.com/gauss-8-track/ AUM project (in full, rather than trying to pull out what I thought were the relevant Mozaic bits). I can confirm that the erase trigger functionality works, as expected, within @slicetwo‘s tool. That gives me hope that I can find a fix on my end, too!
Thanks again!