Here's the initial pre-alpha feature-incomplete use at your own risk don't know why I'm bothering release.
https://github.com/ratbag98/ndlr_control
Either clone the repo if you want to fork it (I won't insult your intelligence by offering instructions for that).
Or download the "NDLR CC Control.amxd" file here: https://github.com/ratbag98/ndlr_control...ntrol.amxd
The extremely skeletal instructions are on the site's wiki: https://github.com/ratbag98/ndlr_control/wiki
Double-clicking the amxd file once you've downloaded it should get it into Ableton. Then the wiki has instructions on how to configure MIDI - this is vital.
If nothing seems to work then make sure the "NDLR Panel" has sensible values (a valid port and channel, preferably not used by anything else) and mash the Retrieve button.
Key points to remember:
1. It's one way traffic other than when you click Retrieve. Ableton will send information to the NDLR but it won't get anything back unless you hit Retrieve. So the two interfaces can easily get out of sync if you keep using the controls on the NDLR itself.
2. Some of the controls don't work. See the thread in the NDLR Beta firmware channel for the whys and wherefores. I hope that a future firmware release will correct some of the CC inconsistencies.
3. Some of the controls can't work: the NDLR doesn't send CCs for things like the part activation buttons. So they appear empty on startup, even if on the NDLR itself they're all primed. After you've clicked Retrieve, click on the activation buttons in the Ableton interface to match the NDLR - from then on they'll be fine (see point 1 above though - if you press the physical buttons then the interfaces will drift again).
The best way to report bugs is via the Github Issues interface here: https://github.com/ratbag98/ndlr_control/issues, but I'll understand if you just want to put a comment here (I'll paste it into Issues as appropriate).
And finally... I got a Deluge last week and I seriously believe that this whole exercise wouldn't have been done if I'd had it originally! The Deluge + NDLR combo is killer and far more immediate (for me at least) than mousing around! But there will still be occasions when I want to do something more complex, and of course you can record the Ableton automation into the Deluge (I think, although I haven't tried), so it's still a useful tool that I will continue to improve.
See SynthDad's excellent tutorial for Deluge+NDLR: https://youtu.be/wvrFre6rM_k
And finally finally - still suffering with the dizziness, so apologies if I take a day or two per bug. I'm not ignoring you, honestly.
https://github.com/ratbag98/ndlr_control
Either clone the repo if you want to fork it (I won't insult your intelligence by offering instructions for that).
Or download the "NDLR CC Control.amxd" file here: https://github.com/ratbag98/ndlr_control...ntrol.amxd
The extremely skeletal instructions are on the site's wiki: https://github.com/ratbag98/ndlr_control/wiki
Double-clicking the amxd file once you've downloaded it should get it into Ableton. Then the wiki has instructions on how to configure MIDI - this is vital.
If nothing seems to work then make sure the "NDLR Panel" has sensible values (a valid port and channel, preferably not used by anything else) and mash the Retrieve button.
Key points to remember:
1. It's one way traffic other than when you click Retrieve. Ableton will send information to the NDLR but it won't get anything back unless you hit Retrieve. So the two interfaces can easily get out of sync if you keep using the controls on the NDLR itself.
2. Some of the controls don't work. See the thread in the NDLR Beta firmware channel for the whys and wherefores. I hope that a future firmware release will correct some of the CC inconsistencies.
3. Some of the controls can't work: the NDLR doesn't send CCs for things like the part activation buttons. So they appear empty on startup, even if on the NDLR itself they're all primed. After you've clicked Retrieve, click on the activation buttons in the Ableton interface to match the NDLR - from then on they'll be fine (see point 1 above though - if you press the physical buttons then the interfaces will drift again).
The best way to report bugs is via the Github Issues interface here: https://github.com/ratbag98/ndlr_control/issues, but I'll understand if you just want to put a comment here (I'll paste it into Issues as appropriate).
And finally... I got a Deluge last week and I seriously believe that this whole exercise wouldn't have been done if I'd had it originally! The Deluge + NDLR combo is killer and far more immediate (for me at least) than mousing around! But there will still be occasions when I want to do something more complex, and of course you can record the Ableton automation into the Deluge (I think, although I haven't tried), so it's still a useful tool that I will continue to improve.
See SynthDad's excellent tutorial for Deluge+NDLR: https://youtu.be/wvrFre6rM_k
And finally finally - still suffering with the dizziness, so apologies if I take a day or two per bug. I'm not ignoring you, honestly.