of course we all agree on this, even if the 2nd part is wrongOn 2005-08-03 23:48, funkysam wrote:
In my opinion, one of scope's main selling point has allways been the flexible no latency routing with external gear...

Of course there is latency with external gear and it's easily enough to spoil any mix or drive you mad if you're unaware of it's existence.
The point is not if the thing is faster than hell or if it has any influence on someone's live performance.
A (processed) signal that comes in a few samples late or earlier regarding it's source will heavily interfere if both signals are mixed together.
As Johann mentioned you cannot notice that in a delay fx (say Husker's Space Echo) because it's late anyway, but an eq or a compressor would be almost out of control as it's frequency depending. It can even beef up certain sounds significantly...
I bet my *rse there are thousands of mixes in which the operator was totally unaware of this relation between parallel signals.
It's possibly even the main source if someone complains about not being able to get that transaprent and punchy sound...

I've had almost the same setup as Husker for some time and it took me several months before I noticed something didn't match.
By a mixture of unawareness and lazyness a (parallel) part of the signal (which should have been muted) made it's way to the monitors.
In such a situation your audible result is completely different from the recorded signal. If you tweak it as good as you can get it, burn a CD and proudly present it next day - you'll definetely be screwed

Of course it's not a problem at all if you monitor and record at the appropriate position of the processing chain - but first you have to be aware of it and todays typical setups are often pretty complex.
that's why such a stupid rule of thumb is really great - always keep your processing chain serial and double check the signal path where creativity drives you to leave the rule

cheers, Tom