Mode Selector LED settings sometimes appear, sometimes don’t

Hi John,

I’m trying to create a script for my Korg nanoKONTROL2. It’s based on djpaimon’s korg_nanokontrol2.json controller template and has 11 modes… 5 primary ‘a’ modes, a shift mode, and 5 secondary ‘b’ modes.

So far, I’ve gotten the functionality working how I want and /mostly/ the correct LEDs come on when the respective mode is active. The exception being the button I’m using to shift between the ‘a’ and ‘b’ sets, which I want to be lit whenever a ‘b’ mode is active. *Finding a fix is out of scope for this post* (though all help gratefully received! suffice it to say, I’ve read your blog post and watched the YT tutorial) but I’m finding it hit and miss in terms of changing LED settings. In that…

Bug?: Mode Selector LED settings sometimes appear, sometimes not

You’ll see what I mean in this video (sorry for low res, I’m running low on space, but you’ll see enough to get the gist of the issue) – https://www.dropbox.com/s/av7wus7rwqg8ub5/CSS_ModeSelectors_LEDsettings….

In this screen recording, I navigate down the script hierarchy selecting Mode Selectors. Keep an eye on two things:
1) Any Mode Selector mapping name ending in ‘LED’ is a Mode Selector for which I’ve already applied an LED setting, but currently the setting is not visible in the GUI
2) Mode Selector mapping names not ending in LED are either not needing a bespoke setting; or, as you’ll see, I finally manage to change them as the setting appears (ie: I was doing this yesterday and the LED settings were missing, but now they appear!)

Hope this makes sense? Controller Template and Script attached

Right… I should now try and discern why Mode 5b is correctly lighting buttons 3 and 7, whilst the other ‘b’ modes are not lighting button 3.

Cheers
Jus