Comment 9 for bug 1531876

To respond to your earlier question about the deck-change message, (and for the sake of completeness), it seem this deck does indeed send a MIDI message when the deck changes (the poor Behringer documentation does not mention this!) I discovered this after putting Mixxx into controllerDebug mode. However, I still think it should be possible to accomplish this without scripting.

Your idea of telling Mixxx about duplexed controllers sounds like an interesting solution, however I still think the old "dumb" behaviour should be made available, (i.e. that the new more sophisticated behaviour should not be implemented at the expense of the more general dumb behaviour as this will *probably* be sufficient inn the majority of situations). Plus I guess there is also the possibility that a controller could become unsynchronised for other reasons than duplexed controls (e.g. when a deck is first powered up perhaps?)

Also, since the old dumb behaviour used to be the norm, I assume it would be relatively easy to re-implement (again perhaps with an adjustable sensitivity and using an alternate XML tag as suggested above so a not to break existing behaviour/controller-mappings).