Hello. This is to notify you that the MIDI mapping XML format has changed somewhat and you'll need to make some adjustments: - <miditype> has become <status> which allows you to enter the desired hex byte (op-code and channel) directly for full customization - <midichan> has been removed due to now being present in the status byte
For those of you working on MIDI scripts, the scripting API has also changed slightly: - The "Device" parameter has been removed - "Category" has become "Status" - The .init function now requires acceptance of an ID string parameter (but you don't have to do anything with it.) - The channel numbers passed to the script now start at zero for direct use in MIDI messages Full details are on the wiki as usual: http://mixxx.org/wiki/doku.php/midi_controller_mapping_file_format http://mixxx.org/wiki/doku.php/midi_scripting Let Albert or me know if you have any questions. Sincerely, Sean M. Pappalardo <<--------------------------------------------------------------------------------->> This E-Mail message has been scanned for viruses and cleared by >>SmartMail<< from Smarter Technology, Inc. <<--------------------------------------------------------------------------------->> ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
