Ben Wheeler wrote: > 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.
Albert actually rewrote the MIDI back end for a multitude of reasons, the most visible of which is so that MIDI scripts could get the unadulterated data they need to be truly future-proof. This also allows more flexibility for simple XML-only input and especially output mappings. To not replace the old system wholesale meant more hacks which we're trying to get away from. He can tell you more though. (Or you can have a look at the MidiMapping class code.) > 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. Like Adam said, modern controllers give you the status bytes in hex in their MIDI manuals, so all users need to do is copy them without having to know what they mean (with the possible exception of the channel number, but that's easy enough to understand.) Sean <<--------------------------------------------------------------------------------->> 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
