View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003499 | ardour | features | public | 2010-10-15 13:29 | 2020-04-19 20:14 |
| Reporter | b0ef | Assigned To | paul | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | won't fix | ||
| Target Version | 3.X | ||||
| Summary | 0003499: MIDI Tracer Connection Manager | ||||
| Description | It would be nice if the same type of connection manager as there is for audio and midi would be available for the MIDI Tracer as well. As it is now, it only allows to select Ardour special MIDI ports. | ||||
| Tags | No tags attached. | ||||
|
|
the MIDI tracer within ardour doesn't watch JACK or ALSA MIDI ports. it tracks data read and written by the internal objects within Ardour. it was never intended to be a general, standalone MIDI tracer. carl wrote a nice jack midi monitoring utility that either has been or will be present in the next release of jack1. it can be used on any JACK MIDI port. |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-10-15 13:29 | b0ef | New Issue | |
| 2010-10-16 11:56 | cth103 | cost | => 0.00 |
| 2010-10-16 11:56 | cth103 | Target Version | => 3.X |
| 2010-10-19 16:55 | paul | Note Added: 0009279 | |
| 2010-10-19 16:55 | paul | Status | new => resolved |
| 2010-10-19 16:55 | paul | Resolution | open => won't fix |
| 2010-10-19 16:55 | paul | Assigned To | => paul |
| 2020-04-19 20:14 | system | Note Added: 0022249 | |
| 2020-04-19 20:14 | system | Status | resolved => closed |
