Mixvibes Dj Community old forum

I want to map PadSelect outputs to my pad leds, so the selected pad will glow. How does it look like in code? I know there is something with the status value.
If you only tell me status value for each pad, I'll be happy

What's really needed is a full on data dictionary identifying the various values for the integer type values and what they mean.

I had to do some trial and error with the looping values and it drove me batty for a little bit.

DzsoniB wrote:I want to map PadSelect outputs to my pad leds, so the selected pad will glow. How does it look like in code? I know there is something with the status value.
If you only tell me status value for each pad, I'll be happy

PadSelect ?didn't see this one into the list.
What are you trying to do (please describe the behavior).

MusicMeister wrote:What's really needed is a full on data dictionary identifying the various values for the integer type values and what they mean.

There isn't such a thing. The only document is the CrossControlAliases list.

Support@MixVibes wrote:

DzsoniB wrote:I want to map PadSelect outputs to my pad leds, so the selected pad will glow. How does it look like in code? I know there is something with the status value.
If you only tell me status value for each pad, I'll be happy

PadSelect ?didin't see this one into the list.
What are you trying to do (please describe the behavior).

MusicMeister wrote:What's really needed is a full on data dictionary identifying the various values for the integer type values and what they mean.

There isn't such a thing. The only document is the CrossControlAliases list.

I misstyped. It is: fam(Sampler)[0x1].SelectActivePad

Seems like an 'Integer' so the value is the one from the pad (don't remember it it's start from 0 or 1). Try from 0 to 7 or from 1 to 8.

Something like :

Code: Select all

<control alias="fam(Sampler)[0x1].SelectActivePad" value="x"/>

Support@MixVibes wrote:

MusicMeister wrote:What's really needed is a full on data dictionary identifying the various values for the integer type values and what they mean.

There isn't such a thing. The only document is the CrossControlAliases list.

I said it was needed, not that it existed.

It would make work on mappings much easier.

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 ACCOUNT CAN USE IT!!!

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

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!

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

PM me, I'll give full support for this! Don't write to any MixVibes Staff member, about problem of this Document, they will be angry

HAVE FUN USING IT!!!

Didn't looked into it but thanks to have bringing it further...

Support@MixVibes wrote:Didn't looked into it but thanks to have bringing it further...

Your Welcome! Test it extensively...

Feedback, Support and info about this Mapping app, is from now on here:

http://forum.mixvibes.com/viewforum.php?f=401