FR (another small tweak): Ability to set track destination as <No Output>

[vitocorleone123]

I'm trying to come up with small workflow related suggestions as opposed to major features, as I know that's the theme of W10. In this case, there can be times when it can be handy to select (never default) a <No Output> as a track destination so that it's just holding content. For example, if you want to be able to have a kick .wav that's visible as a reminder that it's triggering side chain compression you can have it in the track and then be absent when it's not in effect, but still making no sound.

[abrickwall]

Although it's not built in, you can currently set this up yourself. Create a new track and name it "No Output." Go to the Volume plugin on the No Output track and mute it. You can go to the Tracks panel in the browser and Hide the "No Output" track if you don't want to see it. Now any track you route to "Track ## (No Output)" won't play sound.

[spoontechnique]

It would also be nice to be able to set an output to bypass the master effects, in case you want to have reference tracks, for example.

[HansP]

Although it's not built in, you can currently set this up yourself. Create a new track and name it "No Output." Go to the Tracks panel in the browser and disable the "No Output" track. Now any track you route to "Track ## (No Output)" won't play sound.

would it not stop any processing at all, in the whole subtree?

[abrickwall]

would it not stop any processing at all, in the whole subtree?

You're right. Changed my original post. Should work correctly this way.

[HansP]

if we need a track to generate side-chain data, and we mute it, we'll get in trouble.
my workaround is to put an extra stock fader at the end of the track and mute it which in this case means -INF.
If I use a rack to wire the side-chain, I can set the particular dry and wet outputs of the rack to the track to -INF.

[dRowAudio]

If you mute a track, it should still trigger side chain input I think...
Isn't this the easiest option? We can't add a "<No Output>" destination as that would remove it from the audio graph entirely and then it certainly wouldn't sne the sidechain signal.

[fde101]

We can't add a "<No Output>" destination as that would remove it from the audio graph entirely and then it certainly wouldn't sne the sidechain signal.

The function of the "<No Output>" should obviously be a fake output that accepts the audio signal (allowing it to process first) and does nothing with it.

[chico.co.uk]

We can't add a "<No Output>" destination as that would remove it from the audio graph entirely and then it certainly wouldn't sne the sidechain signal.

The function of the "<No Output>" should obviously be a fake output that accepts the audio signal (allowing it to process first) and does nothing with it.

How would that be different to muting the track?

[fde101]

How would that be different to muting the track?

Less likely to be "unmuted" accidentally. To me, a track in a recording is muted because I temporarily don't need it and I will probably unmute it when I see that it is muted without giving much thought to why it was muted to begin with. Setting the destination to "No Output" would signal a more permanent situation and make it easier to keep track of a track that shouldn't be tracked...

[chico.co.uk]

Okay, well if it was me, i'd mute the track, and hide it from display, in the Tracks section of the panel browser, if you think you're likely to un-mute it.
Then it wouldn't even be displayed on screen to distract you.