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.
Is there a way to have a widget action send MIDI cc cmd to all instances of a certain AuV3 plugin
Is there a way to have a widget action send MIDI to all instances of a certain AuV3 plugin vs being bound to a specific instance of the plugin?
I expect I can use StreamByter or other plugins as the target of this midi cmd and then have StreamByter route to multiple instances, but I'd like to be able to do this over time as the instances may change.
In LP, when you have 2 instances of plugin X, they would be called Xa and Xb. If my widget action has target of Xb and I remove that instance at some point, then my action no longer has a valid target. Is there way to make this work more dynamically, so I can have the action target/send to any/all active instances of this plugin?
If not, is there a way to do this via StreamByter (ie: target all active instances, perhaps up to a certain number of instances), haven't done any scripting in StreamByter as of yet, so thanks for any thoughts.
Of course, if there is a simpler way to do this, please let me know...Thanks
Comments
Effect or Audio Input plugin? I assume you know about "clone" FX instances synchronize settings across each instance, and I assume this isn't what you're after.
There is no Loopy Pro feature to do what you're asking. I'm not sure how Streambyter would help either as if you remove a plugin then there's no target for the midi routing either.
If you're asking about Audio Input plugins, then leveraging the Replace functionality might help. Rather than removing the plugin instance, you can long-press on the icon in the mixer and select to Replace it. This keeps all routing in place. It probably won't work for plugin parameters, but should work for MIDI. I use Streambyter as my "placeholder" plugin of choice for this purpose.
@wim, MIDI plugin.
As I said, haven't used Streambyter yet, but thought it allowed scripting, so was hoping there might be a way to do something like iterate through all LP plugin instances that contain or start with a certain string (ie: the plugin name) and then route the incoming midi to each of these in the list...that way, whether there is one instance or 4, it would route the incoming midi to each of them
No, streambyter can't do that. It has no awareness of plugin instances. It just receives, acts on, and outputs MIDI. Mozaic is the same.
You need to work within the routing possibilities of the host. Loopy doesn't have plugin-wide awareness across instances of action and MIDI routing. No host does. The closest any host comes to that is Loopy's "clone" FX instance capability.
@danm: While mozaic and streambyter do scripting, they are doing scripting of the midi stream that passes through them. They can receive midi and send midi but can't manipulate the host or know anything about it (other than knowing about the host clock).
Thanks @wim and @espiegel123