posting this here since NORNS Help was closed.
(sorry if it’s not the right place)
i posted this under MANGL but it looks like i should post this here in NORNS HELP so i am moving it here.
my reference is with MANGL since i was was broadcasting last night but i will look at other scripts as well tonight.
i’m having the old MIDI control issue again where norns/MANGL will not respond to certain control assignments.
norns will (learn) the controller in the MIDI learn parameters page.
so i know it will see it.
just won’t react to it.
weird thing is…different MANGL tracks do not like certain CC numbers.
voice TWO volume on MANGL will not respond to CC 26 but it will with CC 27.
voice THREE volume on MANGL will not respond to CC 26, 27 or 32 but it will react to 8.
Delay send for ONE doesn’t like CC 9 but 8 will work.
this makes trying to control MANGL a bit of a rollercoaster.
TWO is controlled by fader 3.
THREE is controlled by knob 20.
Delay send for ONE is to the left of where it should be.
(you get the idea)
i did get a powered USB hub to alleviate USB connectivity on norns but this was happening before and after i added the hub.
tried a fresh start from SLEEP but it seems to be consistent.
hm… one thing is that if a mapping is created, and then the underlying set of parameters is changed (e.g. by an update), then the mappings will be off. (because under the hood, the target of a control mapping is a numerical index and is not aware of the actual name or “identity” of the parameter.)
so you might want to try clearing mapping files (.pmap) from the script’s location in ~/dust/data
but of course that doesn’t specifically address some problem where certain CC numbers are usable and others are not. that makes no sense at all to me (the CC number is just a byte value, nothing in the midi handling pipeline should be particular about it)