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.
Button status, light ON or OFF...
Hello,
I need some advice to properly configure my buttons in Loopy Pro.
Here's an example :
I'd like to have a button that activates the "Loop section" function for my plugin JustChords (auV3 in LP). This function should be controlled by Midi CC 51.
I created a "standard" Loopy Pro button.
Then I created a "Toggle" action for this button.
I set the action correctly to have the button sending the midi message CC 51 to my plugin.
This works but I have to press the button twice to activate or desactivate the "Loop" function of Just Chords. This results in no way to have visual feedback on the "loop function" status.
I understand that's a normal behaviour because the midi message is only sent when my button is "active" (= lit ON) and nothing is sent when it's lit OFF. I guess I should have 2 distinct values for my midi message (127 for ON and 0 for OFF) but when choosing a "Toggle" action the "data value" of the CC is not available.
I tried to choose a "PRESS" action instead of "Toggle" but in this way I can't have any visual status of my button (lit ON or OFF to know if the loop function is ON or OFF) as the button only flashes quickly when pressed.
Can anyone help me on that ?
Thanks for your replies.
Comments
The right way to do this would be to use the button toggle to set the MIDI AU parameter for Loop. That way the state would provide feedback to the control so that it doesn't get out of sync if you change the mode in the plugin.
However, the AUv3 parameter isn't working in JustChords. This is a problem that should be reported to the developer. It happens in AUM too.
There are some ways to make the button light while reverting to using CC control, but it's almost 3:00am and my brain is too foggy to work on it right now. I'll be back later with some options if the amazing Mr. Ed hasn't already chimed in by then.
OK thanks a lot @wim for the 1st part of the answer
I'll wait for you to come back after a few hours of sleeping !
It's almost 12 AM here ;-)
Toggle with send midi message will alternate sending cc value 127 and 0. Value 0 gets sent when the button when the button is pressed while lit at which time the button becomes unlit. Use a midi monitor to see what is happening.
If it is taking two button presses to toggle JC, it may toggle its message when it receives value 127 rather than use 127 for on and 0 for off.
To test this, create a button that sends 127 and one that sends 0 and see how JC behaves.
@Steve77 : I just checked. JC toggles the loop setting when it receives value 127. Unfortunately, Loopy doesn’t know the loop mode setting.
I notice that the AU has a loop mode AU parameter. But it looks like it isn’t working. If it were working, you would want to toggle that parameter as then loopy could set the button state to match.
Humm ... so I tried a workaround. The workaround is functioning as far as the button light goes, but I can't get the Loop setting to change even with the right CC sent to it from a button.
@espiegel123 - did you try from a widget, or from a hardware controller?
Widget
Thanks @espiegel123. Must be user error.
I considered sharing a trick but it could lead to the button state being the opposite of JC’s. I’ve let the dev know that the param seems not to work.
Well ... I'm stumped as to why I can't get a widget sending CC 51, value 127 to JustChords. I've added the trigger, but it just won't work for me.
Anyway, my workaround was going to be to add a "dummy" toggle button to give the original button something for feedback. The original would have Press action to 1) send MIDI to the plugin, and 2) trigger the dummy toggle. Not a great workaround as it would be easy to get the app and the toggle state out of sync. But it would sort of work.
The JustChords developer is very responsive. I think it's better to wait for the bug fix.
I am sending note on rather than CC
But I just tried CC and it works. JC responds to ON only. ON toggles JC’s setting.
I'm gonna drop this now.
I tried with note on. I tried changing DATA 2 to 0 as in your screenshot (it was at 127 before). I tried changing to CC 50, as in your screenshot, thinking maybe the developer was off by one in the numbering. None work.
No point pursuing why a workaround that isn't the right solution to begin with isn't working.
Data 2 is the midi channel, I believe.
Btw, I am using a JC TestFlight. Possibly the App Store version behaves differently.
Wow !
Thanks for your investigations @espiegel123 and @wim
I'm not such a midi expert !
So it seems that it's a bug from JC ?
If yes @espiegel123 have you reported this to Marek the developper of JC ?
The midi works fine for me.
It is adjusting the AUV3 parameter directly that isn’t working. I have let the developer know.
There was an App Store update yesterday that fixed the MIDI trigger not working for me.
No, it's the CC value. Either that or the developer thinks that there are 128 midi channels available. When I had the Data 32 set to 0 the trigger didn't work (from a button set to send value 127). When I changed that to 127 to agree with the button, it worked to toggle looping mode.
I have no clue why it works differently for me than for you.
So ... if @steve77's installation works the same as mine. A somewhat crummy workaround for the button lighting issue is:
For the first button set two actions on Press
If the state of looping in JustChords is off when the button is lit, then toggle it in the app to match the button. After that it'll stay in line. It'll get out of sync again if you make the change in the app, or in some cases on project load. Can't be helped until the AU parameter is working.
Thanks a lot @wim ;-)
I think I understand the logic in it... I'll try that asap !
Oops! I was using press/release so the release (Val 0) was triggering it. Thanks for the correction.
That works perfectly @wim thanks a lot !!!
@Steve77 ; the latest JC beta fixes the AU looping parameter. It allows you to toggle the setting with the Adjust Parameter action.
When version 9.20 is released or if you use the current beta, the Adjust MIDI AU parameter action will work in a button with the action set up as shown below. I was using it as the button’s press action
Great !
That's a lot simplier like that !
Thanks @espiegel123
I was hoping the parameter "Selected song" would work... but no success.
Do you manage to load a specific song with the "Adjust AU parameter" action ?
Are you a member of the JC Discord? If not, I suggest joining it. The developer is eager for feedback and responsive. Let him know about any issues you have.
https://discord.gg/3BdHEdAF77
Yes I am a member of JC discord forum, I’ll tell Marek about that ;-)
Thanks !