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.
Questions about midi control of auv3 presets in Loopy Pro
I'm setting up an MC6 Pro, using switches A thru F to select different Tonestack pro preset effects.
Wondering if the best approach is to use midi learn in Loopy Pro.
Does this approach target only the specific Tonestack instance I select when Midi Learn'ing?
Appears so, just wondering if there's anything I'm missing or should be thinking about up front.
Also, is there any way to have Tonestack plugin instances share their presets when running within Loopy Pro or do I just have to replicate/save the presets for each instance of Tonestack auv3, if I want all the instances to share a similar set of presets?
Thanks
Comments
Tonestack Pro 1.5...so also wondering if it is recommended to always instantiate "Tonestack Pro MIDI" (not Tonestack Pro) as auv3 Plugin for this type of usage...are there any use cases to use "Tonestack Pro" vs "Tonestack Pro MIDI" with Loopy Pro? Thanks again
The non-midi version I believe is only there for compatibility with pre-midi tonestack projects
ToneStack responds to whatever midi you send it. I am not sure I understand the question.
Presets are not per instance. How to handle presets depends on whether you want to use Loopy’s preset system or tone stack’s.
New territory for me...I'll do some tests and see, but sounds like I can send midi to each plugin instance individually (ie: to A, B, and C individually), which is what I'd like to do.
Ah ok. I've been doing "new" and "save" from the folder icon on the top of the plugin's (Tonestack Pro in this example) window. Those presets don't appear to be shared across instances (or maybe it was bc I was experimenting with Tonestack Pro and Tonestack Pro Midi instances that I saw this behavior).
I'd like to have presets be avail across plugin instances, so perhaps I should use Loopy's preset system. I'll read up on this, let me know, please, if you feel there are some recommended resources on this, outside of the manual or wiki.
Thanks very much
What do you mean that they don't seem to be shared across instances? Can you post screenshots demontrating? Any preset you had to Loopy Pro will be available to any instance of the same plug in.
If you find a case where that doesn't happen that would a bug. When you drop down the list of Loopy Pro presets from your different ToneStack Pro instances, do you not see the same list? Notice that they all need to be instances of the same type. ToneStack Pro and ToneStack Pro MIDI are different plugins as far as a host is concerned.
The confusion was relating to "Tonestack Pro" and "Tonestack Pro Midi" being treated like different plugins from the host perspective. Especially confusing when there is no visual difference between the two in the mixer channels and the differentiation on the bottom of the page is very subtle (TSP vs TSPM)...Now things are making more sense, thanks
There is no reason to use the non-MIDI version of ToneStack Pro. I believe it only exists so that people can open projects that contain ToneStack Pro that were created before the MIDI version was available.
Right, I wasn't even really initially aware that both were there/different and was arbitrarily selecting either...now, I'll only use the MIDI version. Perhaps the non Midi version can even be safely deleted from my devices, will have to look into that
There isn’t a way to do that as far as I know.