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.
Ripplemaker and AB3 midi sending
Anyone else having trouble using Ripplemaker as a MIDI sender in AB3 unless you already have the app open? It's missing from the list of options when I open the AB3 MIDI sender dialog. If I launch Ripplemaker separately it suddenly appears in the same dialogue. Interestingly, Troublemaker does show in the list of options no matter if I have the app open previously or not.
Comments
Yep I'm getting the same behavior here.
@brambos . Yes, I have Troublemaker showing up, but Ripplemaker is missing in AB3 MIDI since the update
I see Ripplemaker in the AB3 MIDI senders as well as my other 'makers, Phasemaker and Troublemaker.
...and I don't have any of them open first.
Its not really a ripple-maker specific bug. it happens when you have too many apps. Ab3 tends to randomly not list some of the apps as a result. used to happen with AB2 and AUM as well. the fix is to just open the app first. I've actually had Moog's Model 15 not list a few times..... I own too many apps DX
Only explanation I have is that the AB3 app database needs to update. This happens in the background while AB3 is open long enough.
I had this problem too, before the update. I also still have it now. Reported it through the AB3 beta a week ago. I was told to delete then reinstall the beta, but that did not rectify the situation.
I sometimes have to leave AB3's app load window open for ~10 minutes (while the 'loading' spinner is visible at the top) before it completes updating its database. Audiobus only shows apps which it 'knows' about, so until it has refreshed the database it simply doesn't know Ripplemaker exists as a MIDI sender.
Troublemaker is always visible, because that one was already released when Audiobus' default database was shipped with the installer.