Ok, lets start.
Changes with the GUI:
when you already have a texteditor-altered midi XML, don't map anything new to it in the GUI.
by doing so, it will be rewritten completely once you press "save" in the midi setup, srewing up at least your order. also removing your comments. "Comments" you ask?
Comments:
you can add comments, but they are not copied to your auto_save.XML
Quote:
<!-- this is a comment -->
everything inbetween <!-- and --> is ignored
I WILL FROM HERE ON USE COMMENTS IN THE PROVIDED EXAMPLE CODES.
Shift Functions
a lot of Controls have shifted functions. if you have read the manual, this is nothing new to you.
you can map them regularly from within the GUI already.
Example for the GUI method:
in internal mode, enter midi mapping mode, hold shift and then klick on the pitch fader
now map a button. this button will now reset the pitch to zero.
A lot of control elements have a shifted function. READ THE MANUAL
now here is the fun part.
you can also map them with a text editor:
Example for TEXTEDITOR method:
Quote:
<!-- this is an autoloop -->
<Control name="Auto Loop Half Button A" channel="8" event_type="Note On" control="91" />
<!-- this is a loop roll -->
<Control name="Auto Loop Half Button A" channel="8" event_type="Note On" control="78"
key="alt+ctrl"/>
See? the control name is identical, but by adding the key="..." part, the functionality changes.
possible values for key="..." : shift, alt, ctrl, alt, alt+ctrl, maybe some more combinations.
Modifiers
you can define your own midi shift keys:
Example:
Quote:
<!-- this is the button which acts as a shift key or "modifier" -->
<Modifier name="MyFirstModifier" event_type="Note On" channel="16" control="124" />
<!-- this is the unmodified button (simple click) -->
<Control name="Play Forward A" channel="8" event_type="Note On" control="42" />
<!-- this is the button with holding down the modifier (modifier hold plus button click) -->
<Control name="Play Reverse A" channel="8" event_type="Note On" control="42"
on_modifier="MyFirstModifier"/>
Undocumented Functions
Check the Konix (Youtube: "SeratoTutor") Video about deleting Cue Points via MIDI,
and check the Thread here in the forums about platter control.
Finding the codes for Functions
I use to create a new mapping, map what i want, e.g. a Cue Button.
then save.
now i open in texteditor, and look at the resulting code.
Example:
Quote:
<Control name="Trigger Cue Point Button A0" channel="8" event_type="Note On" control="65" />
now i copy that one code line for one cue button on one deck, paste it into my mapping XML several times and change it the way i need it
such that it controls the other cues or even the other deck. usually the names are pretty self explanatory.
Example:
Quote:
<Control name="Trigger Cue Point Button A0" channel="8" event_type="Note On" control="65" />
<Control name="Trigger Cue Point Button A1" channel="8" event_type="Note On" control="66" />
<Control name="Trigger Cue Point Button A2" channel="8" event_type="Note On" control="67" />
<!-- and so on -->
