I also mapped in an audio record button //Audio Record button Start/Stop Toggle MAP CH#0:15 CC#117 => CH#15,15,15,15,15,15,15,15,15,15,15,15,15,15,15,15 NON#23
Yeah, after getting a few mapping failures and looking at the examples I realized repeating the same number over and over would fill out the struct as expected
After looking at the code, I’d expect that the internal solution will be to expand out the mapping behind the scenes.
Any chance you could implement CH# CC# VAL# => CH# CC# VAL# while you are in that code? I was about to start looking around to see what I could do to add assignment.
OK! Mapping N=>1 is already implemented. I just commited …
Mapping 1=>N is more complex to implement, sorry. Implementing this is not easy with the current paradigm.
Same for this. The current paradigm doesn’t allow to make this easily. Sorry …
I did some digging around on my own and yes, there would be significant rework involved in getting this to work with value assignments. Ideally it would also support N=>1 value assignments.
If I can get a VM running zynth, I’d probably clone and start hacking around a bit more. I’m getting tired of messing up my rig. Finally got smart and cloned the SD card as a backup.
One more request/suggestion.
Any chance that the MIDI filter Rules could be changed to 1:16 rather than 0:15?
The 1:16 values are what are presented everywhere else MIDI is used.
Always a problem this one. Coders are going to prefer 0-15 users probably would prefer 1-16 and some of us change depending on the day and the weather.
Perhaps we could embed logic in the mapping parser?
=> is base 0
==> is base 1
It avoids the almost inevitable webconf midi base option, and would mean that cut and pasted settings would work consistently.
MIDI channel numbers should be presented 1-based (1-16) everywhere to users. zero-based indexing should only be within code. All user interfaces should be 1-16. Let’s make this consistent so that both coders and users don’t have to figure out what is happening at different parts of the interface.
I’m a coder, and a musician. In this case I just want it to match the “MIDI Channel” that is displayed on my keyboard controller when I’m writing rules… and this can wait. I’d rather have an official buster!