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.
How to route midi command sent from Midi Source Plugin to a widget
I've got a midi source/instrument plugin and it is sending a midi command at certain times and wondering how I can route/translate that command (ie: cc msg on certain channel) to trigger/press one of my widgets...I've been trying different things with virtual midi and midi learn, but can't connect these dots, so thanks for any guidance. I have confirmed the midi command is getting sent by using ShowMidi auv3
Thanks
Comments
Can you consider one of the IOS apps that present a BUTTON and have MIDI knowledge? They tend to function as an AUv3
That is loaded into a host/DAW.
There are two principle ways:
@espiegel123, my issue is figuring out how to get the midi source to be the auv3 midi instrument that's sending the midi command...I'm using your 2nd method and in "Devices" (I figure that's what you are referring to when you say "Choose the midi source") I'm selecting "Virtual MIDI In" but still things aren't getting triggered as expected.
Is this what you were suggesting?
What is sending the MIDI?
If you are trying to send midi from an audio AU or effect, you need to add them as midi sources:
https://wiki.loopypro.com/MIDI_Essential_Tips_and_Tricks#Audio_Instruments_and_Effects_as_MIDI_Sources
Thanks @espiegel123. It is Piano Motifs, added as MIDI, that is sending the MIDI
If it is a midi source in loopy pro’s mixer, it will appear as a source in the Devices section of midi learn panel when you tap in the lower section.
thanks @espiegel123. that's what I'm expecting.
I guess I’m just confusing something.
Here is the mixer showing the midi plugin and the devices section in midi learn
@danm - is the list in your last screenshot scrollable? "P" is after "M"(Morningstar), so just checking.
great thought @wim! I've tried to scroll that list probably 50 times today as I go back and forth trying to figure out what I've done wrong here, but no it's not scrollable
Are you sure it isn’t scrollable? There are several midi sources not showing in that list. When that happens dragging with your finger should scroll the list.
Try saving and reopening the project?
Could be a bug. I've never dealt with a midi source dialog with that many entries. I wonder if it makes any difference if you turn the device to portrait.
Is it possible for you to stop all other midi sources but Piano Motifs, then go to midi learn to see if the notes coming from it are registered?
@danm : it is because you are learning into a Global profile. You need to learn into a project profile as AU references are local to the project.
@espiegel123 and @wim, tried saving, closing project, closing loopy, opening loopy and re-opening project.
I see less midi sources, but still not scrollable...and btw, none of those things are actually attached at the moment (ie: Akai, Launchkey, Morningstar, etc...I've never even had iRig and SINCO, perhaps those are left over from the sample project that @espiegel123 created, that I've been enhancing...should any of these things show up if they are not active and attached at the moment?
Hmm...okay, why'd it default to the global one, I wonder...is that typical?
@espiegel123, this is built off your sample … how do you recommend I proceed, should I create a new project profile for basic stuff like this or add it to one of the ones you already have here?
@danm i would create a new project profile for bindings you are adding.
Okay, will do. Since you are constantly changing profiles in this project, would the one I'm adding likely remain active in addition to the ones you are engaging/disengaging or will it likely be stopped as you stop/start those other project profiles? Thanks for your thoughts
I believe that all of the profile switching is set up to be limited to the relevant profiles.
It may be worth your while to see how that is all set up.
The auv3 presets are not affected by global vs local project stuff, correct?
Presets are showing up in the auv3 preset list when I create them in Loopy Pro (in the Piano Motifs UI window), but appear to do nothing when recalled (ie: no noticeable change to the Piano Motifs state)...I'm assuming this is related to Piano Motifs not implementing something required by LP for Presets to work, ya?
Sounds like something on the Piano Motifs side.
Makes sense.
In a Piano Motifs thread in General Apps I asked the dev and he responded:
Hi @danm , Piano Motifs doesn’t implement any presets, but it does implement state saving. I guess in Loopy Pro state saving is performed when you save a project or automatically if you close the app. When you open the project again, the motif and it’s settings will be retrieved. Now, if what you want is to have one Loopy Pro project and be able to save and retrieve Piano Motifs motifs+settings, may I suggest you use the Piano Motifs Save and Load functions. When you press Save, both the motif and its settings will be saved in the Piano Motifs Library. To retrieve, just press Load. Hope this helps.
If you have any info I can share with him so he's aware (if he's not already) how to make this work with Loopy Pro, I'll pass it along...or feel free to share yourself if you'd like, here's the thread:
https://forum.loopypro.com/discussion/38865/piano-motifs-by-fernando-morales/p79
Do you have AUM? If so, open Piano Motifs and try to add a preset. Is the Save in Plugin option available?
I don't have AUM
Perhaps you could ask someone in that thread to try what I suggested..
Normally, if an AU doesn’t have the flag turned on that it supports AUv3 preset-saving, loopy pro saves its state into a preset when you save a preset. If an AU indicates that it supports the OS’s preset saving mechanism then Loopy makes use of the OS calls.
@espiegel123, the developer responded:
Hi @danm, since Piano Motifs doesn't implement Presets, the Save in Plugin option is greyed out when you try to Save a Preset in AUM.
The next question, which I’ve asked, is what happens if AUM’s Save in AUM option is used.
When Save in Plugin isn’t available, Loopy Pro uses the plugin’s state-saving to save /recall presets. If state-saving works for the plugin, this should work.
When you save a project that contains Piano Motifs, is Piano Motifs restored to the expected state when you reopen the project?
@espiegel123, when I save an LP project that contains Piano Motifs, Piano Motifs does appear to restore to the expected state (all I've tested is if it is has the correct Motif loaded, haven't checked all the settings) when I reopen the project