Details: I am building my first orchestral template: After I configure all the routing, mics, and set the articulations for everything, I duplicate the track and configure the duplicates as shorts, pizzicato etc. When I am done with each library I keep Long (or Legato in some libraries) active, but for shorts, pizzicato etc. I deactivate the track hoping to save CPU. Rationale being that once a library is open, the duplicates load very fast. The performance meter is barely moving except for the Asio Guard which runs at about 20% without even having anything loaded. The real time and peak I am guessing at 3-4%
So… does that mean disable track doesnt do anything? This sounds like a lot of clicking once you get 50-60 tracks, you may as well just duplicate and create a new track (1 click)
r
“Disabling a track […] shuts down all […] processing for the track.”
Apologies, my suggestions are just additional options to control how ASIO-Guard behaves – see under " Further hints for ASIO-Guard". It’s an old article but still valid as it explains exactly what the effects of ASIO-Guard are. If disabling tracks is quicker for you, it will save CPU.
I must be doing something wrong as I crashed my template yesterday and lost about 2 hours worth of work. I barely had 20 tracks, Ive had way more than that with other pieces I’ve written. I have a crap ton of ram and processing power… I must be too stupid to understand how to do this, it’s my third attempt at creating a template, all failed miserably.
From experience disabling a track does improve CPU, taking it completely off the system.
This is not the same as muting a track, which is still getting processed if audio is passing through it. Even bypassing plugins does not take them off the CPU (if audio is passing through). You have to disable them to get the CPU benefit.
