| 2010-05-18 20:24:23 |
Bruno Buccolo |
description |
Let's say a user wants to map one midi message to multiple controlobjects:
Button 1 --> Sync Deck A
Button 1 --> Sync Deck B
or
Button 1 --> Flanger Deck A
Button 1 --> Crossfader to Side A
Something like that is impossible to Mixxx, since after the first mapping is made, the second mapping of the macro overlapps the first one.
I'm working on the bug, currently trying to use QMultiHash for the MidiInputMapping, but it was really not as simple as I tought.
I'll post up the research as I go, and also link this bug to my Midi Learning Branch since I'm already working with midi there :)
Thanks. |
Let's say a user wants to map one midi message to multiple controlobjects:
Button 1 --> Sync Deck A
Button 1 --> Sync Deck B
or
Button 1 --> Flanger Deck A
Button 1 --> Crossfader to Side A
Something like that is impossible to Mixxx, since after the first mapping is made, the second mapping of the macro overlapps the first one.
I'm working on the bug, currently trying to use QMultiHash for the MidiInputMapping, but it was really not as simple as I tought.
I'll post up the research as I go, and also link this bug to my Midi Learning Branch since I'm already working with midi there :)
Thanks.
== Followup ==
By using QHash::insertMulti or even QMultiHash for the MidiInputMapping, it seems that Mixxx can already save the correct midi.xml, however, it doesn't work (macro) and it's not displayed correctly in the MidiInputMappingTable.
|
|
