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.
Single MIDI configuration (destination, channel) for multiple widgets ?
Is it possible to group widgets in Loopy Pro, so that the MIDI channel and destination can be set for all widgets at once?
I want to control hardware and avoid the chore of having to set up MIDI for each individual widget. One possible solution that comes to my mind would be some kind of dummy MIDI track as receiver for all widgets. The problem here is that it does not seem to be possible to create an empty MIDI track that has no plugin loaded.
Comments
Could you use a script (Mozaic or StreamByter) to be controlled by the widgets, and send the desired messages?
Edit: Also, StreamByter loaded as a plug-in, with no script, simply relays all input messages to its output.
As @uncledave says: Streambyter loaded as a Midi AU with no script is the we way to go. It is also how you can send midi to Loopy’s mid control from within loopy.
I was thinking about that kind of workaround. I wasn’t sure if there is a plain way of achieving this without additional plugins in Loopy Pro.
In loopy, you midi messages have a single target. I don’t know of another way to redirect a single target to many for arbitrary midi messages.
mfxStrip is handy for avoiding scripting for this kind of thing.
[Edit] Unfortunately it doesn't expose any AU parameters, or they could be changed from a widget, so not a good solution.
To be clear, Streambyter needs zero scripting for this use case. You just load it with no script. And its free.
I'm assuming the midi channel sent from the widgets needs to be changed as stated in the OP.
Re-reading the OP, I guess I am not 100% sure I know what he meant. I may have misinterpreted.
@catherder : can you clarify what you mean by the set the MIDI channel and destination of all widgets at once? Are you talking about MIDI bindings TO the widget or the MIDI sent by a widget that has a send midi action. (Widgets themselves don't have MIDI settings)
Let me clarify the situation: I have an external piece of kit - a Korg Volca Bass for example that has settings that I want to control via widgets in Loopy pro. As far as I can see, I would have to configure a Midi action that includes the Volcas Midi Channel, and the Midi destination (interface) for each widget. I find this complicated because the moment I want to use another Midi interface or channel, I'll have to edit all widgets.
TouchOSC for example has a hierarchical object structure that allows for widgets to be grouped and use settings from the parent widget. For Loopy I cannot see such an option, so I was thinking about bundling the output of all widgets into one midi track, that then has a specific channel and output interface configured.
There isn’t that sort of abstraction. So, you would need to send through a dummy AU such as streambyter, mozaic or mfxstrip.
If you initially set up your send midi actions with the desired midi channel, you could use streambyter without a script. If you need to later change the midi channel it would just be a few straightforward lines that someone would probably be happy to supply if there isn’t already a script to do what you need.
im trying the streambyter thing, new to loopy. made a template and realised I cant realistically share it unless I do this streambyter workaround. it looks like its working and I can just use it as a midi monitor too, but am I doomed to have a big bar at the bottom of my template that says streambyter now?
Click the "eye" icon to hide the stream and not show "the big bar".
That setting is not easy to understand what it does.
You can turn of AU’s being displayed down there. Open the AU window. Click on the gear icon. Tap the eye icon to toggle visibility of the AU button.
Would be nice to extend control groups to abstract midi outputs in Loopy directly.
There is a a site for adding feature requests and upvoting existing requests:
https://roadmap.loopypro.com
And here is the feature request waiting for up-votes:
https://roadmap.loopypro.com/feature-requests/p/midi-bus
@quadbus @espiegel123
thanks guys thats great
@catherder upvoted and commented. at least we have some sort of workaround.