American Audio VMS2 mappings broken

[Mel Grubb]

I the 1.12 beta, i can't seem to use either of the VMS2 mappings. It's working just fine for me in 1.11, using the "Alternative" mapping at the moment, but in 1.12, one mapping has working jog wheels, but the cue/play/pause buttons don't do anything. In the other mapping, they do exactly the opposite. Neither mapping in 1.12 seems to include the center "search" knob.

[Stefan Nürnberger (kabelfrickler)]

I'm the author of the "Alternative" mapping. Unfortunately I gave my AA VMS2 to a friend, lately. So I currently can't test with 1.12. But he should be experiencing the same issues soon. I'll contact him.

Actually since 1.12 supports 4 decks now, I wanted to change the following:
- Play/Pause should be mapped to the Play Button (toggle mode) but I think it already is.
- The Pause Button should be used to switch Decks 1/3 & 2/4

Do the jog wheels work for you in the alternative mapping?
Center search knob should also work. Pressing it (it's also a button) toggles between side bar and main window scrolling.

Are you on Linux? I had some issues with device detection. The VMS2 actually shows up twice now for me. I had to activate both. My distribution is Debian so Ubuntu is probably also affected.

[Stefan Nürnberger (kabelfrickler)]

Also when I finally get to it, I should rework the Vinyl/Scratch-Mode to just toggle on every press of the vinyl button. My unit was missing the rubber rings for the jog wheels.

[Stefan Nürnberger (kabelfrickler)]

I tested and verified the "Alternative" mapping to work on the release-2.0.0 git tag and current git master with Linux. The included mapping has some invalid controls, which Mixxx warns about. However, it does not inhibit functionality. All buttons work the same as they did in 1.11.

The VMS2 is now listed twice in controller selection, once as "HID" and one "MIDI" device. Only the MIDI device needs to be activated for me. My VMS2 USB device ID is "04d8:0a0b Microchip Technology, Inc."

@Mel Grubb can you try to temporarily remove your mapping settings (the contents of directory ".mixxx/controllers" on Linux, but *do a backup* if you edited any mapping by yourself) and restart Mixxx. Then load the mapping again using the controller configuration menu. If the problem persists, try to start Mixxx with the "--midiDebug" commandline option (from a command line, so you can see debug output), and see if the controller does indeed send MIDI requests.

Regarding the "they do exactly the opposite", the [PLAY] button is a play/pause toggle. The [PAUSE] button does pause, but is redundant from that perspective. This is why remapping it to a deck switch would actually be awesome.

I just filed a pull request against master with an updated mapping. It is not 4-deck, yet but improves the mapping in quite some areas. The pull request is here: https://github.com/mixxxdj/mixxx/pull/876

From my perspective the bug can be closed as any of "Cannot reproduce" / "Works for me" / "Need info". Thanks for reporting, though. It got me to finally update this mapping.

[Mel Grubb (melgrubb)]

I don't have that controller available anymore, so I can't verify the mapping now, unfortunately.

[Stefan Nürnberger (kabelfrickler)]

FWIW I tested the controller with a fresh Mixxx 2.0.0 install on Windows 10 x64. The "Alternative" mapping worked fine for me.

[Swiftb0y (swiftb0y)]

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