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 issue in Ripplemaker and BB17
I use 3rd party AUv3 synths in GarageBand on my iPhone 13 Pro Max , and all of a sudden some parameters are changing on their own. It JUST started a few days ago. In this example, on
Ripplemaker by @brambos the LFO rate drops back down; in BB17 the frequency fader goes all the way down.
https://youtube.com/shorts/uo_Lef4FW48?si=4P9G8dk07wQKU2aK
Any thoughts? I’m 99.9% certain the issue is GarageBand itself; I updated my IOS version and still have same issue
Comments
Do you have any MIDI controllers connected? Ripplemaker implements MIDI CC parameters (31 corresponds to LFO rate)
No midi controllers . Just use my phone and that’s it. This randomly just started happening and it’s affecting my workflow
It sounds like you may have recorded some MIDI CC automation along with the notes you're sending to Ripplemaker. You're looking for MIDI being input to the app, not AUv3 Parameter changes.
is this true even in a totally new project?
Yes…. In the short I posted above I started a new song from scratch and the problem happens immediately. > @uncledave said:
That’s not it… it happens when I first start a song ; even hitting play with absolutely nothing loaded causes the fader to go to 0. Happens with BB17 as well as Ripplemaker. I haven’t noticed it in any other app yet
I can confirm this happens with Ripplemaker in GarageBand. As soon as you hit play the LFO drops to zero from wherever you had it set.
Ripplemaker responds to CC 31 for the LFO speed. It's possible GarageBand is sending value zero for that CC on transport start. It's not possible to check with a midi monitor though since midi FX aren't supported in GarageBand.
( @brambos )
If BB7 has any kind of midi learn, maybe you could check if it uses the same CC for LFO speed. That would be a huge coincidence, which makes me think it may not be related to CC at all.
No midi learn, or if there is I can’t find it
And no manual.
If I had the app I'd try sending CC 31 to it in another host to see what happens.
Could be unrelated to CC's altogether though.
Honestly I don’t even know what that means 😔 lol
Doesn't matter. At the end of the day the only way it gets fixed is if one of the developers is willing to look into the issue. At least it's repeatable. I pinged Bram Bos a few posts up. You could also try contacting the BB17 developer if you know how.
Yeah unfortunately the BB developer doesn’t have a contact option 😞 I checked the site
https://docs.google.com/forms/d/1LAsWJaqwkUOW59MnrAf9b5ZmnaHILC1GGQRT1TZv-WI/viewform?edit_requested=true
Thank you …just filled it out
I messed with Ripplemaker in GarageBand. It’s the mod wheel in GarageBand that is overriding the LFO rate.
Nice find!! 🔥🔥🔥
Hmmm... ok. I could remove the MIDI input and make Ripplemaker AU Parameter-only (like my latest plugins). That may break some existing projects for some people out there, however, so I'm a bit hesitant.
It feels like a Garageband issue to me, to be honest. If you don't touch the mod wheel, it shouldn't be sending messages...
It's weird because mod wheel (cc 1) isn't even what you have set for LFO rate (cc 31).
I hope don't remove midi input. I prefer it to AUv3 setting up AU parameter mapping in every single project and/or host. Removing features because one DAW acts weird doesn't make sense to me.
IMO this should be reported to Apple as a bug, though that's probably a complete waste of time.
@brambos Hm this is super interesting... may this be somehow related to that old bug where in Nanostudio LFO value is always reset to zero when you save and reload project ?
To me looks like it may be. Maybe both these DAWs are doing somehing which forces Ripplemater to reset this particular parameter, just GB does it on play and NS only on project save.
I tested this in AUM. It looks like Mod Wheel (CC1) is permanently connected to LFO Rate in Ripplemaker. There appears to be no way to turn off this connection.
I suppose the Frequency control in BB17 is similarly connected to Mod Wheel.
It sounds like Garage Band is sending the current Mod Wheel position on Play. Not sure if this is right or wrong, since any controlled parameter will jump as soon as the wheel is moved.
Yeah the messed up part is the only way to contact Apple for this is apparently by phone…and I have no service (I use wifi as my data plan was sent to collections when I first got to rehab)
Ooo very cool … that explains EVERYTHING … also reason why on project load it is reseted to zero in NS - that is defsult modwheel position in AU instrument interface ..
@brambos i guess, this should be easy to fix in Ripplemaker just by adding switch in options to remove this connection.
Well no, because I don't have options or settings panels in my apps. That's a hard design principle.
The thing I’m not understanding is , why did it just start? GarageBand hasn’t had any updates in a while , and neither has Ripplemaker or BB
Are you saying you can remember a recent point in time where you used one of them that actually uses the LFO where that didn't happen. That seems unlikely to me, but maybe you have a really good memory. Would you even notice if the LFO speed went to zero if it wasn't patched into something?
Yes, because I use Ripplemaker quite often…it’s one of my favorite apps. And I’ve only had BB 17 for a month and used it a lot the past two band releases on Bandcamp. This is a recent issue within the last 2 weeks
What changed on your device in that time?
It's not limited to his device. It's a confirmed behavior.
It can only be a GarageBand change (sending mod wheel 0 on transport start), or a Ripplemaker and BB17 change to suddenly hard wire mod wheel to LFO rate. I think you see the unlikeliness of such a coincidence involving two plugins. GarageBand's last update was Sept 2023. So something simply doesn't add up here.
Yeah it’s confounding me greatly
Is it possible you just didn't apply a GarageBand update until recently?