i renctly got an rmx used from a friend. he said he was having problems with the pitch slider of deck a being controlled by th eq low knob. i tried to remap the controls but it still doesnt work. i have updated all the drivers and im using it with virtual dj pro 7. i cant seem to figure out how to undo this mapping configuration.
On the Virtual DJ MAPPER tab (Configuration menu), simply click on the "CD" ison at the bottom left of the page to reload the default mapping.
If you want to verify if the Rmx is working correctly as a MIDI controller, you can use the following procedure:
I tried that Phatso. I re-set to factory default and it still didn't work. Will the test to verify if the RMX is working correctly allow me to repair problems? Can I use it to re-map the controller?
I used MIDI Monitor to see if the RMX was working correctly as a MIDI controller, it was not. I saw general purpose control mesages when I move the pitch slider on deck "A", not the same pitch controller messages that I get when moving the other pitch slider. I'm not sure how to fix this problem. When I turn the EQ Low knob on the "B" deck, it changes the pitch of "A" deck. When I move the hardware fader on the RMX "A" deck there is no change in pitch. I've tried re-setting to factory default settings and nothing has worked.
On the Virtual DJ MAPPER tab (Configuration menu), simply click on the "CD" ison at the bottom left of the page to reload the default mapping.
If you want to verify if the Rmx is working correctly as a MIDI controller, you can use the following procedure:
http://ts.hercules.com/faqs/eng/her_eng_00353.pdf/blockquote >
This link sent me to a site where the download link doesn't work.
So let's resume here:
- Testing the Rmx outside of VDJ using MIDI monitor, are all controls sending different data ?
They should. If this is not the case, then there is a problem.
The Deck A Pitch should be Gen Purp 2, while Deck B is Control 59.
Deck A EQ Low is Control 54 while for Deck B it is Hold 1
If this is all correct, then the hardware is fine and the problem is obviously related to VDJ.
- Did you ever install any add-ons (plugins, mappers, etc) that could potentially have an influence on the controller behavior ?
- Are you using the latest version (7.05) ?
- Have you tried a complete uninstall and reinstall of VDJ ?
