Your shopping cart is empty.

M4L Parameter Assignment is random

Submitted by geraldbiggs on Fri, 01/24/2020 - 02:32
Control Surface Studio User

Hi there.

I have a possible bug with the midi fighter twister.

I've included a screenshot of the issue - where the same knob controls seemingly random knobs for the m4l devices.

I notice that the blue hand isn't showing - so maybe it's a setting on my part?

The default midi twister script (outside of css) works fine.

Thank you. I can provide more information as needed

Topic Category: 

5 Responses


Control Surface Studio User

Ah, I see the blue-hand thing is what locks ableton to a "top 8" paradigm. Interesting that it would mean max4live knobs are out of sequence.

Control Surface Studio User


I figured out the quirk! It's a good one - solution below

In my screen shot - I've created 3 dials from left to right. Initially they all worked in order. as live.dial, live.dial[1], live.dial[2]

I fiddled with the visual order - all the knobs worked the same. I didn't grok the whole python scrip that CSS makes - but I imagined it'd be operating on the names of each knob and putting them in order. So I changed the last knob and changed "Long Name" it to "Z." My third knob controlled it.

Then I changed the Long Name of the third knob to "A." My first knob controlled it.

Hopefully, if the list is always sorted by order of long name (maybe also scripting name).... and the display name is "Short name"

I've included a screenshot where the third dial on the right, is controlled by my first knob on my controller - due to the long name being "a." I'm very underslept so I hope this is helpful to someone.

I believe the line is here:[x]

So the problem is not necessarily CSS. Except that it relies on the iteration through the array of parameters by index. Assuming the sorting method Ableton uses is safe - relying on alphanumeric sorting is probably safe.

On native ableton effects: It seems that the knobs by "blue hand" are the same as CSS knob arrangements. Ableton probably names their "long names / scripting names" according to order.

John C
Forum Admin


I'm not entirely certain about how Max4Live Devices construct the order of their parameters but CSS simply uses the order they are served inside the api.
And regarding the Blue Hand, CSS doesn't use this due to the limitations it creates along with it - 8 params maximum.



Control Surface Studio User

long name seems to have a influence.. but its not really working on the octascenes.. like you can map parameter 1-8 more or less in order except 6... also sceneA and sceneB is not Next to each other..

to map this device seems impossible.. it's depressing.

(the file attached is actually a amxd file.. i just renamed it to txt to upload, you can vice versa)

upload files: 
Control Surface Studio User