when i did it on OTC it was an easy change, but for ETC, it would also require C&G to create an ‘upgrade’ process (i don’t think this has been done before for etc!?)
… again not too difficult, and useful for the future.
(Id port the otc code over, but ive no way of testing it, nor developing the upgrader)
you will only ever get CC 21-24 from the MIDI port on the ETC, all other CC numbers are filtered out in firmware and cannot be changed (at least without taking the case off and using a programming cable)… MIDI over USB could do any CC, but isn’t supported on ETC without updating software.
This entry is modified. Modified or added text parts are marked in italics…:
I managed to use more MIDI controllers at least on my laptop testsystem. I still get an error if I try it on the ETC “Exception IndexError: ‘list index out of range’ in ‘liblo._callback’ ignored”. I assume on the laptop the function for checking the builtin knobs is ignored. On the ETC checking for 16 knobs fails, because there are only 5 real knobs.
You have to have SSH access to the ETC, then you can edit the various python files which sum up to the ETC program (and more important: you can make backups in case you fail editing…)
I simply extended the count of “knobs” to 16 (I use a Doepfer Pocket Control, which provides 16 controllers). Most changes are, that I extended the range of a “for…”-loop from 5 to 16. And sometimes individual settings for each knob are required.
Here is the diff-list for the files from /root/ETC_Mother/ which I edited (left file is the edited version, the right file is the regular version):
just to re-interate what owen said… ( as i understood it)
this will only work on the USB interface, not on the DIN (serial) interface as the STM controller filters others CCs
outside of this, id recommend doing as Ive done in OTC, and simply create a new CC array, where you store the last values - i don’t see much advantage of creating ‘virtual knobs’ , seems like more effort, and the resulting modes are no more/less compatible.