Fader 5 not showing information on screen only in daw mode

Lab KeyLab
#1

Hi

Recently became aware of this bug where the fader 5, corresponding to macro 13 in daw mode, does not show any information on screen. Although it works perfect in every other template, arturia mode or user´s.

So i´m guessing it is a daw scrypt issue?

#2

Could you give us a hint what DAW you are talking about? That could be helpful.

#3

Ableton Live 12

#4

And what device is active on the track? AFAIK, the faders are mapped to some default controls depending on the device — or to the macro knobs if you i.e. use an instrument rack.

#5

Ah … and what mode is active? Mixer or device?

#6

I have noticed the bug when controlling an instrument rack, it happens with audio effect rack too. And in both modes, mixer or device. The fader works properly, i can control the things that are mapped to it, but the information does not show on screen.

I have also noticed that when i push any fader that shows information on screen, ableton´s midi signal monitor shows both orange and cyan lights, but when i push the fader that doesnt show information it only gives an orange light (i was trying to attach images of this but im a new user so i cant :frowning: )

#7

Okay … I will try this later when I am back in my studio.

#8

Sorry, but I cannot replicate this with the currently released version of Live (12.1.11) and the latest firmware.

But maybe someone else has this issue, too?

#9

Same Issue here.
Fader 5 is not reviewing midi information back from ableton .
Its a bug in the ableton control script.
Would be nice if it can be fixed

#10

I just noticed this too.

Ableton 12 DAW Mixer mode.
Fader 5 does move Vol in ABE but does not give feedback in KL screen.
All other Faders are fine.
Dang. Has this been happening for 6mths+ and the last update missed it? Oh dear…

#11

Encourage others to check this and send a note to Tech if so.
Arturia may need numbers to action things qucker. :muscle:

#12

In Logic, the script doesn’t have mapped fader return values, but it’s doable in the controller assignments.
I suppose you can do it manually in Ableton too.

No script is truly finished; event it take fews minutes to correct it…
these should have been urgent updates. its a shame

But apparently, we have to be happy with the sustain pedal working now and thats it.

For a year now, Arturia has solved quite a few problems for the various DAWs, but hasn’t released the fixes… Arturia just doesnt care…

#13

I contacted support about six weeks ago. It took several emails before they finally said, yes, the error is known.
As Ben972 already mentioned, this is actually a minor issue that could be fixed very quickly. It has nothing to do with the update i think. Perhaps someone at Arturia could quickly add the missing parameter to the Ableton Control script. It would take 10 minutes and make many customers from the Keylab happier than before.