Same request was made last year but the topic was closed. I think it’s a great suggestion: when working with larger projects it’s quite cumbersome to assign tracks to VCAs/busses one by one. For implementation ideally can just add/remove the desired VCA/bus routing to all selected tracks, without effecting existing assignments/IOs.
As that post mentions, maybe it’s possible with Lua scripting but as Ardour progresses I’m hoping there can be less reliance on scripting for useful tasks like these — it would be Ardour a lot more intuitive to use for beginners.
Using Ardour for quite some time and following the forum i notice regulary that you created really awesome features … that “no one” knows about because the documentation in the manual is either not there or somehow doesn’t reach the user (me).
Is there something we can do to improve the documentation? (Document something we don’t know of hen egg problem, tho)
As said, been here for a while and done that repeatedly. The manual is great for getting the general concepts and workflow but it doesn’t cover every feature yet. There were several occasions where @paul himself stated “this feature is not documented that well” (can’t recall the forum posts so the quote is a sum up from my memory and should be treated as such.). Yes that were very specific operations but still.
The “50 things you can do with Ardour” vid was great because it filled that gap a little but it also showed that there is a gap.
I know it’s a ton of work to document things and i get the frustration of “people often said they want to help and then do nothing”. I don’t see myself doing big parts on a regular base either. But a little text here and there or a short video about one feature is not impossible. I also get the argument of not relying on pictures because of GUI development. All valid points.
My question is, how can we help improve documentation if we don’t know of the features because they’re not documented?
