MIXVIBES Dj Community old forum

Hello everyone , sorry for the translation with google , start by doing a critique on the mapping file and led away on little documentation .
I Got a problem with various versions of Cross - DJ and I can not find solved :
1 ) when an active modifiers ( holder or toggler ) LEDs on the MIDI device is locked , if you enable + a modifier you go into confusion .
2 ) I am trying to map a DJ-tech mixer-one and I can not operate the LEDs of the VU- meter ( I lost a lot of time reading around and try )
3 ) always as an example , the mixer-one , if an active modifier on channel A and then step C , the buttons do not work neither led nor , I must return to deactivate the modifier A return to C and then it works .
I would like to know if there are solutions to the above, thanks .

tonip wrote:Hello everyone , sorry for the translation with google , start by doing a critique on the mapping file and led away on little documentation .
I Got a problem with various versions of Cross - DJ and I can not find solved :
1 ) when an active modifiers ( holder or toggler ) LEDs on the MIDI device is locked , if you enable + a modifier you go into confusion .
2 ) I am trying to map a DJ-tech mixer-one and I can not operate the LEDs of the VU- meter ( I lost a lot of time reading around and try )
3 ) always as an example , the mixer-one , if an active modifier on channel A and then step C , the buttons do not work neither led nor , I must return to deactivate the modifier A return to C and then it works .
I would like to know if there are solutions to the above, thanks .

When you do a basic map without modifiers the LED work all the time. However, when there is a modifier command you must specify all the conditions in which you want the LEDs to work.

For example

if you have to buttons and each sets a modifier condition say

Button 1 sets ML1 and button 2 sets ML2

Then if you want and LED to work all the time you must map the LED in the output session to cover the following conditions.

1. No modifier set
2. ML1 set
3. ML2 set
4. ML1 and ML2 set

You basically have to map each LED 4 times to cover all conditions in this example.

Below is a code example for a Play/pause LED that needs to work all the time regardless the set conditions of ML1 and ML2.

No condition set

<mapping>
<control alias="fam(Player)[0x1].PlayPause" value="true"/>
<MIDI type="Note" parameter="0x2" channel="0x1" value="127"/>
</mapping>
<mapping>
<control alias="fam(Player)[0x1].PlayPause" value="false"/>
<MIDI type="Note" parameter="0x2" channel="0x1" value="0"/>
</mapping>

Condition ML1 set

<mapping>
<control alias="fam(Player)[0x1].PlayPause" value="true" modifiers="ML1"/>
<MIDI type="Note" parameter="0x2" channel="0x1" value="127"/>
</mapping>
<mapping>
<control alias="fam(Player)[0x1].PlayPause" value="false" modifiers="ML1"/>
<MIDI type="Note" parameter="0x2" channel="0x1" value="0"/>
</mapping>

Condition ML2 set

<mapping>
<control alias="fam(Player)[0x1].PlayPause" value="true" modifiers="ML2"/>
<MIDI type="Note" parameter="0x2" channel="0x1" value="127"/>
</mapping>
<mapping>
<control alias="fam(Player)[0x1].PlayPause" value="false" modifiers="ML2"/>
<MIDI type="Note" parameter="0x2" channel="0x1" value="0"/>
</mapping>

Condition ML1 and ML2 set

<mapping>
<control alias="fam(Player)[0x1].PlayPause" value="true" modifiers="ML1, ML2"/>
<MIDI type="Note" parameter="0x2" channel="0x1" value="127"/>
</mapping>
<mapping>
<control alias="fam(Player)[0x1].PlayPause" value="false" modifiers="ML1, ML2"/>
<MIDI type="Note" parameter="0x2" channel="0x1" value="0"/>
</mapping>

Hope the above information helps you with the map.

hello,
The thing I ask is simple :
Active FX and the modifier ML1 to manage the functions of the filters , at the same time if there are flashing LEDs are locked , if I press other buttons(no modifier) , the corresponding LED will not turn on or turn off

