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.
Routing sysex messages?
Is it possible to selectively route sysex messages to just one connected device at a time? Say I have two MIDI devices connected that can respond to the same type of sysex message, and sometimes I want that sysex to go to the first device, and other times it goes to the second. I’d like to do this dynamically from a script, without having to manually reconfigure something.
From what I can tell, I can only broadcast sysex messages to all connected devices at once, but maybe I’m missing something. Perhaps this is possible with one of the iConnect interfaces?
Comments
@orand Never had more than one of the same device to send info to so no real world experience with this particular issue. From what I understand, in between the company ID byte (i.e. Roland) and the model ID byte (TD6) there is a device ID byte. How you figure that out/find it- I’m not sure. Looks like you can have up to 32 of the same devices though receiving their own info.
Thanks, I wasn’t aware of that. I just sent a message to Arturia asking them if their devices support this. I’d like to do this with a MiniLab and a Beatstep, both of which use identical sysex messages.
If you can't get that information, then another way might be a set of Mozaic scripts. There would need to be one master that isn't routed to anything, then one on each channel that receives the sysex before it goes to the target. The master could communicate via global variables to the receivers to tell them whether or not to pass the sysex through.
It sounds harder than it is. The scripts should be very simple.
Actually, the master isn't even needed. Each "sysex solo" script can communicate with the others via global variables. So all you need to do is set the a number for each instance to identify it, then from any instance pick which one should get the sysex.
Probably easier to code than to explain. I'll try something out shortly here.
Brilliant! That should work perfectly. I’m already working on a circular buffer for outgoing sysex messages due to hitting the batch limit, so I’ll just switch the buffer to use global variables and it should “just work.” I can use one buffer per device to keep it straight. Thanks for that great idea.
Agreed, that makes sense. I already have a “master” script that writes to my sysex circular buffer(s), so what I will likely do is just create multiple separate “sysex sender” scripts that are identical other than config at the top which tells it which buffer to send from.
Great! I won't bother with a prototype. It sounds like you have it dialed in already.
Just don't name your circular buffer script "Circle Jerk", OK?
They can't be identical as the device ID would be different.
This article helped me a lot dealing with arturia sysex:
https://www.untergeek.de/2014/11/taming-arturias-beatstep-sysex-codes-for-programming-via-ipad/
Yep, that page has been very helpful. Unfortunately the MiniLab device ID is identical. All the messages to and from the MiniLab (including from Arturia’s own software) start with “ F0 00 20 6B 7F 42”, which is why I can use the messages from Untergeek’s Beatstep page as-is with the MiniLab. Others in the comments have done the same. I’ve also discovered a few more useful messages myself that aren’t documented there (yet).
My Arturia support request is being forwarded to someone more knowledgeable now. Fingers crossed…
Welp, just another reason to fuel the fire if my arturia distain