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.
TouchOSC alternative in AUv3.
Hello! I need to control external gear (DIY firmware on eurorack module Daisy Patch) by custom touch midi controller and i use TouchOSC for it. But when i use it with AUM, i must switch the apps (AUM <> TouchOSC) and It creates sudden DSP overloads in AUM. If there was an app that would work as a MIDI AUv3 plugin, where i can create my own midi controller with the arrangement of knobs, sliders etc i need. Now i port my touchOSC project to Drambo, But it's still not as convenient as TouchOSC.
I test a GSDSP MMM, but here is limited number of controllers. May be someone know an app that could help me?
Comments
Had to move touchosc to another device for the same reason but I only needed to guide the controls by a mouse which is I guess is not what you're aiming at. There is a CC send module in auv3 version of Audulus to which you can connect knobs, sliders, x/y etc. The downside of it that there is no midi assignment to anything but you could still control those physically. MiRack could also work and has more midi connectivity.
I do think theres a gap in the market for this.
Nurack by 4pockets has some midi controllers, not customisable to the degree touch osc is. I just tried to have a look but its failing to load, dunno if its my iPad or the app needs an update.
KB-1 by Kai Aras will give you xy pads or a good number of knobs quick and easy. Might be a nice thing to get you by.
Fwiw, Audulus does have midi assignment but you have to assign manually rather than midi learn...and it looks like its sliders and knobs don't visually update to reflect received values even though they are passed on.
I was try to use Audulus 4 plug-in for it….but when I create a midi cc, it crash. And it don’t have channel change.
I don't know if your ipad model and OS can use Stage Manager, but I wonder if you have both Touch OSC and AUM open in Stage Manager whether you would still get the dsp spikes? Might be worth a try.
If MIDI level granularity is acceptable, Loopy Pro can send midi from its sliders, knobs, buttons, etc.
As for cpu spikes, even with AUv3, opening their windows will often cause cpu spikes due to the way the os re-does throttling and core assignment based on computational demands.
As I know, my iPad 9th gen don’t support stage manager and I must switch between apps.
@temaniak : one thing that Loopy Pro as a host offers is that you can add sliders, knobs, buttons etc to send midi directly on loopy's work surface.
How about the Controller IAP in LK?
Very few controls. This is my control on TouchOSC. I need something like this)
You could do that in Loopy Pro as long as there isn't any scripting behind those controls or anything.
I was going to suggest using TouchOSC in slide-over mode with AUM. That doesn't require stage manager and should get rid of the CPU spikes. But, based on the screenshot, slide-over mode won't give you enough control space.
Midi Designer Pro 2 shouldn't have the drawbacks of TouchOSC when switching apps.
What is the reason MD Pro 2 doesn't have that problem Wim, just curious.
I suspect it's because MD Pro 2 is able to run in background mode while TouchOSC isn't able to. So every time you switch away from TouchOSC, it has to reload. It also means that even if you have two way MIDI communication to update TouchOSC controls, it doesn't work unless TouchOSC remains in the foreground.
There was a discussion on this topic on the TouchOsc discord (https://discord.com/channels/887723540240019556/887806764504993843/1038915377712873673)... but it doesn't seem to be a priority (and I suppose it is not trivial).