MIXVIBES Dj Community old forum

Hi all,

I have a VMS4.1 with Cross 2.0.1. All firmware is up to date in the VMS4.1 and with its ASIO.

I am using the preset mapping for the VMS4 that comes with Cross 2.0 as well.

If its a preset map for VMS4...shouldnt the jog wheels be working as well? Or is there something I'm missing to activate them?

The VMS4 mapping need a special firmware to work and won't work with the VMS 4.1

So as of right now,

There is no possible way to map the jog wheels for the VMS4.1?

Never had one in hands so I can't tell for sure, but the original VMS4 was sending weird messages from the jogs wheels that's why they have re-designed a firmware to have a better handling with Cross.

If the VMS4.1 is like the VMS4 before custom firmware, for me it is a big no.

Sweet!



Just uped to Cross too. Bummer.

Is there any talk of fixing the bug at all?

I love Cross. I dont wanna change software.

From Mixvibes side? There isn't that bug...

To outline Uncle's comment: There are standards for MIDI commands, how to use it, what to use, ... all the stuff, but standardized. Mixvibes is working with those standards, while some controller builder don't do so! Your problem is the best example for a company not sticking to these standards. It is a shame because what are those standards for then?

Hey.

I love...LOVE Mixvibes. I believe in the product and its team.

If nothing can be done about it...Nothing can be done about it.


This is the controller I have. I dont have the money for anything else.


I hope in the future things change so I can go back to using a great product. Thank you both for your help.

Ok, so for every companies that are doing everything out of the standard, we need to do a specific handling ?

For the VMS4 they have done a 'special' firmware for us and afterward they did (again) the same error on the VMS4.1.

Plug the controler into midiox and send me the messages from the jogs backward and forward.