View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008368 | ardour | bugs | public | 2020-08-18 20:28 | 2020-08-19 09:00 |
| Reporter | unfa | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Platform | Arch | OS | Linux | OS Version | (any) |
| Product Version | 6.2 | ||||
| Summary | 0008368: Strict I/O not working on MIDI tracks? | ||||
| Description | Please watch this quick demonstration of the problem: https://youtu.be/x-D5NAJts_U It seems that Strict-I/O on a MIDI track doesn't really constrain the output channel count like I thought it would. Am I doing something wrong? is this expected behaviour? | ||||
| Tags | Midi | ||||
|
|
from https://manual.ardour.org/signal-routing/signal-flow/ Midi Synths. When adding a synth at a point where there is a Midi port only, the synthesizer plugin will add audio output ports, which trickle down the processor chain to all follow up plugins as inputs and in turn force their outputs to match. |
|
|
I see. I'd expect the Strict-I/O to make sure the port layout doesn't change after the first instrument plug-in. But maybe that doesn't make sense, because there's so many different things that could be done here that'd break... Thought if they do - the user could just switch to Flexible-I/O. I guess Strict-I/O only works if we have also audio ports in the MIDI track - for a Vocoder plug-in for example? Do you think it could make sense to alter it's behaviour for MIDI tracks/buses? |
