View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002734 | ardour | features | public | 2009-06-16 14:54 | 2020-04-19 20:14 |
Reporter | seanbutnotheard | Assigned To | cth103 | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | fixed | ||
Target Version | 3.0-beta1 | ||||
Summary | 0002734: Enhancement of edit and/or mix groups | ||||
Description | This is more of a "feature discussion" as I would welcome feedback to refine this idea. Mix groups and edit groups are great features, but I think they need a few additional tweaks to be truly workflow-enhancing. Here are my thoughts for how to make these features great: 1. Make the features more visible to the user: When creating a route, the user should have the option of adding to a new or existing edit/mix group. 2. Under the "g" and "Grp" buttons, the user should be able to create a new group rather than just assign to an existing group. This seems more intuitive than managing via the group lists. 3. Visually, the groups should be obvious when looking at the editor/mixer. My thought was to have a "header" of sorts that groups the routes together. This would imply that routes in the same group should be physically next to each other. I've attached a crude mockup to demonstrate the idea. Then, the user could engage/disengage the grouping functionality by simply clicking the header. Other thoughts: Is there really a useful distinction between edit groups and mix groups? Would it perhaps be more useful to have a general "route group" feature, where different parameter sets (i.e., editing, M/S/R, fader levels, etc) can be linked individually? This might be equivalent to automatically making a mix group when an edit group is created, and vice-versa. If the devs see this as a viable enhancement, I'd be glad to add some modest sponsorship (and would hope that some other users might too). | ||||
Tags | No tags attached. | ||||
Users sponsoring this issue | ||
Sponsors List |
Total Sponsorship = US$ 75 2009-06-17 13:24: seanbutnotheard (US$ 75) |
---|
2009-06-16 14:54
|
|
|
Hi, I'm inclined to agree with these suggestions. I'm not entirely sure of the distinction between edit and mix groups, but merging them seems like a good idea to me. |
|
Positive feedback from one developer is good enough for me. I'd say we can consider this "closed" when the 3 main points listed are addressed; The other thoughts about merging group functionality could perhaps be considered for future development. Thanks! |
|
The editor group headers are now implemented in 3.0 SVN. Your suggested layout would have been better, I think, but is very tricky to do, unfortunately. |
|
You can now assign new tracks to particular edit groups, and create edit groups from the route 'edit group' menu. |
|
This should all be implemented now. Comments welcome. |
|
I'll do an SVN checkout and test it this week. Thanks! |
|
Played with this today and I really like the implementation. I like how the tabs gracefully split and join when the routes are reordered, this is probably better than my "always keep grouped routes physically together" idea. The options to link various parameters individually are great too (in the new group dialog). A few comments (as of rev. 5244): In the new track/bus dialog, the "Add to Group" option doesn't display any existing groups. Also, a "new group..." option would be nice in there as well, in fact I imagine that's where it'll get used the most. Minor GUI tweak: I'd suggest putting a max width on the Group button in the mixer strips, because the changing button label can make the button (and hence the whole strip) really wide, which is kind of a waste of screen space. I also just noticed that the tabs in the mixer don't refresh when the strip order changes. |
|
Thanks for the feedback, this should all have been fixed up in SVN. |
|
Looks great! I've sent payment to Paul. Two very small bugs: the tabs in the mixer don't resize when strip widths are changed, and the tabs will be hard to see against the background if the tab color is dark. For my next feature request: an Ardour 3.0 alpha release... ;) |
|
Two larger issue: Gains don't seem to be linked among members of a group when "Gain" is enabled. Also it appears that "Selection" must be linked in order for edits to apply to all members of a group; Having "Editing" alone selected doesn't work. Or maybe it's just not doing what I'm expecting. |
|
The mixer strip width thing should be fixed now. Also Paul has fixed the gain grouping. You're right about the selection / editing thing, I'll try to sort that out. Thanks! |
|
Editing now works on grouped tracks without "Selection" enabled as a group property. |
|
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 |
---|---|---|---|
2009-06-16 14:54 | seanbutnotheard | New Issue | |
2009-06-16 14:54 | seanbutnotheard | File Added: ardour-groups-1.jpg | |
2009-06-17 10:40 | cth103 | Note Added: 0006133 | |
2009-06-17 13:24 | seanbutnotheard | Sponsorship Added | seanbutnotheard: US$ 75 |
2009-06-17 13:24 | seanbutnotheard | Sponsorship Total | 0 => 75 |
2009-06-17 13:43 | seanbutnotheard | Note Added: 0006134 | |
2009-06-20 13:43 | cth103 | Note Added: 0006138 | |
2009-06-20 15:40 | cth103 | Note Added: 0006144 | |
2009-06-20 17:19 | cth103 | Note Added: 0006145 | |
2009-06-20 17:19 | cth103 | Status | new => feedback |
2009-06-21 17:53 | seanbutnotheard | Note Added: 0006150 | |
2009-06-22 15:10 | seanbutnotheard | Note Added: 0006153 | |
2009-06-22 22:31 | cth103 | Note Added: 0006155 | |
2009-06-23 13:29 | seanbutnotheard | Note Added: 0006159 | |
2009-06-23 14:40 | seanbutnotheard | Note Added: 0006160 | |
2009-06-23 23:06 | cth103 | Note Added: 0006162 | |
2010-07-21 15:46 | cth103 | cost | => 0.00 |
2010-07-21 15:46 | cth103 | Target Version | => 3.0-beta1 |
2010-08-28 15:02 | cth103 | Note Added: 0008928 | |
2010-08-28 15:02 | cth103 | Status | feedback => resolved |
2010-08-28 15:02 | cth103 | Resolution | open => fixed |
2010-08-28 15:02 | cth103 | Assigned To | => cth103 |
2020-04-19 20:14 | system | Note Added: 0021933 | |
2020-04-19 20:14 | system | Status | resolved => closed |