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
The advantage of the script is it can transparently restore the controller to where it needs to be automatically on AUM session load. When you change sessions your controller will be all out of whack and you'll get jumps when you change anything. You can ignore the snapshots feature or use the second linked script which is the same but without the added snapshots feature.
However, I really don't know if it'll work with the EC4. It depends on whether or not the EC4 accepts simple feedback to update its encoders status. I would be interested to know if it works should you decide to try it out.
That was my point too.
Obscured in too many words as I always do. 😂
I think having simple feedback as an option (defaulted to off) is preferable, but that's just my personal opinion.
Wouldn’t the midi learn button, at the top left of every window, be an easy way to switch any connection quickly.
If your question is directed to me: i‘m using the midi learn function on every single knob/button connection i create. But that‘s not the point. You turn your cutoff knob fully open, then switch to another synth preset with completely closed filter. You touch the knob again, cutoff value jumps immediately to the knob position, from 0 to 127 in a milisecond. It‘s absolutely not a problem in desktop world, even most hardware synths offer different options to avoid this. Just turn the knob and it will slowly increase the value from where it actually is in the synth. Not a big deal i thought. How wrong i was…
This is even the reason why they invented endless rotary dials and why most midi controller have this encoder. But if the software does not support it…
I wonder if IOS music production will ever reach a halfway matured status 🫠
That's not my impression. I don't have any data to back it up, but it seems to me like most controllers use pots. Certainly any faders are pots/absolute. Even many controllers with encoders default to absolute values. The ones with encoders tend to be (but aren't always) more expensive than others.
Pickup or takeover mode should be a default function part of any midi controlled app though. I can't think of any case other than for relative encoders where it makes any sense at all not to have it.
[edit] wait ... yes there is a case: buttons that are intended to send values other than 0 and 127. Pickup mode could never work for buttons. So, you'd end up needing to defeat takeover mode on a per control basis. The devil is always in the details.
I just remembered that the basis of this group, Audiobus, has always supported pickup mode for AUv3 parameters controlled by MIDI. So, a host that supports pickup mode for controllers is readily available. It does seem unfortunate that AUM hasn't incorporated this yet.
yeah, you are right of course. I left faders out of my math by intention 😉How about motorfader though?
I also can‘t backup my statement regarding“most“ controllers. I thought about it and from all the cobtroller that popped up in my mind, most were with endless dials. Thats not a very scientific approach 😂 Just a lil drama out of frustration. I do love pots (much)more than encoder, especially on synths. But i don‘t like puckup mode at all, takeover on a pot is“okay“ though. On a midi controller i prefer encoder, it just makes way more sense if you want to use it on a lot of different things.
I prefer relative encoders too, but finding support for them is rough on iOS. Fortunately my main two apps, Loopy Pro and Drambo are good on that score.
@Crabman : i don’t think it is the case that most midi controllers feature endless encoders. A lot of controllers have knobs that are not endless encoders unfortunately.
I love AUM so much but i have drambo as well. Maybe i should try my idea there. But i‘m a drambo noob and find it not very intuitive in some cases. I had a quick look but i have actually no idea how set it up as a „dual hardware fx box with 2x4 AU slots“ 😂 This needs a deeper investigation it seems
To me Loopy Pro is more analogous to AUM than Drambo is as a replacement host / mixer / midi router. Not that Drambo can't do it, but the concepts are closer in Loopy.
I don‘t want to spend 30€ now just for a 2 channel mixer.I have no use for loopy, as good as it might be.
I'm thinking pickup-mode should be implemented by the controller, since it's the controller that switches between its pages? If implemented by the receiving side, how does it know that you don't actually want to jump to a specific value?
sorry i meant takeover. Pickup mode is good for pots but makes not much sense on an endless dial
Pick-up mode would be an option in the host for absolute controllers. It is VERY useful as an awful lot of controllers are dumb and are send-only. It is a useful option for use-cases where controller knobs or faders are dumb and user doesn’t want jumpy values.
What? Oh no, we are doomed.
Sorry, but how should the controller manage pick up when it doesn't get Feedback from the Software via MIDI?
Pickup works only on the software side and was especially for potentiometers that always send their actual position on change.
Only the Software e.g. AUM knows the value of the MIDI learned parameter and ...
Damn, i should start with Swift and build an Audio Unit Host and MIDI routing software myself to get whats needed.
See ya in 1-2 years ...
FYI, loopy pro has pick-up and also supports relative MIDI.
...
And sends MIDI feedback, I know.
Loopy is amazing. 🥲
But, for now, AUM is way faster in connecting devices via midi routing matrix and has more effective midi learn via knob change.
No. Even if the controller is not switching between pages (many keyboard controllers have no "pages"), the user will restore a host preset, or start from cold. So the hardware controls (pots) are completely misaligned relative to the mapped AUv3 parameters.. The user would like to be able to turn a mapped knob and not have the parameter jump to the random knob position. It's difficult to imagine a situation where this jump would be desired or intended. AUM is the only component that can implement this, because it knows the current value of the AUv3 parameter, and it knows the details of the mapped control (probably a CC), including scaling, so it can block adjustment until the control value matches the parameter. This needs to be implemented for the AUM parameters, like the volume sliders, as well. And, just for argument's sake, Audiobus has supported pickup mode as long as it has included MIDI mapping.
Incidentally, the trick is not to wait until the control value exactly matches the parameter value, since that may never happen. You need to detect whether the mapped value is high or low, and begin tracking when the value crosses the app value.
Thanks for the clarification! You're absolutely right.
However there are situations where you don't want it, for example when controlling a parameter from a sequencer. So I believe it must be an option. Maybe per MIDI control source? So that a user can decide that this controller should be pick-up mode, but this sequencer plugin should not.
But the tracking must be done per MIDI control destination parameter, since one MIDI cc could be mapped to multiple destination params. So logically it would make more sense to enable/disable pickup mode per each destination parameter.
I think we have been trying to express the the idea that it is a per-parameter option that a user switches on per-parameter when setting up midi learning or setting up a parameter not a global or always on option.
Exactly. Here's the MIDI learn menu from Audiobus. You select the parameter from a list, and optionally enable Pick-Up mode.
Wow I did not know Audiobus could so easily do that. And so I’m assuming Loopy can do it as well, since @Michael has said Loopy has advanced AB in features?
Yes, Loopy Pro has it per parameter as well.
And handles relative midi
Ok, good! Makes sense.
I‘m testing the Loopy Demo right now and…shit…looks like i need to buy it only for this (more or less) single purpose to use it as a mixer 🫣😳 It does exactly what i want. One thing though: i couldn’t figure out yet how i need to setup loopy to change fx presets via push button. Not a big deal though, using a knob is good enough to me.
What I do is set up a stepped dial, set the press action to Trigger Widget. Select the dial itself . Set the action to scroll. Choose nudge. Optionally turn on wraparound. Now, tapping the dial, advances the dial.
Thanks a lot, i will give it a try 👍
No idea what went wrong last time but i had no problems now to set it up (even not following your instructions). It´s mindblowing how good the midi implementation of Loopy is. And in an almost forgotten „it just works“ apple manner from better days. Íˋm able to completely remote control everything i was hoping for from the Faderfox now. No value jumps, always the correct values disaplayed, switching plugin preset with button push etc. I just start loopy and can hide the idevice for the rest of the session ❤️
Thanks for this awesome work @Michael no regrets to buy it just for the mixer and midi control alone 😀 👍 But with the release of midi clips i’m sure i‘ll find more uses for it.