Sign In:     

Forum: General Discussion

Topic: Stupid mapping / definitions file questions

This topic is old and might contain outdated or incorrect information.

Okay, I've been riding on all your coat tails for long enough and I'm trying to wrap my brain around the whole "making my own mapping" thing. So I've got a few questions about the mapping and definitions files that I'm not seeing in the documentation (or maybe have changed in v8 anyway).

1) How do you look up the default definitions of natively supported controllers? Specifically, what each key is called. I'm not seeing xml files anywhere so I'm assuming it may be compiled into the software itself?

2) If I don't want to use the default definition, how do I call to my own definition file in the devices directory? I've looked at a few samples but don't see a call anywhere in the xml.

To put it in context, I'm trying to do some mapping of my VCI-400 transport controls, but in the native definitions the transport buttons don't seem to be specified individually but rather grouped together. Play on deck 1 seems to send the same control as play on deck 2, leaving it to the software to see which side you are actually working on. I'm trying to fix the deck controls to ultimately have access to 4 decks at once similar to how Serato lays out the 400, but when I attempt to lock the play button on one side to deck 1 it locks the play button on deck 2 as well...

Anybody want to help a newbie out? Just remember to talk slowly... ;-)
 
Posted Thu 10 Jul 14 @ 12:02 am
1) You cannot have access to the definitions files. If you wish to see how each key is named, you will need to add all the Keys to a custom mapping, even if those are assigned as "nothing". Then you can open the custom mapping.xml with a Text Editor and see how everything is named.

2) In order to use a custom definition instead of the default one, simply add force- in front of the name. E.g. force-MyVCI400definition.xml

3) This is how all keys are defined. There is no PLAY_LEFT or PLAY_RIGHT, just PLAY
If you wish to have different action for the left and different action for the right, you can map the keys as ..
device_side 'left' ? action for the left side : action for the right side
or
action_deck 1 ? action when a button is pressed on deck 1 : action_deck 2 ? action when a button is pressed on deck 2 : action_deck 3 ? action when a button is pressed on deck 3 : action when a button is pressed on deck 4
 
Thanks for the quick reply!

Okay, I get that there is no play_left or play_right, but my two play buttons both seem to send back the same name "track_pad_decks_play" despite both having different midi notes (26/D1/ch3 vs. 30/F#1/ch6). Is the native definition grouping the two notes together and is there no way to separate them without having to write my own definitions file?

And assuming there isn't, and I'll be writing my own definition file - where exactly am I putting that force command?

Thanks again!
 
 


(Old topics and forums are automatically closed)