Most DJ controllers are designed for a certain use case, like i.e. a 4x2 button grid of a Reloop TerminalMix is mapped to control 4 hotcues and 4 samplers (like the labels on the device).
Naturally, those predetermined presets don't fit all use cases. Mixxx users can re-assign any control from within the Input Mapping GUI. But for example for the aforementioned Samplers/Hotcue grid this is tedious.
Also some settings need to be adjusted in included js files, which IMO is a barrier for users who just want to make music not 'to program'. I noticed this a few times with guys who are great when it's comes to music and music gear, but are unfamiliar with any kind of code and are therefore afraid to mess things up when editing js or xml files.
What about having a basic mapping file for a controller which can include various sub-mappings, i.e. to use a 4x2 grid for a) 8 Hotcues b) 8 samplers c) fixed-size loop buttons d) ...
In addition to the mapping description, the `Controller Setup` page could host radio buttons or drop-down menus for a few reasonable mapping alternatives to ease the remapping process for ALL users.
Another example for controllers with jogwheels:
Shift + wheel (touch &) turn could either toggle SlipMode or adjust the decks rate in 1-BPM steps.