11-22-2020, 06:43 PM
(11-22-2020, 12:42 PM)House de Kris Wrote: I'd like to humbly request a couple minor changes to the CC#s that the NDLR responds to currently. This is actually a two-pronged request, and I realize I should probably split it into two separate threads for clarity, but I'm lazy - so please treat this as two separate and independent change requests.Hey Kris,
REQUEST 1:
I'd like to have another CC# added to control the Pause / Play aspect of all four parts, in one word. Currently there are four CC#s used, one for each part, with accepted values of 0-62 implying Pause and 63-127 resulting in Play. I'll skip the lengthy reasoning why this is difficult for me to integrate into my NDLR usage, but having one CC# for all parts would make it easier (for me). Use just the bottom four bits for control, and ignore the higher order bits. Perhaps something like:
Bit0 = Motif 1
Bit1 = Motif 2
Bit2 = Drone
Bit3 = Pads
Where, 0 = Pause and 1 = Play
This implies a 0-15 acceptable range, but if higher order bits are ignored, then the pattern of 16 valid codes repeats through the entire range of 0-127.
REQUEST 2:
I love the Modulation Matrix, but I'm disappointed that there just aren't enough sources. I'm not requesting more LFOs or preset modulators, but rather a path for user supplied external oscillators to be used as sources. Very similar to the MIDI inputs, but more of them and with a consistent usage pattern. Therefore, I propose using a block of eight CC#s from 100 to 107 as sources for the Modulation Matrix. My justification for this request stems from my past usage of an Alesis MMT-8 sequencer as an octal MIDI-sync'ed LFO generator. This would give a greater frequency range, wave shapes, phase relationships than the ones included in the stock NDLR.
SUGGESTIONS TO FULFILL REQUESTS:
I made a chart showing the CC#s as defined in the NDLR currently, and suggested changes to realize the two separate requests of this post, see attached.
This chart displays all 128 possible CC#s and NDLR uses, in addition to standard MIDI definitions of common or reserved CC#s. The vertical columns are (from left to right):
CC# - the CC#
Resr - Reserved
Genl - General use functions of NDLR
Mot1 - Motif 1 specific functions in NDLR
Mot2 - Motif 2 specific functions in NDLR
Dron - Drone specific functions in NDLR
Pads - Pads specific functions in NDLR
Prop - Proposed new functions in this request
RANGE - Indicates allowable values that are recognized per CC#
TARGET - A brief description of the CC# function
The dashes under Resr, Genl, Mot1, Mot2, Dron, and Pads visually show how each CC# is used. Periods are used in those fields for the proposed changes, which are designated with YYYY and XXXX in the Prop column (differentiating the two different requests).
I hope this makes sense. If any clarification is needed, please ask. I also hope that the level of effort in making this request gives a hint as to how much I'd appreciate having these features added.
Thanks,
House de Kris
This is definitely the most thoroughly documented feature request I've come across. I'll be sure to pass this along to Steve and see what he thinks.
My two cents is that it seems a little bit fiddly to use the bit values of one channel for the Play/Pause, rather than individual on off CCs. I can see it being really hard to use for people with a MIDI controller slider or knob, no? It would seem to be simpler to just add a CC, I could see that working more predictably anyway.
I don't imagine any major expansions of the ModMatrix are likely but I will for sure run it by the man and see what he thinks. I do see how that would be pretty neat.
Thanks for taking the time to present these ideas, your feedback has always been top notch. I can't say whether or not they get implemented but I imagine we will have more time to look at these in March after the MRCC is launched.
Best,
Jesse