Itās not fun if you donāt share it with others
And yes, I have a few ideas for more fixed racks but Iām just waiting for VCV to stabilize a bit first.
Stand-alone template. Iām running Plateau, Valhalle Supermassive, Soundtoys Echoboy and Clouds on the 4 aux busses. Then thereās some dynamics, coloration and limiter: Bassmaster, Waves Kramer Tape, Waves LA-2A and Fabfilter L2. Channel 1-8 on the MindMeld have some lo cut filtering and levels pre-set.
I was just updating my template patch, so I thought I would revive this topic, how are all your templates doing?
Previously my template patch had been slimed down to just the very basics because when testing modules during development I normally donāt want any extra fluff around my focus.
But having changed my speakers I need to update my audio settings in the template, so I figured Iād make a change:
The main changes are simply reintroducing a mixer, because adding a mixer is normally the very first thing I do in a new patch. Adding a limiter, because I am a lazy and donāt like anything to be too loud. Added the Host-FX module because, although Chronoblob is amazing, I feel it is becoming a crutch, so I am going to prop myself up on ValhallaSupermassive for a bit instead. And finally, I swapped out the Inklen Cable Color Key for the Count Modular Palette. The Inklen module is great, but I really really need it to remember which colour I have selected between saves, rather than revert back to the first colour, I find that so annoying.
I am trying to decide if I should move my Keystep Pro over to my work desk and setup the midi and maybe a Patchmaster thing as a controllerā¦ do I want that in the template, or just as a selection that I can import?
I absolutely canāt decide between Inklen - great for recolouring - and the Submarine one - collapsible and lets me pick from a long list of colours to cycle through, but setting cable colours after the fact is laboriousā¦
Using Stroke to map keys to some basic functions like reset, record start/stop, mute, and zoom to extents of the patch. The Startup Delay forces a reset on patch load and also forces the patch to be muted for the first 3 seconds after load.
Interesting, so you save patches that are in a running state or is this just a safety thing? (I guess you might be loading someone elseās patch and donāt know its starting state)
I normally always put in some sort of start/stop mechanism before I save them, which I also use during any video capture, but I could see this being useful for saving in progress patches
Most of my patches tend to be free running or I have a sequencer controlling the arrangement and Iām too lazy to stop everything and reset it before I save it so I force the restart on load.