dmbaer
This already exists.  It's called MSpectralDynamics from the same folks that brought us MMultiAnalyzer.

Interesting stuff.  Some very far-reaching possibilities.  But I am thinking of more of a "wizard mode" process where the software starts to think like an expert-level sound engineer.  That is the concept with LANDR and I think there is a lot of potential in that direction. 
 
I would draw a parallel with many photo processing programs.  Some tools allow a person to do extremely detailed editing, and there is a place for that.  But many of they have features where the software some more of the tedium, such as fixing red eye. 
 
It would be nice for a tool to detect these frequency collisions and pop up a menu of possible actions I might want to take, such as duck the bass under the kick drum, lighten the kick fundamental, but boost the harmonics that don't conflict, attenuate the kick after the the attack to leave more room for the bass, move the kick to the sides with the bass being more in the middle, etc.

cparmerlee

jeteague
    A good reference for understanding reverb in mixing is Mike Senior's  book "Mixing Secrets".  There is a chapter dedicated to reverb.  He breaks the use of reverb into five different functions: blend, size, tone, sustain, and spread. 

Senior says that reverbs should always be done on separate buses.  I'm OK with that, as it is easy to do in Sonar.  I have not done this in the past, but will probably make that SOP going forward.
 
I am studying what Senior has to say about each of those 5 uses for reverb.  For now, I will probably concentrate on blend and size as these seem to be the first order uses -- the other 3 being more advanced and subtle. 
 
His approach seems to imply (but he doesn't exactly state) that he would use 5 separate reverb buses, because the shape of the reverb could be different for each of those 5 uses.  Is this a correct reading of his advice?  Do any of you normally set up multiple reverb buses along the lines Senior suggests?

I'm in total agreement.
 
After reading Mike's book, this is the strategy I always adopt now.
I find that Blend & Size are the only 2 I really need.
 
If you did decide to use one of the other functions then yes, create another bus.