I second this. It’s really something I’ve missed now and then too. If there are many effects I usually go around it by inserting a new track and copying the track to it. That way it’s easy to switch between them by just soloing the tracks (right-clicking the scopes).
Yes this is fine if you want to put all your fx on a send. The only prob is that send tracks are limited to the right of the screen making it for less convenient tracking. If you use this method also you are likely to end up with as many send tracks as normal tracks. To me this is not convenient.
With the method I mentioned you keep all your fx on your original track/s and then just route as many tracks you want to, to a single empty send. The inconvenience here being that you do have to switch your mute keep source buttons.
Both are not as convenient as a master tick would be to me, but thanks for mentioning anyway.
Is that just a workaround or are you arguing against the suggestion? Anyway, I can’t see any problem with a “bypass fx” checkbox, but the send track solution is definately more tedious, as Ledger mentioned.
Well, a good idea could indeed be grouping DSP effects in various chaingroups, but this will require a different list-mode…
(A list on the left and the viewpanel of the selected listobject on the right with all the parameters.)
I don’t think this will increase the overview that much over using a few send-tracks.
Besides it will probably also require new effect commands of which there’s isn’t much room.
And adding an extra digit in any of the available columns without complete having to reshuffle the core source-structure seems out of the question for the devs.
Combining columns or removing the F limition and continue counting up to Z is being considered newbie unfriendly.
How would anyone design a newbie friendly concept that does not require new effect-commands?
I second this suggestion, it is very useful to be able to hear track “dry” on the fly, especially when mixing the song. Acid has this option, and I use it a lot. There could simply be a button next to active+off+mute buttons. Ot maybe it could even replace the “active” button, which I don’t find much use for anyway (you could just as easily unclick off or mute buttons instead clicking “active”).
Well then why not just have a send device at the beginning of the chain, with the mute button permanently set, and then just tick/untick the enable box whenever you need to hear your track dry? The send track it would send to would be empty of course.
Heh, I must have missed your first post, otherwise I would have worded that differently. Funny that, if I’d read it then I probably wouldn’t have thought of this at all. The mind works in myserious ways.