midi input on channel 2 broken
Bug #706435 reported by
William Good
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Fix Released
|
High
|
William Good | ||
Bug Description
Reporting mostly for my own benefit (so I figure this out and don't forget).
Using Vestax Typhoon mapping in 1.9bzr r2685, NOTE ONs don't seem to be registering if they're for [Channel2]. [Channel2] changes from midi script are fine.
Related branches
lp:mixxx/1.9
(Merged)
Revision history for this message
| William Good (bkgood) wrote | #1 |
| Changed in mixxx: | |
| status: | Confirmed → Fix Committed |
| Changed in mixxx: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #2 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
Fixed in lp:mixxx/1.9 r2686. The PortMIDI translation layer was passing along the entire status byte as the opcode, so if channel was greater than 0, (in my case, the message was on channel 1 which translates roughly to [Channel2]), the channel number being in the opcode byte would mess up matching with the byte signature given in the mapping xml later in the midi call chain. This has existed in code since 2010-12-12, which I guess was post-beta.