MIXVIBES Dj Community old forum

Hi,

I'm trying to map my Xone X on Windows 7 but have some problems I don't realy find an answer for with the search option on this forum:

1)
The DX has a boot monitor output. In the audio configuration file I can set 4 outputs but in internal mixing "dual stereo" only the first (master) and the second (headphones) are connected. How can I modify this to get the sound also to the boot monitor output and controlled with the boot volume knob (cc21 on channel 12)

2)
The layout of the DX is 1-red, 2-green on the left and 3-red, 4-green on the richt side. The mixer in CrossDJ however is setup as CABD.
I changed the mapping so I can control player A with slider 1 and C withe slider 2 (ACBD config) but in the display when I move slider 1, the second slider moves (same for bass-mid-hi-gain and filter ofcourse). This is verry confusing when I would take the software to play in public and things get stressy. I could change the mapping and put some tape over the 1234 but than the green and red indicators would still be opposite from the left on the right. Again confusing and guaranteed to get it wrong more than once when getting tired/stressed. How can this be changed so that the display gets me ACBD sliders on the screen?

3)
The cue LED on channel 1 and 4 are constantly lid in orange, when pressing the cue button on channel 1 it turns red, on channel 2 the button doesn't do anything, on channel 3 the cue button lights the led of channel 4 in red and the cue button on channel 4 doesn't change any lights. The signal is sent to the headphone for the right channel.
I understand that I can modify these leds by editing some file but am a bit confused by where to find this file and how to get the led's right.

I bought CrossDJ as it had support/mapping for my Xone:DX but found that this mapping is only half work, so please help me with getting it complete as I have gigs to play soon. As soon as I have a good mapping working I'll post it on the forum for other members!

I love the simple and powerfull interface of crossDJ but no boot monitor output and the confusing channel line up are almost showstoppers.

I hope things can work out

jimmy

MrKite wrote:1)
The DX has a boot monitor output. In the audio configuration file I can set 4 outputs but in internal mixing "dual stereo" only the first (master) and the second (headphones) are connected. How can I modify this to get the sound also to the boot monitor output and controlled with the boot volume knob (cc21 on channel 12)

Cross don't have a booth output, unless your soundcard can handle this as an hardware mixer (what it doesn't), it won't be possible.

2)
The layout of the DX is 1-red, 2-green on the left and 3-red, 4-green on the richt side. The mixer in CrossDJ however is setup as CABD.
I changed the mapping so I can control player A with slider 1 and C withe slider 2 (ACBD config) but in the display when I move slider 1, the second slider moves (same for bass-mid-hi-gain and filter ofcourse). This is verry confusing when I would take the software to play in public and things get stressy. I could change the mapping and put some tape over the 1234 but than the green and red indicators would still be opposite from the left on the right. Again confusing and guaranteed to get it wrong more than once when getting tired/stressed. How can this be changed so that the display gets me ACBD sliders on the screen?

CABD is becoming the standard 4 decks layouts this is nothing weird and we cannot modify this into the software by option/preferences.

3) The cue LED on channel 1 and 4 are constantly lid in orange, when pressing the cue button on channel 1 it turns red, on channel 2 the button doesn't do anything, on channel 3 the cue button lights the led of channel 4 in red and the cue button on channel 4 doesn't change any lights. The signal is sent to the headphone for the right channel.

I guess the lights are handled by the hardware, so you need to override it with the software if is allowed.

I understand that I can modify these leds by editing some file but am a bit confused by where to find this file and how to get the led's right.

This need some xml knowledge and understanding of MIDI coding.

I bought CrossDJ as it had support/mapping for my Xone:DX but found that this mapping is only half work, so please help me with getting it complete as I have gigs to play soon. As soon as I have a good mapping working I'll post it on the forum for other members!

The story is that when it has been mapped Cross was half of what it is now. You can see the version number into the mapping for the DX and it is 1.50

I love the simple and powerfull interface of CrossDJ but no boot monitor output and the confusing channel line up are almost showstoppers.

CABD instead of ABCD shouldn't be that hard to integrate. Unfortunately I don't have any DX there anymore to help you on these.

Hi,

I am working on an update for the xone DX mappings for 4 decks and I think I'm almost there for having a working version. I mapped them to be able to use the 4 decks on a gig this friday, so no library or editing functions have been mapped, just controlling the decks and the effects will have to do for now.

for my earlier questions:

The boot monitor problem I can solve for now by taking a link through from my speakers back to the monitors. This requires more cables but ok for now. For future releases this will for sure be on the wish list as any pro equipment has boot outputs.

For the CABD layout, I'm remapping my brain as red lights are in the middle, green on the outside. Still needs some more practice before this is embedded in my brain (changing habits takes time) but I'll get there.

I'm still strugling with the VU meters and would like some help.

I have the meters working for channel A and B but C and D stay dead:

<mapping>
<control alias="fam(Mixer).PlayerAMeter" value="%"/>
<MIDI type="CC" parameter="0x4" channel="0xc" value="%"/>
</mapping>
<mapping>
<control alias="fam(Mixer).PlayerBMeter" value="%"/>
<MIDI type="CC" parameter="0x7" channel="0xc" value="%"/>
</mapping>
<mapping>
<control alias="fam(Mixer).PlayerCMeter" value="%"/>
<MIDI type="CC" parameter="0x11" channel="0xc" value="%"/>
</mapping>
<mapping>
<control alias="fam(Mixer).PlayerDMeter" value="%"/>
<MIDI type="CC" parameter="0x19" channel="0xc" value="%"/>
</mapping>
</output-mappings>
</mappings>
</controller>
</main>

however, when I put the parameter and channel values all on PlayerAMeter and PlayerBmeter, all 4 channel meters are working so I have the parameters right (this was the test coding:)

<mapping>
<control alias="fam(Mixer).PlayerAMeter" value="%"/>
<MIDI type="CC" parameter="0x4" channel="0xc" value="%"/>
<MIDI type="CC" parameter="0x11" channel="0xc" value="%"/>
</mapping>
<mapping>
<control alias="fam(Mixer).PlayerBMeter" value="%"/>
<MIDI type="CC" parameter="0x7" channel="0xc" value="%"/>
<MIDI type="CC" parameter="0x19" channel="0xc" value="%"/>
</mapping>

Ofcourse the lights of channel C are moving to the sound of channel A but it was just checking for the right parameters.
Could you help me with defining the channel meters for C and D?
My mapping for 2.4 is in attachment.

Second, when I open the history, there are all the songs I played in channel A and B but none for players C and D! Could this be a bug in 2.4 ?

Thanks for your help

jimmy

The ouput aliases for vu-meters are:
ChannelAMeter
ChannelBMeter
ChannelCMeter
ChannelDMeter

You're using deprecated ones (working only for A & B for those who have very old mappings).

Thanks for the fast support, I'll try it out ASAP.

Hope you'll find the answer to the history problem also fast.

Jimmy

MrKite wrote:The boot monitor problem I can solve for now by taking a link through from my speakers back to the monitors. This requires more cables but ok for now. For future releases this will for sure be on the wish list as any pro equipment has boot outputs

Yes but some of them are hardware and handled by the soundcard directly.

Second, when I open the history, there are all the songs I played in channel A and B but none for players C and D! Could this be a bug in 2.4 ?

Nice find !