-
If only one track/bus in “regular” group is selected and there is Mute or Solo option turned on in the group properties, apply Solo and Mute switch for entire group, not just for that single selected track/bus.
-
Save mixer tracks/buses width with the session. If I make them all narrow, some of them become randomly wide next time opened.
Our decision for #1 was that if you disable shared selection for a group (so that selecting one item in it will not select them all), we are not going to override that by enforcing the group properties. It wasn’t an easy decision, but we felt it was the one that was mostly likely to be correct for more users, more of the time.
This is really bad. I almost always miss the “solo” or “mute” buttons as they are really small and click on a track by mistake selecting it. So mute or solo whole group is an arcade game for me. This is really badly thought out. 
The above sentences are my personal opinion only. I do not intend to hurt anyone’s feelings.
Do you know of lots of other Ardour users who also think this is a really bad decision?
If something isn’t right for your particular setup and workflow doesn’t mean that it’s also wrong for the vast majority of Ardour users.
Paul’s reply indicates that this way of doing it was taken after some hard considerations.
You, or some of the others who may feel the same way, could always send a pull request to make it a configurable option.
I don’t know many other Ardour users actually. But if I keep quiet, no one will ever know that some functionality has drawbacks for someone and can disrupt workflow used over the years. And this particular feature is misleading. There are obvious group settings where you can check “solo”, “mute” and other options shared by the group, but sometimes it works, sometimes it doesn’t which can be difficult to figure out by users.
Maybe you should have expressed your personal feelings by writing “This doesn’t work for me” instead of the more accusatory “This is really bad… This is really badly thought out”.
Ardour is open source so if the workflow has changed in the last versions you can always revert that change yourself or continue using a version that worked for you in the past.
Or submit a PR to make it an option or start a petition to show Paul and Robin that a majority of users feel the same way you do.
Telling an open source developer “your decisions suck” is usually not that productive if there’s only one user feeling that way.
You’re right. Sorry for that.
I appreciate the idea of quick groups, but the way they work affects the regular groups too much (in my opinion). 
Also, it is probably possible to write a Lua script, which implements the behaviour you want and bind it to a keyboard shortcut.
It sounds like you might benefit from going to:
Edit → Preferences → SIze and Scale → GUI and Font Scaling
and telling everything, including those buttons, to grow a bit.
No, thanks. I tried that.
Actually I’m in the middle of fully switching to Presonus S1, the only thing that stops me is no GUI support in other plugins than the embedded. I like these plugins, but I miss the drums (I mean real drum set, not the simple sampler, I use MTPower Drumkit II). I really hope that some Windows plugin wrappers, like Yabridge or so, will get native Wayland support soon (S1 is Wayland only, and it can display only Wayland plugins GUI). I tried Tracktion Waveform but while it’s a great DAW with all features I need (great comping and audio bend), I really dislike it’s look’n’feel. The same with Reaper. Bitwig Studio is focused on other things than recorded audio and traditional workflow. I really love Ardour and I keep fingers crossed for it’s future, but it miss basic tools (ie. no comping at all). And the features I really liked for years are being changed in a way that I don’t like.
This quick grup behaviour could be easily fixed if we assume that quick group is more than one track. That’s all. So if I select one track in regular group and press solo, all grouped tracks are soloed. If I select two or more - then only them are soloed. Everyone is happy. Have a great day! Skygge.
Hi Thomas! I’ve just recorded a very short video especially for you, to show you how comping using layers in Ardour actually works.
So I would be curious as I don’t see that behavior here on Mixbus 10 at least. What you are showing is a bug, but I am curious as to the cause, in fact I see likely two bugs there, one of which has to do with locations so far down the timeline they cause an out of bounds error/crash. What version of Ardour are you using, and did you get it from this website?
Seablade
Ardour 8.9.0 “Sonora Portraits” (rev 8.9) Intel 64-bit
Downloaded from ardour website.
Interesting. I would love to hear if others are able to replicate this behavior, as what you are seeing are definitely bugs in my experience. It would be most useful first and foremost to determine what is causing the bugs for instance, and address that. That would likely improve the usefulness of comping in Ardour for you.
Seablade
This can be observed if one of recorded layers was previously splitted.
Record. Split the region. Record new layer over it. Voila!
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.