On Fri, Apr 10, 2009 at 11:58:56PM -0400, Sean M. Pappalardo wrote: > 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
Next up, the format will change to being a raw stream of MIDI bytes! Seriously, I don't see why the old system had to be *removed* in favour of the new system. Using type + channel is plainly easier for humans than having to calculate a combined status byte. Couldn't you have allowed for the incredibly rare cases that the status byte needs to take a value that can't easily be represented in terms of type and channel, by *adding* that ability alongside the existing format instead of replacing it? Sorry to carp but it really seems to me that lately the format of MIDI maps is becoming easier for machines to read and write at the expense of becoming more complicated for humans to read and write. Ben ------------------------------------------------------------------------------ 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
