pmidi use wrong device number
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pmidi (Debian) |
Fix Released
|
Unknown
|
|||
pmidi (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: pmidi
This bug was originally reported by fueryuejing.
https:/
pmidi use wrong device number on multi port midi file and send SysEx
all ports. This problem is caused in src/midiread.
Further information is following:
a. Device num (msp->device) and port num (msp->port) is served to deal multi
port if channel num is over 16. For example, if port num is 0 and
channel is 2, then device num become 16*0+(2-1)=1. If port num is 2 and
channel is 14, then device num become 16*2+(14-1)=45.
b. Therefore if status byte (status) is channel message (0x80-0xef),
destination device num of message must be "port(msp>
c. However if status byte is SysEx message (0xf0-0xff), device num must eqaul
to "port(msp-
d. In source code at this time, if pmidi is recived SysEx message,
debice num(msp->device) will be 0, even use any port and channel num.
e. This patch is that default device num set to
"port(
And add channel num to device num, if message is not SysEx.
Related branches
Changed in pmidi: | |
status: | Unknown → New |
Changed in pmidi (Debian): | |
status: | New → Fix Released |
pmidi (1.6.0-4build2) jaunty; urgency=low
* Add debian/ patches/ 01-multiport. dpatch
- Deal multiport midi file (LP: #316265)
* Modify debin/control file
- Bump up Standards-Version to 3.8.0
- Add ${misc:Depends} to Depends field
- Move Homepage field to first paragraph