Support - MIDI Output mapping utility (intro)

[BennyB]

write here any questions, and problems.

BEFORE POSTING READ THIS THREAD:

Many of you know, that I was working on a MIDI Output Mapping tool, to make output mapping easier.

It's in early phases, but here you go.

ONLY USERS WITH GOOGLE ACCAUNT CAN USE IT!!!

MixVibes Cross 2.x MIDI Output Script (Alpha 1.3.4)

When you open it, go to File/ Make a Copy... to copy it into your own Google Doc base, and after that you can use it!

Recommended for advanced users.

Da-FAQ Section :
1. Can It open my mapping file?
No it can't!

2. What does this document do?
Basicly you input your MIDI data (alias, notes, channel. etc..) and it generates a code that you can use in your Mapping file.

3. How can I generate the code?
Click on the big GENERATE button on the right. If you can't see it, look at the black cells, and click the middle of them. On first try, it will ask you to use the script... bla-bla-bla, just OK everything. After this you'll be able to generate the code.

4. What does "Entry No." and "File Name" mean?
There is an Entry No. Culomn in the left. Just check the number of the last row you used in the document, and type that in. The File Name will be the name of the Google Doc that will be generated.

5. Where can I find that Google Doc, and what's inside?
The generated doc will be in you Google Drive document list in a few moments, with the File Name you inputed before. In the Doc there will be the code you'll need!

EXPLANATION OF CULOMNS and technical terms in the doc:
Alias: it is the name of the parameter you want to give led feedback to. For example fam(Fx)[0x1].OnOff means, that you want to control a led to tell you, if the FX1 in Cross is active or not.

STATE: various states of the parameter. Active/on (true), Inactive/off (false), % for mapping VU meter leds, or led rings to show the set value of a fader or knob, and the rest are multiple states, for sample pads, loop values, etc.

note: This is the note assigned to the led you want to control. Most controllers has a table that contains these.

type: It is the type of the led-note. Note means, that the led will light up, or not, or simpli blink, but in the defined way in the code. CC is a dinamic thing. You use CC to control ring leds, VU meter leds, or single leds, to light up if the limiter engaged.

channel: The MIDI channel of the led-note.

value: This value determains if the led light up or not. For example 0 means no light, 127 means full brightness. Also some controller use different values to define different colours, on mulit-colored pads or buttons.

Blinkstate: CONSTANT means, the led will glow constantly, and TRUE means the led will blink.
loop: The blinking continues, if set to true, otherwise it will blink only once.
time: blink time set in milisconds (ms). Set it from 500 or less. 500 means, the led will blink at every half seconds (one blink in a second). 100 means, it will blink 5 times in a second.

6. How do I use my generated code?
Open the Google Doc, with the code. Select all (Crtl+A), and then copy it (Crtl+C).
Once you've done it open your mapping file (make a copy of the mapping file you wnat to put this in). Open the file with Notepad, then look at this part in the file, and look for this, an basicly do as I say below.

Code: Select all

      </input-mappings>
      <output-mappings>
code goes here as you copied it from the Doc
      </output-mappings>
    </mappings>
  </controller>
</main>


If you already have stuff in the Output Mapping section, find the last one and follow this:

Code: Select all

      </input-mappings>
      <output-mappings>
.
.
.
     </mapping>
code goes here as you copied it from the Doc
      </output-mappings>
    </mappings>
  </controller>
</main>


Once you've done, save the file. Open Cross, import the mapping, and try it... make sure your controller is plugged in.


IMPORTANT NOTE:
FEEDBACK PLEASE

IF YOU NEED HELP FEEL FREE TO POST BELLOW! (No support by PM).
Don't write to any MixVibes Staff member, about problem of this Document, they will be angry

HAVE FUN USING IT!!!

[dj_decka]

First off I wanna say thank you for makin this tool.

I am sure when I have a better understanding how it works, I am sure this will become quite useful.

I'll start from the beginning.

I am running 3 MIDI boards. One VCI 400 and 2 LPD8 pads.

The default mapping on the VCI 400 makes the pads above the job wheels the sampler pads. I want to use those pads for other things hence the LPDs. I delete the mapping for the sampler pads on the VCI. When I trigger the sampler via LPD...The light that would indicate the sample is being triggered on the VCI lights up. What I am trying to is turn the led off.

Following me so far?

[Alexkidd]

