bapu
sharke
I wonder if something like this would be of any use to me given that I already have MAutoAnalyzer to identify frequency collisions.
Well I would suspect probably not, but does MAutoAnalyzer also create an EQ curve based on what it found? That might be a tipping point since Neutron does (which of course you can tweak).
That may be helpful in some situations yes, although I have to say I think the whole area of identifying frequency collisions and applying curves to correct them is only part of the whole EQ story. Sometimes MAutoAnalyzer will identify a "hotspot" which to my ears isn't really doing the mix any harm. I think it's possible to get too obsessed with perfect separation, sometimes instruments share frequency ranges and that's OK.
When I first got MAutoAnalyzer I went a little nuts trying to "correct" every collision it identified. You end up chasing your tail. First of all, those collision hotspots are moving around all the time as the music plays. You might see a brief flash at 500Hz and then it moves to 1kHz for a second, and then 250Hz lights up. And secondly, you can lose your mind comparing one instrument to another and seeing different frequency clashes. Pretty soon you've got multiple EQ's and stupidly complex curves all over the place. The only time I use it now is when I have a really big problem with masking. And first and foremost, I try to avoid that by giving more thought to sound selection. Every now and then I will put three or four sounds together and they all sound perfectly distinct and balanced before I've inserted a single EQ. Doesn't happen very often but when it does it always reminds me of how little EQ you can get away with if you choose your sounds wisely.