View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000137 | ardour | bugs | public | 2003-11-17 07:25 | 2008-11-21 00:03 |
| Reporter | nettings | Assigned To | v2 | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000137: in-/outputs on multi-channel tracks should always have #tracks ports | ||||
| Description | on multi-channel tracks, sends should have as many outputs (and inserts and plugins as many ins and outs) as there are channels on the track. it needs to be transparent at all times which channel goes where - to avoid an extra stage of routing, there should be a hard-wired 1:1 correspondence of channels and ins/outs, and the user can leave unneeded ports unconnected. | ||||
| Additional Information | for the case in which on channel of a multichannel track must be sent to more than one destination: i suggest not to allow this directly, but instead to do that via an additional track. | ||||
| Tags | No tags attached. | ||||
|
|
Is this still an issue? If so, it should probably wait until after 1.0. |
|
|
sends are fixed, port inserts are not. |
|
|
are port inserts fixed yet? |
|
|
I'm guessing this is fixed. Inserts were done a few years back. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-11-17 07:25 | nettings | New Issue | |
| 2004-07-31 23:13 | taybin | Note Added: 0001325 | |
| 2004-08-03 22:47 | paul | Note Added: 0001368 | |
| 2007-02-14 22:35 | taybin | Note Added: 0003275 | |
| 2008-02-19 06:37 | v2 | Status | new => resolved |
| 2008-02-19 06:37 | v2 | Resolution | open => fixed |
| 2008-02-19 06:37 | v2 | Assigned To | => v2 |
| 2008-02-19 06:37 | v2 | Note Added: 0004728 | |
| 2008-11-21 00:03 | seablade | Status | resolved => closed |
