🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

Send parameter value from Ableton to MF Twister

General
Submitted by grandyzer on Mon, 04/08/2024 - 00:50
grandyzer
Control Surface Studio User

Hi folks,
I am just getting started with a simple script for the Midi fighter twister using the Remotify template.

I have successfully assigned knob 1 to control parameter number 20 of the selected device of a selected track.

The issue I am running into is that the value of the encoder isn't updating when I switch to another device so I can seamlessly transition to modifying the value of another device. The parameter is instead jumping to the value of the ecnoder which was set when it was controlling the last device.

Is there a way to send the value of the param from Ableton to the Twister? I believe I have to use REactions, but the video is not clear on how i should do this.

Thanks,

Topic Category: 

3 Responses

Comments

Glenn Verhaeghe
Control Surface Studio User
Glenn Verhaeghe - Mon, 04/08/2024 - 16:37
#1

The Device Parameter Mapping in the added .json file controls the first Parameter of the selected Device on the selected Track with the top-left knob of the MFTwister. When I change selected Devices, it updates the LED ring accordingly on my Twister. Does it work for you as well?

It would also be useful if you could send an export of the mapping that's not working correctly.

upload files: 
Binary Data MFT LED Ring Test 20240408_1729.json
grandyzer
Control Surface Studio User
grandyzer - Thu, 04/11/2024 - 00:41
#2

Thanks Glenn

I have attached my script (I couldn't get yours to work).

I am trying to start really small, so this script is only supposed to control the volume of any Simpler device that has been selected.

So far it is controlling the volume of any selected Simpler device, but it is not "picking up" the value of the parameter of the device I selected and continuing from there. The parameter is instead picking up the value of the encoder on the Twister, which is making the parameter jump in value.

Thanks again

upload files: 
Binary Data 1_script.json
grandyzer
Control Surface Studio User
grandyzer - Sat, 04/20/2024 - 20:23
#3

I am absolutely at a loss here. I've been banging my head against this controller and program trying to get just one knob to do what I need. Is anyone at all able to help?

- I am trying to get just one knob to control the volume of any selected Simpler device. Why is it that when I change Simpler device, Ableton does not send the volume of the newly selected Simpler to the encoder? Instead, the encoder is making the volume parameter jump. This is an endless encoder. There is no reason it should be doing this.

Am I missing something here? I have tried:
- Setting the knob to absolute, but the encoder makes the parameter value of any Simpler I select jump to a new positon. I shouldn't have ot use the "Pickup" or "Value scaling" modes with an endless encoder to avoid this.
- Setting the knob to "relative mode' which moves the parameter from its most recent position, but the LEDs are incorrect when I do this. Values from -0.1 to -36 are not displaying at all (below 0 on the encoder).

What the hell is going on here? How can the MF Twister be this expensive when it's so difficult to ocnfigure and operate as an endless encoder? Hard mappings for a device liek this defeat the purpsoe of using an encoder.