Midi mapping concepts?

[faeruithir]

Hi everyone,

I've been trying to create a good mapping for my korg padkontrol. But its really hard wrapping my head around that many controls, modifiers, and other things without any clear kind of guidance. Does anybody have any midi mapping concepts that they follow when making a mapping? Like...the less modifiers the better...or...1 deck per page...or...just any guiding concepts that you keep in mind when mapping

Thanks!

[Yul]

I usually think about what do my control allow: number and types of controls, number of midi channels and types of notes, all possibilities and limitations. I then think about the use of the controller I plan to have with. I then decide about the basic functions I need to implement, the ones I would like to have on it and then the funky stuff and extra bits that would be cool to get but I could live without in case.
I make a written plan. I also preview the theory of the modifier system I plan to use.I try to think about the practicality of it. I implement, I realize I make mistakes, I correct, etc, etc...
I usually start to map either the most basic things (basic controls, few modifiers) and then add the most complex parts. Or, I make separate little test mappings to check specific part for the mapping (leds, modifier functions usually).