American Audio VMS2

[dst]

Anybody have any mappings for this? Disappointed to see that there's none in my version of Mixxx.

[bestdani]

I read somewhere it should be almost compatible with the existing vms4 mapping. I'm quite unsure which controller I'm going to buy these days (just waiting for maybe winning one for free ) but the vms2 is an option for me. I wrote already midi scripts for controlling mixxx with my gamepad and joystick, so if I decide to buy a vms2, I'll write a mixxx mapping for it.

Maybe try the mapping wizard, should work for the important features, but also midi scripting is actually easy, particularly if you know something about programming / java script.

Off Topic:
Do you know if the vms2 has 10-bit midi pitch faders? I guess and hope it has, because the vms4 should have ones.

[Pegasus]

I did the current VMS4 mappings in v1.9.2 and 1.10.0. I'm curious to know how different the VMS2 is to the 4, so would you mind just loading up the VMS4 mapping and tell me what doesn't work? (Or what works if that list is shorter? )

[dst]

I'll do this soon..............I've gone over to the dark side of Virtual DJ (which I'm not totally digging, don't like their scrolling waveform). I did load up the VMS 4 mapping right after I opened the box, enough didn't work that I loaded up VDJ to get a better sense of the hardware.

As for the controller, I really like it as a step up from the entry level Numark I was using to see if I wanted to keep dj-ing digitally after only using vinyl. The lack of EQ kills is nearly fatal though.

[Pegasus]

You can use keyboard shortcuts for kills since the controller lacks them.

Yeah, when you get a chance, make sure you're using Mixxx 1.10.0, reload the VMS4 mapping from the drop-down, and let me know what doesn't work so we can try to fix it.

[BoLLiX]

Hello, I also recently purchased an AA VMS2 for use with Mixxx. I'm using the VMS4 mapping and here are the problems I'm encountering so far:

*Sometimes, the pitch controls will "stick" in Mixx (especially after using the Sync button). I'll move the sliders but nothing will happen. It seems to be fixed when I bring the slider close to where it is on the gui and play with it
*When hit the smaller CUE button, I imagine it would correspond to the headphone button in Mixx, but it doesn't. It does come out the headphones on the VMS2 with the Cue Mix knob set correctly. The volume on the deck in question has to be turned all the way down to keep it out of the main channel though (I mean, to the speakers).

Will update as I've only begun messing with it.

ED

*The track selector (knob and 4 arrow buttons around it) do nothing
* The left gain, high, mid, and low don't map to anything in the Mixx GUI yet does have an effect on the audio output
* The right gain, high, mid, and low knowbs map to the left in Mixx. Low and gain only work for mapping from the values 5 - 10 (from 0 - 10, 5 being middle/standard). This affects the sounds of both players left and right simultaneousls

[Pegasus]

The "sticking" controls is on purpose. It's called soft-takeover and prevents sudden jumps when the on-screen control is far from the physical control. (It can be disabled if you don't like it.)

Does the right channel's CUE button do anything? The VMS4 has the center two channels mapped (mixer channels 2 & 3 so I suspect that causes a problem on the VMS2. It should just be a matter of changing the <midino> value in the XML though. Run with --midiDebug to see what control number the button is.)

The VMS4 has no track selector, so I don't know how to map that without having one to test with.

The left gain, high, mid, and low don't map to anything in the Mixx GUI yet does have an effect on the audio output

Yes, you're affecting the internal mixer EQs so it will have an effect on the output, unless you have the unit in Pre-EQ mode. The fact that they don't do anything on screen is likely the same situation as for the CUE button. And the fact that the right controls map to the left deck in Mixxx confirms it. Simply changing the <midino> values in the XML file should straighten it out.

[Groschi]

My unit shoud arrive today and i'll try to get it mapped asap. Since i have no scripting experience i'll only be able to do a basic remapping and i won't fiddle around much with the script for now. But at least we'll have something to start with.

[Groschi]

So here it is. Actually there was very little to do, there are some things bugging me about it though. I only had to change the EQ, gain knobs and the channel faders; most other things seemed to work fine already. I didn't touch the scripts at all.

Things that don't work:
The jogs always operate in scratch mode. Switching to "nudge"-mode and back via the "vinyl"-button apparently isn't implemented in the VMS4-script.
Couldn't get the track navigation knob to work properly, so i left it and the four directional buttons unmapped.

You see, i really suck at this. But at least it (kind of) works.

*edit*
Oh, now i get it. The VMS4 jogwheels are touch sensitive on top and but not on the edges. The VMS2 ones are sensitive on the whole surface, so a way to switch modes would be really welcome. I guess it's also possible by manually adjusting the scripts a bit. Do you guys have an easy solution for this? The way it is now doesn't really suit my style.
Thx to all you guys.

[zestoi]

if you have any spare buttons, ideally with led's, then you could map one of those to a shift 'toggle' to enable/disable scratch mode. would need a tiny bit of scripting but i could help with that.

edit: i'm sure the mapping is basically doing what's described here http://mixxx.org/wiki/doku.php/midi_scripting#scratching but in your case you'd use a separate button for the scratch enable/disable function.