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.
Weird Trooper glitch
So I’m using Trooper as an AU in GarageBand on my phone, and periodically the sound will change on its own to a different preset, usually whatever the second preset is in the bank I’m on. Once this happens , it is stuck like that the rest of the song; no matter what I choose, when I play back it ends up reverting back to that sound.
Any ideas?
Comments
Could Trooper be receiving a MIDI Program Change message from somewhere? Is there something in GarageBand that might do this? The "second" preset in the bank would correspond to a PC message with the value one (PC messages count from zero).
Yeah something’s not right. It reverts right when I hit play. It doesn’t matter which bank I’m in either
Looks like it’s not just reverting to the one on the second bank…it’s seemingly random, but once it switches , it gets stuck on that one. I did a screen recording of it (it’s unlisted ; I only did this to demonstrate what happens)
I would ask for a refund but it’s getting close to a month and I don’t know when the cutoff is; plus I bought IAPs for it. Haven’t heard back from developer yet.
This sucks as my funds are limited and I feel like I wasted my money as I can’t use it
Edit. I went ahead and requested a refund as deleting/reinstalling didn’t work. I feel really bad about this as what initially convinced me to buy it (I was deciding between this, Nambu , and Poison 202, and I ended up getting the latter anyway shortly after) was the interview Jakob Haq did with the developer, who seemed like a really cool guy. I had problems shortly after buying it but I thought it was just a glitch. As it is , I read that it’s a 14 day return policy and I’m on day 18; I’m probably going to be denied anyway but I had to at least try just in case the problem isn’t fixable.
Regardless I still feel bad 😞
In the Trooper MIDI settings, there's one called "Prog Channel", defaulting to OMNI. Try changing it to OFF. That might block unwanted Program Change messages.
I don’t see anything like that in AU mode. I see it in standalone but that’s not how I’m using it
In standalone, it was already off .
Are you using pre-made MIDI files in Garageband?
Ones either I’ve made or one my collaborator makes. It doesn’t happen with anything else I use (poison, Ripplemaker, OB-Xd, ect)
You could load a MIDI monitor AUv3 instead of Trooper to see if there's any PC message sent on that track.
I don’t know what that is or what that means 😞 is that something I have to buy?
StreamByter is a free AUv3 app that includes a MIDI monitor. Connect it to the MIDI stream and it will list the messages; use the magnifier icon. May be a little hard to spot a Program Change among the notes.
The reason changing patches doesn't happen with other apps may be because they don't support program change messages. It's very common on hardware synths, but patchy on software apps.
I just downloaded it, opened it up in GarageBand, and when I tried to figure out what it wants me to do, it just went over my head completely. I don’t really understand this stuff…I just play notes and turn knobs until it sounds good. Even if I could understand the html and gobbledygook, I wouldn’t have the foggiest idea of what to do to fix it . I can patch the ever living hell out of a west coast synth but hell if I know computer speak 🤣
Just use the magnifier and send the MIDI stream to it. You don't need to do anything.
We suspect that your MIDI has program change messages used to switch patches when the MIDI was recorded. They are affecting Trooper, which makes them seem random.
I’m not understanding what you mean by “sending the midi stream” to it. I’m using my iPhone. If this is a Mac thing then that would explain why I’m not seeing how to do it. Do you mean for me to put the affected midi file on the track where StreamByter is located?
Even weirder….I loaded up the exact same file and it’s not doing it currently . It’s been intermittent but if it was something to do with whatever MIDI gremlin is there, wouldn’t it happen every time?
@Fear2Stop Your Streambyter setup looks good.
Maybe try a few restarts of your project playback from the beginning until the problem might show again? I'd also save that project, restart Garageband and try again...
@ All: Does anyone know how to show program change messages in Garageband's MIDI tracks?
Thanks for the help…I apologize for not quite getting it at first . My first language is music. Not being facetious or pretentious in the least…it’s the only thing that comes easy to me. Technical stuff? Not so much!
I think there’s definitely some kind of compatibility issue, in that it did something similar yet different just now, in that the volume adjusted on its own like I was using automation. Only problem is.,:I wasn’t using midi…I played & recorded a part live to the metronome and it was doing it during playback. Plus, I don’t use GarageBand’s automation at all …like, ever.
So yeah there’s something glitchy with how they’re talking to each other. The million dollar question is, how to fix it