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.
Trigger Widgets.
This is a widget question because the multitrack Drambo sequencing view ( in vid )
Dosent have solo on its track buttons.
So creating a loopy midi template anyway for macros.
The square buttons are mapped to Drambo solos.
The bigger square button to right is a trigger widget.
My setting are toggle for the midi out to Drambo solo buttons.
It seems I can only choose press/release for the trigger widget.
Is there no press/hold midi out.
So that a widget can release with release ?
The idea is to solo with track squares but release all solos with 1 button.
Although Drambo solos dosent seem available in multitrack sequencer mode.
In non multitrack sequencer mode. You can actually acheieve whats needed because you solo with the track buttons ( which arnt midi mapped ) and have 1 global button from loopy midi out, to unsolo all.
With the only mode seemingly available.
Toggle as midi out commands to Drambo and trigger widget to these buttons as press/release.
It switches all tracks briefly on, before unsolo all.
Comments
@sigma79 : What you want is probably possible but I am not understanding your question. Can you explain in more direct terms what you want the button to do.
[Like: when I press the button , I want it to send midi cc 20 value 127
What does “press/hold midi out” mean?
What does “release with hold” mean?
Press and hold are both supported. They are different gestures. Press is a short tap. Hold is a long one. Release is the gesture when you remove your finger at the end of the tap. Toggle is a behavior when presses alternate between sent values.
In vid.
I solo by just pressing the Drambo solo buttons.
Then instead, with loopy mapped ( the first 3 white squares to the 3 Drambo track solos )
Then a master un solo using a trigger widget pointed at the 3 loopy squares )
It dosent sound that bad.
But you hear audio of the other tracks soloing, before a master un-solo.
The settings are different cc numbers to Drambo track solos and setup, as toggle in loopy.
The widget points at the first 3 squares in loopy and set to press/release.
@sigma79 : I don't know anything about the Drambo side of things.
Can you explain what you want the button in Loopy to do. Let's take it one step at a time.
What is the first thing you want the button to do that you don't know how to do. On the Loopy side of things, it sounds like all Loopy needs to do is send midi messages.
Iv progressed.
I can make the command to Drambo solos
But cant trigger the on off state of the loopy buttons that the widget points at.
The loopy midi outs are toggle and release ( with release inverted )
The widget is release sent to each loopy midi button.
This makes it work but the widget dosent turn off the toggle state of the loopy buttons.
Just need to acheive this.
But the midi button here that releases all Drambo solos.
When using loopy.
Has to be a widget pointed at loopy midi out buttons ( which solo drambo tracks )
It works but the widget dosent trigger the midi buttons on off state.
A couple of things. Sending midi from a button doesn't result in a visible state change. See these wiki articles:
https://wiki.loopypro.com/State_Feedback
https://wiki.loopypro.com/Tech_Note:_Persistent_Send_MIDI_Widgets#Tech_Note:_Persistent_Send_MIDI_Widgets
I don't understand what you mean "the widget doesn't turn off the toggle state of the loopy buttons."
I am also not quite understanding what you are saying about toggle and release. Can you post screenshots of the widget actions and say what you want to happen and what is happening.
A trigger widget points at loopy midi buttons, which point at drambo solos.
You use the midi buttons to solo drambo per track and the widget to unsolo all which are solo.
It works but the widget pointing at the buttons dosent trigger the correct visual state of the midi buttons.
Which would be off because its turning off the solos.
@sigma79 : can you post screenshots of the action details of the toggle and release actions of your buttons?
Are you aware that when you have toggle and release gesture actions for a button that every time you put your finger down on the button and lift it that both the toggle and release actions are sent?
I toggle solo with the midi buttons.
Then unsolo all these midi buttons with the trigger widget.
Even then, it will toggle solos because some will be on and some will be off.
I confirmed it with a hardware mapping and mapping hardware button to trigger widget. Then the trigger widget, triggers the midi buttons ( after I have pressed the midi buttons via screen for solos ) Same result.
It just seems the trigger widget is recieving data anyway. Its not 100% send of data ( a midi button can trigger the widgets on/off state etc )
So settled on the widget being press/release, whilst the midi buttons are toggle.
It just means there will be slight audio bleed as you un solo all but you have to time solo anyway.
This is my drum ipad anyway.
What acheived with Drambo and loopy ( plus hardware controllers )
Kind of overkill ( cost ) etc.
And im currently liking just sampling all my drum apps ( acoustic sounds )
Where iv got a Fac drum per track.
I can layer/sequence say 4 snares
Or perhaps frequency shift and sequence a seemingly variation of a drum.
Obviously when sequencing electronic synth kits of fac drum, theres more variation to sequence, rather than using samples
The loopy controllers are just perfomance of euclidean sequencing.
Then a standard drum sequence loopy controller ( with the solos ) and macros. So you get the multitrack sequencing view of Drambo.
Will see what Battalion will be like ( may then forget this drum build )
Can you get it to work though ?
Its a host or app which needs different cc for each solo
Loopy midi buttons will trigger these solos.
Another loopy command ( the trigger widget ) Will un-solo all that are solo, without turning on solos that wernt on.
@sigma79 : I’d love to help you but I am not understanding your explanations. What I need to know is what midi you need loopy to send and how you want to trigger them.
The details of how you map Drambo to respond aren’t as far as I can tell necessary for this.
I asked some questions in my previous post whose answers would be helpful.
I suggest using a midi monitor to examine the midi loopy is sending. The combination of using both toggle and release gestures is something I wonder about.
Do you really want every button press to send two messages: one whose value toggles with each press and another when you lift your finger.
With Drambo the track select buttons are also for solo and mute. You swipe up and down.
In a different Drambo mode, these solo arnt available.
So in the mode which they are available.
It were just a case of sending a loopy midi out command and probably just set to release. All the Drambo solos midi would be the same for the one loopy midi out button because you would use the Drambo tracks to solo. You would just need a master un-solo button ( loopy )
So now I have to add loopy buttons because the Drambo buttons arnt visibly available but now they would need to all be different cc numbers.
Id still need a master release button, thats pointed at the multiple midi out loopy buttons ( which also visually toggle ) to correspond with the solo states.
I need this.
Its solo via touching screen track buttons ( they are then on )
The loopy button sends release ( so that the button dosent then switch on tracks, whilst the others off )
Loopy would now need midi buttons that are mapped to Drambis solos.
but then 1 release button.
This button would need to be a trigger widget because all the other midi out loopy buttons are a different cc.
Any solo buttons you press and are toggle.
Pressing the widget will release any toggles without triggering others that arnt toggled ( so I guess just a release command )
Im aware of toggle and release being on.
but just sending a toggle from a widget will toggle some off and others on, depending on state im pressing, on the midi out buttons.
Maybe im not understanding what trigger widgets are for ?
@sigma79 : “ Maybe im not understanding what trigger widgets are for ?”
There isn’t a type of widget called a trigger widget. “Trigger Widget” is the name of the Loopy Pro action that can be used so that a widget or midi binding can act on a widget.
It would be much easier to help you if we could take one issue at a time and discuss it only in terms of the loopy actions and the midi messages you want to send without getting into the Drambo side of things.
It seems like there might be a misunderstanding about how Loopy’s gestures and messages work, but I can’t tell.
If that isn’t of interest to you, maybe someone else has a better understanding what you want and can help you better.
Its cool.
Thanks for help though.
If you can figure it out though.
The four buttons on the left will send out a different cc ( for each button )
And have a visible toggle state when pressed.
The button on the right will turn off all the buttons on the left, including visible toggle state.
Without turning say the 4th on. If its only the first 3 that are only pressed ( and waiting for release )
@sigma79 : did you read the wiki articles I linked to earlier? One is about sending midi and state feedback. If you want to use a button to send midi and have the visual state reflect the midi that was sent, you need to use a second widget with it.
https://wiki.loopypro.com/Tech_Note:_Persistent_Send_MIDI_Widgets#Tech_Note:_Persistent_Send_MIDI_Widgets
I will show you an example after I have more information.
What specifically do you want each of those buttons to send and when?
@sigma79 : what does “waiting for release” mean when you say“ … If its only the first 3 that are only pressed ( and waiting for release )”
For this particular case, you might want to use a slider set up as a fake button… when you answer the questions, I’ll explain how that works.
The big button on the right should be only able to switch off any of the 4 buttons ( if they are on )
And these 4 buttons send out a different midi cc each.
It needs to be made so that I can send out cc from these 4 buttons but the big button can only turn them off.
How does it work mate ?
@sigma79 : “ What specifically do you want each of those buttons to send and when?”
As I said, when you answer the questions I can show you. Still unanswered:
What specifically do you want each of those buttons to send and when?
What does “waiting for release” mean in your earlier message. In Loopy, “release” means lifting your finger off of a button.
Im not sure of what needs to be sent and when.
If you check last vid.
If I switch on the first blue button ( with my hand ) which is sending midi out to Drambo solo.
When I press the green button, it will deactivate the blue button ( but not activate the 2nd blue button in the process )
If I press both blue buttons.
The green button will deactivate both blue buttons.
The green button cant activate the blue buttons ( id be doing that with my hand )
The green button can only decativate any blue buttons that are on.
@sigma79 : if you can’t say what midi messages you want the buttons to send , I can’t really advise you.
I cant say but you can see what Im trying to acheive.
The blue buttons send out midi and are then lit.
The green button should turn these off.
It actually does the needed ( turn off solo elsewhere )
But not the lit buttons.
I have to deactivate myself.
I just dont understand the trigger widget.
The first blue button can trigger the green trigger widget ( I thought the trigger widget is the trigger to blue buttons only )
I can also achieve what I need to do ( with midi )
But not turn off the lit state of the blue buttons.
I just need the green button to turn off the blue buttons and the blue buttons send out midi.
What example might you have ?
Iv shown enough videos.
@sigma79 : here is a project that shows how to use sliders as toggling midi buttons with a button that turns them off.
The “buttons” are actually sliders
The press action for the slider is set to toggle the slider
The big button sets each slider to 0
Dosent seem to work espiegel.
I choose sliders then a big button ( button )
I set the midi message for the sliders as press.
1st slider ch 1. Cc 1
2nd slider ch1. Cc 2.
Then button is set throught trigger widget.
Press.
Choose slider.
Then set make settings same ( as your trigger widget pic )
For both sliders.
@sigma79 : did you try my project ?
did you examine how each of the widgets is set up?
does the example work when you run it?
Can you post screenshots of each of the widgets actions in your project.