View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008910 | ardour | features | public | 2022-05-03 09:10 | 2022-05-04 13:47 |
| Reporter | johne53 | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Microsoft | OS | Windows | OS Version | 10 |
| Product Version | 6.9 | ||||
| Summary | 0008910: Strange inverted behaviour with track groups | ||||
| Description | This was first reported by a Mixbus user but I couldn't reproduce it in Mixbus - however it seems very reproducible in Ardour. Although it refers to tracks, it's easier to see in the Edit window. | ||||
| Steps To Reproduce | 1) Select two Editor tracks and click 'Group->New Group' to add them to a group. 2) Moving one fader will now (correctly) move them both. 3) 'Shift+Move' will (correctly) move only the selected fader. 4) Now select 'Group->Edit Group' and mark the group as inactive. 5) Each fader can now (correctly) be moved independently - i.e. as if they weren't grouped. 6) BUT - 'Shift+Move' now moves both faders. | ||||
| Additional Information | The Mixbus user found it in MB for Linux (not sure which Linux) | ||||
| Tags | No tags attached. | ||||
|
|
That is intentional. Shift "inverts" the group behavior. |
|
|
In that case there seems to be an inconsistency between Ardour and Mixbus - namely:- 1) Select two Editor tracks and click 'Group->New Group' to add them to a group. 2) Moving one fader will now (correctly) move them both. 3) 'Shift+Move' will (correctly) move only the selected fader. 4) Now select 'Group->Edit Group' and mark the group as inactive. 5) Each fader can now (correctly) be moved independently - i.e. as if they weren't grouped. 6) And in Ardour - 'Shift+Move' now moves both faders. 7) But in Mixbus - 'Shift+Move' still only moves the selected fader. |
|
|
Sorry, I should have added that items 6) and 7) refer to adjustments made in the Mixer window (adjustments made in the Edit window seem okay) |
|
|
(6) Ardour -- is what I expect to happen. Shift + action inverts the group setting: deactivated groups (group-settings) are enabled, and vice versa. But yes, Mixbus changes various hardcoded modifiers in Route-UI for their mixer-strips. e.g. shift+click does not reset the Mixbus-Faders to default (double-click does). Mute/Solo buttons group-override is ctrl+click in Ardour, but shift+click for Mixbus. and Solo-isolated toggle is also different ctrl+click in Mixbus... It is inconsistent since the Ardour widgets retain their original behaviour. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-05-03 09:10 | johne53 | New Issue | |
| 2022-05-03 18:18 | x42 | Note Added: 0026427 | |
| 2022-05-04 11:17 | johne53 | Note Added: 0026428 | |
| 2022-05-04 11:23 | johne53 | Note Added: 0026429 | |
| 2022-05-04 12:34 | colinf | Relationship added | related to 0007741 |
| 2022-05-04 13:47 | x42 | Note Added: 0026430 |