Find which MIDI notes the vci's pads send.
Edit the .mapping.xml file with notepad++ editor
Go to output mappings in the xml and carefully delete the code that lights the pads with that send these MIDI notes.
I hope this works

First off I wanna say thank you for makin this tool.

I am sure when I have a better understanding how it works, I am sure this will become quite useful.

I'll start from the beginning.

I am running 3 MIDI boards. One VCI 400 and 2 LPD8 pads.

The default mapping on the VCI 400 makes the pads above the job wheels the sampler pads. I want to use those pads for other things hence the LPDs. I delete the mapping for the sampler pads on the VCI. When I trigger the sampler via LPD...The light that would indicate the sample is being triggered on the VCI lights up. What I am trying to is turn the led off.

Following me so far?

[dj_decka]

I got it so far.

Channel 3 - Note 0x7 in MV is the pad that creates the LED on the VCI I want to change. Its marked as Pad 1 Control under Sampler 1 in mapping.

Would Pad 1 Control be under fam(Sampler)[0x1].Pad1Control?

What does State do?

I figure Note means 0x7 so I put in 7.

Type is Note.

Channel is 3.

Value. Would putting this at 0 stop the LED from lighting?


I'm sorry I am asking all these questions.

[BennyB]

First find your VCI-300's mapping file.
If you are on windows here it is:

C:/users/<your username>/AppData/Romaing/Mixvibes/Cross/Controller/MIDI

Try to open each file, and in the file header you can see the controller's name. Here is an example:

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>

<main>
  <version major="1" minor="0"/>
  <controller kind="MIDI">
    <id ID="884035051"/>
    <properties Model="MPK Mini" Manufacturer="AKAI" Version="4" Publisher="DzsoniB"

Once you found the proper mapping file make a copy it, to your desktop, and open it up with wordpad, or notepad (Wordpad is better.)
Scroll down untill you see this section (Ctrl+F, and type in "/input" it will jump there )

Code: Select all

</input-mappings>
      <output-mappings>

In this code search for something like this:

Code: Select all

fam(Sampler)[0x1].Pad1Control

It might look something like this:

Code: Select all

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

Now start deleting these section from <mapping> to </mapping>, you'll see every pad number twice as all of them needs a dubble mapping (one in case it is active, and one in case it is not (True and False). After you deleted these, check if everything is Ok, like no extra <mapping> or </mapping> frases were there, and save the file.

Once you saved it, Open up Cross, go to Preferences/ MIDI, and the click the import button ( ->[] ), then navigate to the edited mapping, and import it, then select it.

Test if all the light are ok, except the pads.

If the pads don't light up on sample trigger that is good. If nothing else lights up you deleted something you shouldn't.

If you have no clue, attach the mapping file to you post (in a .rar), and I'll edit it.

(Giving support at 3:00 in the morning is fun )

IMPORTANT BUTTOM NOTE:

You need to delete the code I told in the VCI mapping, because that mapping id only for the VCI, so if you don't need those lights to light up, just delete them. The LPD-08 has a different file, so editing those lights should be there.

[dj_decka]

I do appreciate the help at 3 in the morning.

My untrained eyes are starting to see the code in the matrix..

Used Note Pad ++ to open xml file.
Found the code for the pad. Changed the value on false to 0. Saved.
Imported map. Test.


LED is not on anymore when LPD triggers.


Teach a man to fish...

[Alexkidd]

It was late here too when i posted so i hadn't the courage dzsonib had to post such detailed and helpful instruction.
dz props man!
decka i'm glad you managed it.

[BennyB]

I do appreciate the help at 3 in the morning.

My untrained eyes are starting to see the code in the matrix..

Used Note Pad ++ to open xml file.
Found the code for the pad. Changed the value on false to 0. Saved.
Imported map. Test.


LED is not on anymore when LPD triggers.


Teach a man to fish...

You can delete those lines. They can mess things up. Without them things will be more stable.
You can also keep the original mapping, so it's quite flexible.


Tip: I usually make a Folder for a bunch of .txt files containing all my controller output mapping parts (just the output mapping section), and also keep the originals I make. This way they are easy to maintain edit and correct.

[dj_decka]

So delete the True and False part all together?

[BennyB]

So delete the True and False part all together?

Exactly. Just see my post above I told this, there is a code example. But be careful: Delete each true and flase stuff from <mapping> to </mapping> and don't leave empty lines there, so the code won't be interrupted after the deletions.
It's actually routine stuff for me