Page 15 of 16

Re: Cross MIDI output mapping

PostPosted: 10 Feb 2015, 09:49
by ddjj
Here is the list of the IN and OUT aliases (updated for 3.0)

Re: Cross MIDI output mapping

PostPosted: 14 Aug 2015, 17:00
by haga46
Hey there,

I've read the topic 3 times before trying to map but can't get it to work so where does it go wrong :mrgreen: I've tried a few different things but the outcome is the same.
My controller is a reloop beatmix2 ;)

The only things that work correct are the hotcue's all the rest seems to be a mess :rolleyes:

The controller isn't fully mapped but before getting it all mapped i wanted to see if i could manage the outputs :cool:

BeatMix2(Reloop)led test - 3.mappings


Thanks in advance J

Re: Cross MIDI output mapping

PostPosted: 25 Feb 2016, 21:43
by FigDJ
Team Mixvibes

Could someone explain what is this output. Could it be related to the circle indicator for each deck? If so can it then be used to light up LEDs around a jog Wheel?


Out fam(Player)[0x1].DelayWithMaster (Normal) == "Delay with Master"

Re: Cross MIDI output mapping

PostPosted: 31 Jan 2018, 22:51
by baniakrulez
Could someone write me a output script for this input command so I can understand on how to write led out commands for other inputs. I want to map Kontrol Z2.

thats my input command for Cue point locator 1 with CC7 note
<mapping name="Cue 1">
<events>
<MIDI type="CC" parameter="0x7" channel="0x4"/>
</events>
<controls>
<control alias="fam(Player)[0x1].Locator1Control"/>
</controls>
<preset name="Logic Fader/Knob">
<parameters>
<parameter object="invert" key="on" value="off"/>
<parameter object="range" key="range begin" value="0"/>
<parameter object="range" key="range end" value="1"/>
</parameters>
</preset>
</mapping>
</input-mappings>

Re: Cross MIDI output mapping

PostPosted: 31 Jan 2018, 22:51
by baniakrulez
Could someone write me a output script for this input command so I can understand on how to write led out commands for other inputs. I want to map Kontrol Z2.

thats my input command for Cue point locator 1 with CC7 note
<mapping name="Cue 1">
<events>
<MIDI type="CC" parameter="0x7" channel="0x4"/>
</events>
<controls>
<control alias="fam(Player)[0x1].Locator1Control"/>
</controls>
<preset name="Logic Fader/Knob">
<parameters>
<parameter object="invert" key="on" value="off"/>
<parameter object="range" key="range begin" value="0"/>
<parameter object="range" key="range end" value="1"/>
</parameters>
</preset>
</mapping>
</input-mappings>

Re: Cross MIDI output mapping

PostPosted: 01 Feb 2018, 17:13
by FigDJ
OK this is your command below
Code: Select all
        <mapping name="Cue 1">
          <events>
            <MIDI type="cc" parameter="0x7" channel="0x4"/>
          </events>
          <controls>
            <control alias="fam(Player)[0x1].Locator1Control"/>
          </controls>
          <preset name="Logic Fader/KnobHolder Button">
           <parameters>
            <parameter object="range" key="range begin" value="0"/>
            <parameter object="range" key="range end" value="1"/>
           </parameters>
          </preset>
        </mapping>

Normally cue button are map as Holder button so it would look
like this using note or cc depending on your controller. Normally Cross would detect if it is note or cc using the MIDI learn feature.

Note Example
Code: Select all
        <mapping name="Cue 1">
          <events>
            <MIDI type="Note" parameter="0x7" channel="0x4"/>
          </events>
          <controls>
            <control alias="fam(Player)[0x1].Locator1Control"/>
          </controls>
          <preset name="Holder Button">
            <parameters>
              <parameter object="invert" key="on" value="off"/>
            </parameters>
          </preset>
        </mapping>

CC Example
Code: Select all
        <mapping name="Cue 1">
          <events>
            <MIDI type="cc" parameter="0x7" channel="0x4"/>
          </events>
          <controls>
            <control alias="fam(Player)[0x1].Locator1Control"/>
          </controls>
          <preset name="Logic Fader/KnobHolder Button">
           <parameters>
            <parameter object="range" key="range begin" value="0"/>
            <parameter object="range" key="range end" value="1"/>
           </parameters>
          </preset>
        </mapping>

you go this

Now a little info on input and output commands.
Code: Select all
    <mappings>
      <input-mappings>
************************** All your input commands go here
      </input-mappings>
************************** You must create the output section
      <output-mappings>
************************** All your output(led) commands go here
************************** You must close the output section
      </output-mappings>
************************** You must close the mappings
    </mappings>
************************** You must close the controller
  </controller>
************************** You must close the file
</main>

Now an example of the led mapping in the output section
Code: Select all
        <mapping>
          <control alias="fam(Player)[0x1].Locator1Control" value="true"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="127"/>
        </mapping>
        <mapping>
          <control alias="fam(Player)[0x1].Locator1Control" value="false"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="0"/>
        </mapping>

You must map 2 conditions for each led contition on and condition off
The above example uses value 127 for on and 0 for off.
The value of the on condition determines the intensity.

However, on controllers that have have rgb leds the value of the
on condition determines the color.

