Originally Posted by selig
Actually, the Rack view is EXACTLY the same as the Mixer view. They are not different functions at all.
Just like there's a play button at the bottom of the Mixer, the Sequencer, and the Rack (unless you collapse the transport, of course!); It's the SAME button, duplicated in the interface for your convenience. The same is true of the Mute/Solo buttons in the Rack and Mixer.
But OTOH, the Sequencer's mute is muting the NOTE DATA, while the Mixer is muting the AUDIO DATA. One example of how linking these would be impossible would be a ReDrum. I can have a single track in the sequencer (with multiple note lanes if you like), but can be split to appear in up to 10 Mix Channels. OK, now if you hit mute in the sequencer it's clear you'll mute all the drums, but which of those 10 Mix Channels would you want linked in the Mixer?
Not only that, but like my Sends example, linking them (if it WERE possible in all cases), would be redundant since muting one would give the exact same end result as muting the other - silence. Linking them wouldn't give you 'double-silence'!
So a mute is not a mute, as you say, because it DOES matter where in the signal path the mute is located - sends/returns are an excellent example of multiple mute points in the signal flow. Hope this helps in some way. :-)
Yeah yeah, I get it - but I have to be honest, its silly. The very odd occasion this might be handy you could easily do with track automation.
I really dig this software, dont get me wrong, but there are one or two little things like this that imho make the whole interface very clumsy and clunky once you start getting into larger projects.