Looper Status Led / Midi Feedback

1.16K viewsGeneral
0

hey guys, can someone please help me and explain how to generate midi notes corresponding to the state of abletons looper!
i can´t get my head around with reactions 2. cause there is not really an option to select other than decive – state.
the looper device is unfortunately not listed in the devices dropdown menu.
i need to get visual feedback. ideally on rgb leds but as well on simple one colour leds.(maybe with a blinking light option for overdubbing/recording?) or i could spread the functions / status as well on multiple leds.
each one for rec, ovdb, play,stop. but i really need at least some visual feedback for abletons looper…
i would even pay extra for that function!!!!

btw: really like css so far! my setup is pretty crazy big now but it still works like charm!!
thinking back now, the time i saved is nothing compared to what it costs…

anyway, hope someone can help me.. or at least guide me a bit
greetings

edit: just quickly to explain my needs:
4 pads from a roland spd sx are mapped to abletons looper (rec,undo,clear, track mute)
and the roland drumpad has little red leds built in for every pad…. and with these ones i wanna see the looper status

admin Changed status to publish May 22, 2024
Attached Files:
0

Hi,

Some things to help you:
To send LED feedback you probably need to send MIDI velocity value to your controller (not note)
In reactions you send velocity value using the action:
midi controller > send midi velocity value to input

The looper’s state is available from (i think) device parameter 1
And I think the states are something like: 0 = off, 1 = recording, 2 = playing (or something like that anyway).
You can check that by using this script: https://remotify.io/ableton-midi-script/log-device-parameter-names

You could then create a reaction which does this:
when looper state changes (i.e. device parameter 1 changes)
In an Action…
condition : if parameter 1 value is == 1
Action: send velocity value i.e. 127 to controller input
etc

admin Changed status to publish May 22, 2024
Attached Files:
0

Hi VZI,

Aww man, I feel your pain 🙁
I’m little swamped at the minute but I’ll add this to the top of my list and hopefully figure out the problem – it sounds like you’re very close (and I’m pretty certain that the listener should be working).

John

admin Changed status to publish May 22, 2024
Attached Files:
0

I’ll get to the bottom of this, don’t worry 🙂

admin Changed status to publish May 22, 2024
Attached Files:
0

Hi VZI,

After investigating, we have found the problem…
The code being generated for device parameter listeners is incorrect – which is why listeners will not work!
While we work on a solution, here’s how you can fix it:
Switch the listener to ‘custom code’ mode and delete the following piece of code: chains[0].
That includes the full stop after it too! 🙂
See the attached screenshot.

admin Changed status to publish May 22, 2024
0

Thank you so much VZI, that’s brilliant to hear!!
Would love to see this in action 🙂

admin Changed status to publish May 22, 2024
Attached Files: