User Tools

Site Tools


serato_sysex

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
serato_sysex [2016/08/30 10:12]
sblaisot
serato_sysex [2016/08/30 19:56]
be.ing
Line 5: Line 5:
 Controller manufacturers and Serato use this manufacturer ID to exchange sysex messages from the computer to the controller to trigger some functions of the controller. Controller manufacturers and Serato use this manufacturer ID to exchange sysex messages from the computer to the controller to trigger some functions of the controller.
  
-Currently, the only identified System Exclusive MIDI message using this ID is described below+Currently, the only identified System Exclusive MIDI message using this ID is described below.
  
 === Controller status dump === === Controller status dump ===
  
-It appears that serato ​sends the ''​F0 00 20 7F 03 01 F7''​ sysex message to the serato ​certified controllers to ask them to send back the status of each item on the control surface (the value of all knobs and sliders) which means:+It appears that Serato ​sends the ''​F0 00 20 7F 03 01 F7''​ sysex message to the Serato ​certified controllers to ask them to send back the status of each item on the control surface (the value of all knobs and sliders) which means:
   * F0 ⇒ Begin SysEx Message   * F0 ⇒ Begin SysEx Message
   * 00 20 7F ⇒ it's the Serato Manufacturer according to https://​www.midi.org/​specifications/​item/​manufacturer-id-numbers   * 00 20 7F ⇒ it's the Serato Manufacturer according to https://​www.midi.org/​specifications/​item/​manufacturer-id-numbers
Line 15: Line 15:
   * F7 ⇒ End of SysEx Message   * F7 ⇒ End of SysEx Message
  
-After receiving this message, the controller sends back a midi message for each item (knob, slider, ...) sending its current value. Using this after the input connections has been done matches the mixxx controls to the controls on the controller.+After receiving this message, the controller sends back a MIDI message for each item (knob, slider, ...) sending its current value.
  
-So if you are mapping a serato-certified controller, you can try to send this sysex message by adding this declaration at the top of your javascript file:+So if you are mapping a Serato-certified controller, you can try to send this sysex message by adding this declaration at the top of your javascript file:
 <code javascript>​ <code javascript>​
 // The SysEx message to send to the controller to force the midi controller // The SysEx message to send to the controller to force the midi controller
Line 24: Line 24:
 </​code>​ </​code>​
  
-and send it at the end of your ''​init()''​ function, after connections ​has been made:+and send it at the end of your ''​init()''​ function, after connections ​have been made:
 <code javascript>​ <code javascript>​
 // After midi controller receive this Outbound Message request SysEx Message, // After midi controller receive this Outbound Message request SysEx Message,
Line 31: Line 31:
 midi.sendSysexMsg(ControllerStatusSysex,​ ControllerStatusSysex.length);​ midi.sendSysexMsg(ControllerStatusSysex,​ ControllerStatusSysex.length);​
 </​code>​ </​code>​
 +
 +This should make Mixxx match the state of your controller when Mixxx starts up and the mapping is loaded.
serato_sysex.txt · Last modified: 2016/08/30 19:56 by be.ing