Skip to content

cleanup and update controller mappings info #743

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 2.5
Choose a base branch
from

Conversation

ronso0
Copy link
Member

@ronso0 ronso0 commented Mar 13, 2025

I don't think it makes sense anymore to mention the categories Mixxx Certified Mappings and Community Supported Mappings. The wiki page with these mappings isn't linked here, and it's not up-to-date.. at all.

We have built-in mappings and we mention the user mappings forum, that should suffice IMHO.
__
It's not required anymore to restart Mixxx in order to update the mapping list -- either select another mapping or close & reopen the Preferences does the trick.

Comment on lines -135 to -143
with a number of mappings for various devices. There are two levels of
controller mappings:

* **Mixxx Certified Mappings**: These mappings are verified by the Mixxx
Development Team.
* **Community Supported Mappings**: These mappings are provided and have been
verified as working by the Mixxx community, but the Mixxx Development Team is
unable to verify their quality because we don't have the devices ourselves.
They might have bugs or rough edges.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should mention that by default all mappings are essentially community supported mappings (or should be treated as such). Otherwise ppl may expect the "certified mappings" level support for all currently included mappings.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I understand.
If we don't make the distinction between certified and community-supported anymore (and the wiki page with that outdated table wasn't linked anyway), where would the 'certified' expectation come from?

I mean, even though built-in mappings vary greatly in terms of (code) quality, we don't have a quality rating or such for mappings, so if someone discovers issues we'll deal with it individually for each issue, don't we?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where would the 'certified' expectation come from?

From the fact that the mappings ship with mixxx instead of downloaded from some random source online. Compared with other DJ software, mappings shipped with a software are expected to be top notch (1st party support). That is not the case for us and I think we should make that clear. This text part previously made that clear by the official vs community supported distinction. Now that we remove the distinction, we should make clear that users should generally assume community support and not 1st party developer priority support. Does that make sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants