View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005523 | ardour | features | public | 2013-06-12 14:06 | 2015-09-18 15:29 |
| Reporter | colinf | Assigned To | colinf | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0005523: Can't insert audio- or MIDI-only input plugins after a plugin with both MIDI and audio outputs. | ||||
| Description | Some plugins (e.g. setBfree) have both MIDI and audio outputs. Thus, the only kind of plugin that can be inserted after such a plugin is one which has both MIDI and audio inputs. Attempting to add any other kind of plugin after an instance of setBfree causes the "Plugin Incompatibility" window to appear, saying: "... This plugin has: 0 MIDI inputs ... at the insertion point there are: 1 MIDI channel ...", or (in the rather less useful case of adding another instrument plugin after): "... This plugin has: 0 audio inputs ... at the insertion point there are: 2 audio channels ..."" It'd be nice if, in the case of trying to add a plugin with only audio inputs in a place where both audio and MIDI channels are available, the MIDI channels could just be ignored; maybe even vice-versa for plugins with only MIDI inputs. | ||||
| Tags | No tags attached. | ||||
|
|
I suppose there's scope for a 'dummy' plugin that has both MIDI and audio in, but only audio out, that passes the audio straight through, that could be used in this case, somewhat analagous to the good old days of having to use the 'mono to stereo splitter' LADSPA plugin in A2, but I can't say I miss having to use that in A3. |
|
|
Tangentially, there's also something not quite right in the pluralisation of the text: "but at the insertion point, there are:" should read "... there is:" in the case that there is only one channel, but only if there are not both audio and MIDI streams or inputs. I'm not sure whether it'd be possible, let alone desirable, to try to achieve that using ngettext(), but fixing it by coding in English grammar assumptions also feels a bit wrong. |
|
|
dave, carl and i have talked in the past about a generic design to allow anything-to-anything connections. it is quite a complex task .... |
|
|
It seems that bfd50cde fixes this, too. |
|
|
Closing old issues reported by me: these have long since been fixed. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-06-12 14:06 | colinf | New Issue | |
| 2013-06-12 14:10 | colinf | Note Added: 0014984 | |
| 2013-06-12 14:38 | colinf | Note Added: 0014985 | |
| 2013-06-12 15:37 | paul | Note Added: 0014986 | |
| 2013-08-02 09:55 | colinf | Note Added: 0015216 | |
| 2013-08-02 09:55 | colinf | Status | new => resolved |
| 2013-08-02 09:55 | colinf | Resolution | open => fixed |
| 2013-08-02 09:55 | colinf | Assigned To | => colinf |
| 2015-09-18 15:29 | colinf | Note Added: 0017311 | |
| 2015-09-18 15:29 | colinf | Status | resolved => closed |
