MIXVIBES Dj Community old forum

Hello there,

I bought CrossDJ today and started mapping the controls to my MIDI controller (reloop beatmix). When I tried to map the pitch fader I observed a very strange behaviour. After mapping the fader "directly" it worked flawlessly for the first 5 seconds. After that the virtual fader just started to jump around, whenever I touched the physical fader.

Is this a known issue? Does anybody know what might cause such behaviour?

Thanks in advance

Okidoki_Sir wrote:Hello there,

I bought Cross DJ today and started mapping the controls to my MIDI controller (reloop beatmix). When I tried to map the pitch fader I observed a very strange behaviour. After mapping the fader "directly" it worked flawlessly for the first 5 seconds. After that the virtual fader just started to jump around, whenever I touched the physical fader.

Is this a known issue? Does anybody know what might cause such behaviour?

Thanks in advance

Please post your map file so I can examine it and determine if there is a correction needed.

It might be that your controller is doing wrong things. If you go to the MIDI tab in preferences you can test that when you provide a signal there is a flash in the screen. Just check if signals come in when your not using. If so it is a cable or controller issue. Just Maybe reinstall you're driver helps.

The tab is green for as long as I move the fader. When I stop, it is not green anymore. Here is the mapping:

<mapping>
<events>
<MIDI type="CC" parameter="0x76" channel="0x1"/>
</events>
<controls>
<control alias="fam(Player)[0x3].PitchValue"/>
</controls>
<preset name="Direct Fader/Knob">
<parameters>
<parameter object="action-0" key="action" value="SetNormalTakeOver"/>
<parameter object="dispatch" key="centerCCandPWvalueRange" value="64 64"/>
<parameter object="dispatch" key="useCenteredCCandPW" value="off"/>
<parameter object="invert" key="on" value="on"/>
</parameters>
</preset>
</mapping>

Okidoki_Sir wrote:The tab is green for as long as I move the fader. When I stop, it is not green anymore. Here is the mapping:

There is nothing wrong with the map code. At least you now is not that. As far as the green tab that is the normal indication. This seems to be a hardware problem. I would suggest to temporarily your pitch value command to the other fader to see if it is acting the same way. If it is not acting up with the same command you may have a defective fader.

The other Pitchfader reacts the very same way, regardless of what Player I map it to. The strangest thing is: I mapped the crossfader to set the pitch of Player 1 just to check if this works and even the crossfader jumped around, when used as Pitchfader. But when I properly map is at a crossfader it works flawlessly.

Well, I found a workaround now, I will just use the Jogwheels to increase/decrease the pitch. I don't scratch anyway. And maybe my problem will be solved with an update of CrossDJ or the driver

Have you tried enabling/disabling '14 bits' in the MIDI preferences?

i had a similar issue when making a map for my reloop terminal mix 4 (at that time, no official MV map was available for the tm4). it's set to 14bit, and i had to "catch" the upper side note, then manually change it in a text editor. after that, the pitch control moved smoothly

Sorry for the super late reply, but could you elaborate on this a little further? What did you "catch" and what did you change?

i'm basing this on what i went through with my denon sc-2900 mapping. this thread might help (issue resolved on page 2):

http://forum.mixvibes.com/viewtopic.php?f=358&t=25742&hilit=2900

in the mapping editor (and making sure that the 2900 was on 7 bits) i moved the pitch up and down. it's pretty hard to "catch" the proper value and clicking OK, so i took notes on what values appeared as i moved the control. after getting the values down, i saved the map at whatever value it had, then proceeded to use notepad++ to manually change the hex value i had noted (either the LSB or MSB value. one works, the other doesn't). saved the mapping file, reloaded it in Cross, and rechecked. whatever value works on one deck should work on the other.

let me know how it goes.