Feature Request: Track Templates (or something to speed up routing)

Hi,

I'm calling it "Track Templates" but really, the goal here is to provide a means to automate as much of the track setup process as possible. When writing, I tend to (somewhat) dread the idea of adding another track because I know I'm going to have to point and click my way through a bunch of steps I consider to be mundane. I'm talking about anything related to routing, not stuff like selecting an instrument plugin or adding aux sends as that stuff can't be assumed for any given track. Of course, I know what follows is based on my particular work flow so please take it with a grain of salt, realizing I'm simply trying to identify what I consider "routine work" that must be done every time a new track is added.

For context, I should also mention I've settled into the practice of using inserts on my buses to handle my routing. It's quite nice and credit goes to Carl for explaining it here

• Add a new insert (on an existing bus existing for the purpose of mixing down from individual buses used for instruments). We'll call this insert_N.
• Add a new bus. We'll call this busN.
• Connect the following:
  • busN/out_1 -> insert_N/in_1
  • busN/out_2 -> insert_N/in_2
• Add track
• Specify track's audio bus

With the workflow described above, each unit of work is driven from a different location in Qtractor. Sure, shortcuts exist but lots of opportunity exists to streamline this stuff.

So there'd obviously be 2 valid paths worth exploring here. One would involve a templated approach basing everything on known patterns. For example, if the string "Bus" were used as the constant, any new buses would just increment. Same thing for the Inserts and all that would be needed to be set by the user would be to answer the question "On what bus should these automatically created Inserts be created?". For example, if I were afforded this opportunity, I would specify a bus I call "MixIns" which I maintain for the sole purpose of acting as an endpoint for all my instrument buses. I then connect "MixIns" to a bus called "MixDown". The MixDown bus, then hosts several common plugins liike a general Reverb, compressor, etc. Had I combined everything in a single bus, it would be way too difficult to find anything later given how small the area is in the strip's area dedicated for this purpose.

The other (completely opposite) approach would be to drive everything manually; which would be fine, but do it from 1 central place. That place would naturally be the "Add Track" dialog where tabs exist for Track details and plugins, but routing opportunities are very limited. I know the ... can be used to get into the Buses dialog but seriously, why bother? I mean, wouldn't it be cool to just check something like "Create New Bus" checkbox and know 1) a new one will be created and 2) the track's audio will be routed to it. Same thing for an option to create a new Insert on demand.... Everything done from 1 location based on predetermined settings.

I also just realized everything I just scribbled is based on my MIIDI workflow. I tend to not work with Audio very much and realize there are some differences which remove some of the complexity there (I think?).

So that's the request... I'm 100% certain I'm overlooking some things and fully expect there would be many edge cases to consider. Also, I know all about the benefit of Qtractor templates (which I do use) and have tried to limit the points I'm making to adding and working with new tracks........ which goes beyond the benefits of the template approach just mentioned.

Looking forward to feedback.