crossfade assign loves to be at 127

Submitted by ananaphone on Sun, 05/13/2018 - 06:14
Pro User
So the crossfade assign has 3 positions for which Ableton returns the following CC values: no assign: 4, yes 4 for some reason A: 127 B: 127 The issue that I'm having is that the A and B values are the same so they adjust the controls on my Lemur in such a way that I can't tell the difference between A and B. The best I can do is to tell that an assignment has been selected, but I don't know which one. In contrast, a midi mapping in Ableton divides the CC message's range into 3 parts, so if you had let's 3 radio buttons, you could set them to send the values 0, 64, 127 all to the same CC. Not sure how to proceed. Another point of interest is that when the knob is sending messages to Ableton, the crossfade assign rapidly cycles through the three options. So as I slowly move my finger up the range, the A/B assign in Ableton will flicker wildly as it moves from A to B to Off and back to A. I set the knob to send only midi values from 1 to 10 to see if I could see the pattern of the cycle. Strangely, the cycle is the same no matter which way I turn the knob. It always goes A, B, Off, whether I turn the knob up or down. -A

3 Responses


John Carney
Forum Admin
Hi, Have you tried the different Encoder Type options in the mapping settings? Maybe 'relative smooth two compliment' or one of the others would work better. John
Pro User

Best using Midi Note Type for X-fader assign. Note type toggles between A,B and None.

Hawn Solo
Pro User

I was going to say the same thing as Simsonatic. For example I have a button outputting a note that can display multiple LED colors, it is designated for A/B assign of the selected track and it shows no color (or is off) when nothing is selected, yellow when A is selected, and pink when B is selected (closest I could get to orange with my controller).

You might be able to do something similar with Lemur for your A/B assign controls and it should work better than an knob type control.