This is an old revision of the document!
Status: This specification is in drafting. Please feel free to edit this page and add your comments. Mixxx currently supports a wide-range of hardware MIDI controllers that DJs can use to perform with. Each supported MIDI controller has a “mapping” file that is bundled with Mixxx, but this mapping must be manually selected by the user before their controller works.
The aim of this project is to increase the usability for new users by automatically selecting the correct MIDI mapping and to provide an intelligent workflow for when an unsupported MIDI device is connected. And when a mapping for a MIDI device is not present, the user should not be left out in the cold. She should have the option of connecting to mixxx.org to see if there are any official or user-contributed mappings available for download.
When a controller is plugged in and the user needs to do some configurations automatically or manually.Current version Mixxx provide a semiautomatic way, i.e. if there are mapping files in local library, Mixxx will load it during the initialization, if not, Mixxx will do nothing and users have to select a right preset mapping file from a drop-down list or even build mapping files by themselves.This is a little hard to some initial users, so a new small feature will be a user-friendly design if Mixxx can automitically search local library backend and list the match results for user.
Once a local mapping file isn’t searched during the initialization, Mixxx will give a notice message box to user, such as “Sorry,Mixxx cann’t select a perfect mapping for you from local library, you can go to Preferences→Controller widget to get a right one by yourself through our ‘Mapping Preset Manager’”.
If Mixxx load a preset for the devices at the beginning, the result will be showed on ‘dlgprefcontrollerdlg.ui’ just like the current version. A few changes to ‘dlgprefcontrollerdlg.ui’, see Fig.1.
Mixxx can not do an automical map or an perfect map from local library at the beginning, so users need to choose one by themselves.Mapping files needed by user may exist in local or website, we’d better provide an API for user to query both local and cloud depository.Most users are not very sure which one to choose, so we’d better make an intelligent recommendation for users, especially for novice users, to reduce the sense of fear of using mixxx at the beginning. At the same time, it is also very convenience.A mapping file has been downloaded into local library, but maybe it has some bugs or is not that perfect. And there is a new update version on the mixxx forum or somewhere, so when users try to apply a local preset in the case of network connected, we’d better to advice users to update to a new version of preset.
Here I think we can create a new feature called “Mapping Files Manager”, with the following functions: