View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001766 | ardour | bugs | public | 2007-07-14 13:31 | 2007-08-29 11:46 |
| Reporter | oofus | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | Centrino 1.6GHz Laptop | OS | Linux | OS Version | Mandriva 2007 |
| Product Version | 2.0 | ||||
| Summary | 0001766: MMC messages are sent with an ID of 127(7F) regardless of the setting in the midi tab of the options window. | ||||
| Description | MMC messages are sent with an ID of 127(7F) regardless of the setting in the midi tab of the options window. | ||||
| Tags | No tags attached. | ||||
|
|
the MMC ID is the *target* of the message, not the source. 0x7F is used as an "all-call" target ID. do you have something else in mind? |
|
|
So are you saying that Ardour always sends MMC messages with an ID of 0x7F regardless of the ID setting? Also, that setting the ID means that Ardour will only respond to MMC messages with that ID and not 0x7F, or both the set ID and 0x7F. I expected that changing the ID would change what ID Ardour sent MMC messages to, not what ID Ardour would respond to. Also, Ardour should respond to 0x7F and its own registered manufacturer ID, or just 0x7F if one hasn't been registered, thus making it unnecessary to change the ID that Ardour responds to. This leaves only what ID it sends messages with to be configurable; a default value of 0x7F that can be changed to something else. |
|
|
Ardour now has configurable MMC IDs for both sending and receiving. |
