I set my nanoKontrol buttons to be toggles (Light stays on until pressed again), and then midi mapped them to the arm tracks in Ableton. It takes two presses to make them respond. press twice, track is armed, twice more, track is unarmed. I know this is not delay because if I map the buttons in toggle mode to the track activator, there is no delay, and if I map them to the arm command when they are not set to be toggle buttons, there is no problem.
what is wrong?
NanoKontrol Toggle Buttons in Ableton
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
NanoKontrol Toggle have to push button twice issue [FIX]
This works with FL Studio 9 and NanoKontrol with built in Win 7 Driver (NOT KORG DRIVER for some reason...)
Its dicky as anything and should not have been this awkward to setup but heres how I managed to get it to work:
- In the kontrol editor, set the offending buttons to: CC, button behavior Toggle, "on value = 127" and "off value is 127"
(i found only some buttons were behaving like this - very random!)
- Log into your DAW/project. Assign your buttons to suit how you would like to trigger them. I have mine to mute/un-mute drum loops.
- Using your mouse turn all of your mapped controls off. (for example if you mapped a button on your controller to mute a drum loop on your DAW, click on the mute button with your mouse so all controllable parameters are in an "off" state.
-Save your projects state like this so each time you reopen it, everything will be turned off. (This sux but I have not tested enough to confirm if this will be required all the time... at this stage not willing to take the chance lol)
-Now when you open your project from now on, first make sure all the lights are off on your controller so when the project loads, everything is off to start with.
See how you go. Hope this helps you out to get back to making music!
[/list]
Its dicky as anything and should not have been this awkward to setup but heres how I managed to get it to work:
- In the kontrol editor, set the offending buttons to: CC, button behavior Toggle, "on value = 127" and "off value is 127"
(i found only some buttons were behaving like this - very random!)
- Log into your DAW/project. Assign your buttons to suit how you would like to trigger them. I have mine to mute/un-mute drum loops.
- Using your mouse turn all of your mapped controls off. (for example if you mapped a button on your controller to mute a drum loop on your DAW, click on the mute button with your mouse so all controllable parameters are in an "off" state.
-Save your projects state like this so each time you reopen it, everything will be turned off. (This sux but I have not tested enough to confirm if this will be required all the time... at this stage not willing to take the chance lol)
-Now when you open your project from now on, first make sure all the lights are off on your controller so when the project loads, everything is off to start with.
See how you go. Hope this helps you out to get back to making music!
[/list]