The off condition value is always 0.
In addition if you want the led to be reactive to when you set, turn off or set a loop you must also map the condition for each in the output section.
As follows
Code: Select all
        <mapping>
          <control alias="fam(Player)[0x1].Locator1KindControl" value="0"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="0"/>
        </mapping>
        <mapping>
          <control alias="fam(Player)[0x1].Locator1KindControl" value="1"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="127"/>
        </mapping>
        <mapping>
          <control alias="fam(Player)[0x1].Locator1KindControl" value="2"/>
          <MIDI loop="true"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="127" duration="500"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="0" duration="500"/>
        </mapping>

This set condition for on, off and blink when it is a loop.
the duration value determines the length of time of the state in millisecond.
500 milliseconds =.5 seconds so on the example the led turns of for .5 seconds and on for .5 seconds (blink)

Hope this helps

Re: Cross MIDI output mapping

PostPosted: 01 Aug 2019, 14:11
by ashp
ddjj wrote:Here is the list of the IN and OUT aliases (updated for 3.0)


For MixVibes Cross Pro v4 do they support 3.4.3 mappings are are the IN and OUT aliases the same?

I'm looking for an updated list for aliases and what they do

Regards,
ashp

Re: Cross MIDI output mapping

PostPosted: 01 Aug 2019, 14:35
by FigDJ
At this point is all trial and error since an updated list of MIDI messages for Cross 4 has not been published/posted yet.

Re: Cross MIDI output mapping

PostPosted: 18 Apr 2020, 13:58
by Dj Nico
My DDJ SR2 has RGB leds. Where can i get a list of numbers between 0 and 127, that relate to the colors.

E.g off=0, white=127, red=?, blue=? Etc?

Pioneer MIDI info says the numbers between 0 and 64, but doesnt say which number defines which color. Ive tried a few random numbers but all of them shows white??? :rolleyes:


FigDJ wrote:OK this is your command below
Code: Select all
        <mapping name="Cue 1">
          <events>
            <MIDI type="cc" parameter="0x7" channel="0x4"/>
          </events>
          <controls>
            <control alias="fam(Player)[0x1].Locator1Control"/>
          </controls>
          <preset name="Logic Fader/KnobHolder Button">
           <parameters>
            <parameter object="range" key="range begin" value="0"/>
            <parameter object="range" key="range end" value="1"/>
           </parameters>
          </preset>
        </mapping>

Normally cue button are map as Holder button so it would look
like this using note or cc depending on your controller. Normally Cross would detect if it is note or cc using the MIDI learn feature.

Note Example
Code: Select all
        <mapping name="Cue 1">
          <events>
            <MIDI type="Note" parameter="0x7" channel="0x4"/>
          </events>
          <controls>
            <control alias="fam(Player)[0x1].Locator1Control"/>
          </controls>
          <preset name="Holder Button">
            <parameters>
              <parameter object="invert" key="on" value="off"/>
            </parameters>
          </preset>
        </mapping>

CC Example
Code: Select all
        <mapping name="Cue 1">
          <events>
            <MIDI type="cc" parameter="0x7" channel="0x4"/>
          </events>
          <controls>
            <control alias="fam(Player)[0x1].Locator1Control"/>
          </controls>
          <preset name="Logic Fader/KnobHolder Button">
           <parameters>
            <parameter object="range" key="range begin" value="0"/>
            <parameter object="range" key="range end" value="1"/>
           </parameters>
          </preset>
        </mapping>

you go this

Now a little info on input and output commands.
Code: Select all
    <mappings>
      <input-mappings>
************************** All your input commands go here
      </input-mappings>
************************** You must create the output section
      <output-mappings>
************************** All your output(led) commands go here
************************** You must close the output section
      </output-mappings>
************************** You must close the mappings
    </mappings>
************************** You must close the controller
  </controller>
************************** You must close the file
</main>

Now an example of the led mapping in the output section
Code: Select all
        <mapping>
          <control alias="fam(Player)[0x1].Locator1Control" value="true"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="127"/>
        </mapping>
        <mapping>
          <control alias="fam(Player)[0x1].Locator1Control" value="false"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="0"/>
        </mapping>

You must map 2 conditions for each led contition on and condition off
The above example uses value 127 for on and 0 for off.
The value of the on condition determines the intensity.

However, on controllers that have have rgb leds the value of the
on condition determines the color.

The off condition value is always 0.
In addition if you want the led to be reactive to when you set, turn off or set a loop you must also map the condition for each in the output section.
As follows
Code: Select all
        <mapping>
          <control alias="fam(Player)[0x1].Locator1KindControl" value="0"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="0"/>
        </mapping>
        <mapping>
          <control alias="fam(Player)[0x1].Locator1KindControl" value="1"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="127"/>
        </mapping>
        <mapping>
          <control alias="fam(Player)[0x1].Locator1KindControl" value="2"/>
          <MIDI loop="true"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="127" duration="500"/>
          <MIDI type="cc" parameter="0x7" channel="0x4" value="0" duration="500"/>
        </mapping>

This set condition for on, off and blink when it is a loop.
the duration value determines the length of time of the state in millisecond.
500 milliseconds =.5 seconds so on the example the led turns of for .5 seconds and on for .5 seconds (blink)

Hope this helps

Re: Cross MIDI output mapping

PostPosted: 18 Apr 2020, 17:22
by Dj Nico
Nevermind, i figured it out. :mrgreen: