Sending On/Off Values to a Send encoder in Ableton

538 viewsGeneralSENDS
0

Hey Guys,

Stuck trying to send an on/off string to a send encoder in Ableton

At the moment Midi Controller is set to toggle a CC message between values of 0 (off) & 127 (on)

When i set up a string to go to a ‘send track 12’ or Send L the Send track doesn’t work.

When I override the Midi Message in CSS to Absolute then it works but the LED feedback option is not working for me…I set up a reaction with conditions based on the value of the send and sending a MIDI velocity value to the controller input but this causes it to stop working.

Before this I tried a simple on/off over ride but this also doesn’t seem to function for Send Tracks.

Script Attached

Glenn Verhaeghe Answered question August 19, 2024
Attached Files:
0

Using a Knob

What worked for me was setting the Control Type to Relative, with number of Steps set to 1. I had no problem with LED Feedback set to Default on my MIDI Fighter Twister.

Using a Button switch

If you want to toggle the Send between on/off states using a Button, then you need make sure the Send Range Min value is set to 0% and the Max. value to 1%; see the last comment in this post for more info.

R. Posted new comment August 19, 2024

Thanks Glenn,

So I’ve got it function now with a button – the 0-1% trick worked a treat.

The Issue I am now facing is a soon add LED feedback as an option it overrides the button functionality from a toggle to a Momentary switch.

On the MIDI controler I have it defaulting to Toggle, on the Control Template it’s toggle and on the Switch Override I have it as on off, but as soon as I change LED feedback away from the default and to custom it seems to change to momentary functionality.

0

When you say functionality becomes Momentary do you mean:

  • The Send (in Ableton) only becomes 127 when button is pushed down and reverts to 0 when button is released?
  • The LED only lights up when button is pushed down and it’s unlit when button is released?
  • Both previous points happen together?

What have you set your custom LED Feedback settings to?

In your first script I saw you set the LED ON value to 1 and LED OFF to 127. What’s the reason for that?

Is the button you send feedback to the same as the one you’re pressing down?

Glenn Verhaeghe Posted new comment August 22, 2024

Hi Glenn,

Thanks for your response – I’m not sure I described the functionality correctly but let me correct that.

So the issue I have is that when I engage LED feedback option the number of buttons clicks it takes to scroll through the on/off cycle goes up from 2 to 3.

It goes from 0 to 127 back to 0 – then I have to press the button AGAIN and it still stays at 0. Only then does the cycle start again.

In other words it takes 3 button clicks for something that only needs 2 when LED feedback is off.

I have LED feedback set to custom, on is value 1 (red) and off is 127 (white). The Yaeltex control takes colour values as numbers.

The behaviour is the same if I uncheck the ‘Send LED Feedback Box’ and If I send the LED Feedback to a different button.

As soon as I turn LED Feedback off, the button returns to 2 cycle On/Off Functionality.

I was able to recreate your problem on my device. I set the CC Mode of my button to toggle, like you have, and it started behaving that way as well. Even with “MIDI Learn” on in CSS, It shows that the software receives the value of 0 twice when you have to press it twice, which is very odd behaviour (MIDI Learn is that row at the bottom right side of CSS’s screen that shows which MIDI signals are received by CSS).

I don’t understand why the problem is happening but one way to solve this is to set everything to momentary. With “everything” I mean:
– The message that is sent out by the physical button (in other words, the mode of the button inside your physical device)
– The setting in the template for this button
– The setting in the mapping

Then, I think, it will behave as you want it to. I think it’s even a safe bet to set all your buttons to momentary because you can make them act like a toggle using the settings in CSS. But it’s still very odd behavior, that I wish I knew the answer to.

I’m going to make a bug report about it and see if anyone knows what needs to be done.

Edit: I thought I found the solution and started deleting my previous comments, but then I checked again and found I was wrong so I’m reuploading my previous comment 😀 . Sorry for the many notifications.