I'm not a working composer. (I just have pretensions and aspirations to be). I am trying to work some small projects to build up my portfolio and gain experience. I'm in the process of building templates to help my workflow. Nothing huge, but large enough to require a bit of scrolling about if everything were visible and many many instance of Kontakt to host the various instrument articulations.
I'm building them in CUBASE. I've kind of gone whole hog into CUBASE these days...even ditched my Avid ArtistControl for the simpler but purpose-built CC121 AI Controller from Yamaha/Steinberg. Liking it very much too.
Anyway, as I was building these templates, it occurred to me that having instrument "families" (eg, CineSample Core and Pro Brass) configured as CUBASE Track Presets (which can include the separate midi and audio output channels), would allow me to configure templates quickly "on the fly" instead of having multiple huge templates keyed for various project types. All midi assignments, VST output assignments (eg, Kontakt main out, Kontakt 3-4, etc.) and corresponding aux tracks, and track names ARE remembered in a CUBASE track preset, and the actual Cubase project template file would only have to contain a standard set of submix channels (eg, stringSub, brassSub, windsSub, or variation). (This is necessary because audio output assignments and output channels are not memorized in a Track Preset. As a consequence, all multi timbral instrument output channels default to the main stereo out when you load the track preset.)
So, the workflow would be: I open a template that contains only submix and main output channels, load my multitrack track preset, assign the audio outs to the pre existing submix channel(s) I have in the template, roll the new instrument into a folder, and repeat as needed. No huge template to wade through and which I may not use a lot of, no dozens of unused VSTs loaded up into the template gobbling up resources.
(You can do this same type of thing in most DAWs. In DP, you can use 'clippings' to grab whole set ups if I remember correctly and drop these clippings between projects. In LOGIC the new summing tracks feature offers an eloquent and more robust solution than the approach I described above. I think - not sure - you can also do something like this via drag and drop in StudioOne.)
My question: Is there something I am not seeing here that is a show stopper? Seems like most working composers build huge templates as opposed to using short cuts to build templates on the fly like this. As I can't be the only person to ever think of this or try it, there must be a reason most of these folks I read about default to mega templates. Is there something I am not seeing in this approach that makes it less attractive?