No way to automatically map jog wheels in midi wizard

[Owen Williams]

jog wheels are hard, but right now they are totally absent from the midi learning wizard. We should add them!

[jus (jus)]

Safe to say this is a biggie.

[Owen Williams (ywwg)]

Ugh, who can do this? I just wrote the bit of the manual that says we don't support this :(

[RJ Skerry-Ryan (rryan)]

This is on my plate for today or this weekend!

On Thu, Nov 27, 2014, 1:30 PM Owen Williams <email address hidden> wrote:

> Ugh, who can do this? I just wrote the bit of the manual that says we
> don't support this :(
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/1371387
>
> Title:
> No way to automatically map jog wheels in midi wizard
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/1371387/+subscriptions
>

[Owen Williams (ywwg)]

This came up again in the mixxx facebook page. The lack of midi-learn support for jog wheels is an issue.

It may require more work, but maybe we can write some intelligent code that works with several different controllers out of the box? Having mapped a bunch of controllers, there's a commonality to how they work, it's just the details of the various coefficients that needs to be tweaked.

[Sean M. Pappalardo (pegasus-renegadetech)]

This is on my radar. I have a plan in my mind on how to systematically ask the user to do a few simple things and have Mixxx read the resulting controller messages (MIDI and HID alike) to determine the wheel type and resolution so we can automatically create the appropriate mappings. Would it be helpful for me to spell that plan out in a blueprint/wiki page or just spend the time implementing it?

[Owen Williams (ywwg)]

from a UX perspective, it could be something like:

1. rotate the wheel one revolution in one direction: figure out sensitivity
2. move the wheel back and forth gently: figure out positive vs negative
3. scratch the wheel back and forth rapidly: further refinement for scratching?
4. touch the wheel: look for wheel-touch signals, report if none detected

[RJ Skerry-Ryan (rryan)]

Please make sure to implement this within the code that already exists for detecting what type of control something is:
https://github.com/mixxxdj/mixxx/blob/master/src/controllers/learningutils.cpp

(I wrote that with an eye towards auto-detecting the type of a jogwheel.)

[Owen Williams (ywwg)]

If you can do a design, that would be really nice! I and/or RJ can do a basic design checkup to make sure it'll fit in well with the code that we already have. But if we can get something that produces satisfactory results for a bunch of different controllers, that'll be a huge win. (Controller configs are still our #1 feature request, if you aggregate all the different controllers together)

[Marzena Ziomalka (marzimala1)]

I could really use mapping jog wheels in the learning wizard because I can't understand .js files
And such a mapping in 4 steps as above would be very desirable.
I would only add in point 1 to make two or three turns for a more reliable reading of the resolution of the circles.
By the way, a mapping in the learning wizard would also be useful for loop encoders. Which are rotatable with push.
Best regards.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/7584