tonip wrote:hello,
The thing I ask is simple :
Active FX and the modifier ML1 to manage the functions of the filters , at the same time if there are flashing LEDs are locked , if I press other buttons(no modifier) , the corresponding LED will not turn on or turn off

You have to add mapping command for when the ML1 condition is set.

Take the output section copy it to a separate file.
Add the ML1 modifier to every LED command.
Copy this back to the original file in the output section below your normal commands.

If you like you can post your map and will modify it to work.

Maybe we can not understand, I 'm saying that when a modifier is active locks all led MIDI device , for example, if a LED flashes with beatflah freezes, seems to me a bug setting of modifiers , I have the same problem with DJ - tech uSolo - fx player . you activate a modifier that does nothing and all the LEDs are blocked

I guess there are some challenges to overcome. First might be language; technical translations never are easy. Second is structure of a MIDI mapping File, Third technical problem.

1. What is you native language.
2. A MIDI mapping has 2 main sections. Input: A control (button etc.) is moved. The midi-code is send to the PC. The PC checks the mapping to understand what it has to do. Next the PC checks the Output section of the MIDI file. If there is info for that action it will read it and send the code to the controller.

What seems wrong now (as I understand) that if you press button A (e.g. Play) the light of an other LED is turned on (e.g. Cue). This means that the Output code for action Play needs to activate a different named LED.

What might be a good step is to upload your MIDI mapping file here (option at bottom when you reply. After upload please also use the "place inline" to actually put it in the post.
By doing this many misunderstand can be reduce by making it just a technical problem.

VU meters usually aren't the easiest; so let's not try to start with that. First basic on/off switching of LEDs should work.

Pretty sure it can be solved as MIDI is a standard for decades...

tonip wrote:Maybe we can not understand, I 'm saying that when a modifier is active locks all led MIDI device , for example, if a LED flashes with beatflah freezes, seems to me a bug setting of modifiers , I have the same problem with DJ - tech uSolo - fx player . you activate a modifier that does nothing and all the LEDs are blocked

I know. it is exactly what I am talking about.

For example. lets talk about just one LED and 1 modifier condition.

In a normal map without conditions your LED work like it is suposed to all the time. The map tell the hardaware how to act.

When you set a software modifier condition on, without modifying the map the LED does not know what to do so it remains either off or stuck. When the condition is turned of the LED resumes normal operation.

In order for LED to work correctly even when a condition is set, you must tell the LED how to act when the condition is set. Therefore
you must map the LED

1st map for no condition set.
2nd map for condition set.

That just for one condition. If you have 2 conditions say ML1 and ML2 then an LED must be mapped 4 times.

1. No condition set
2. ML1 set
3. ML2 set
4. ML1 and ML2 set.

Once again the solution to your problem is to add command for each LED to work for each condition it is not a bug just the way it works. Conditional mapping was introduced in version 2.4. I complained that conditional mapping in the output section should follow the same rules as conditional mapping in the input section but nothing has changed on that respect.

Are you telling me that if I have 10 bright buttons , each time an active modifier for works other than these buttons have to reconfigure all buttons for each modifier , it seems absurd

tonip wrote:Are you telling me that if I have 10 bright buttons , each time an active modifier for works other than these buttons have to reconfigure all buttons for each modifier , it seems absurd

You may think what you want. I am just trying to help you resolve the problem.

The functions on the buttons do not get affected unless they are only set to function within a modified layer. So there is no reconfiguring of the functions. However, the LEDs that are in the buttons do get their behavior affected by every modifier.

Once again the solution is to tell each LED how to properly behave for every modifier and modifier combination.

You may want to complaint about this to Mixvibes. Furthermore and for clarification, I don't work for Mixvibes. All Moderators are volunteer DJs that try to help other DJs by donating their time and sharing knowledge and tips.

You can still post your map and let me modify it. Once I am done you can test it and we can iron out any bugs together. Otherwise I already told you how to solve the problem.