MCompare is among one of my favorite tool for mastering, although i think a peak spectrum analyzer would be so much useful, so we can compare and check both master and our reference visually too.
The idea is to have a spectrum analyzer that also enable to hold peaks (just check "Hornet MultiFreq" with peak enabled) that shows both tracks simultaneously but just listening one of them (as it is right now).
Otherwise to achieve the same stuff you need to make inconvenient routing making a submix, and stuff i'd love to avoid cause it may mess up with the mix and other stuff
here you find a very raw mockup i made just to give an idea
The reason of this request is because when you have a reference to match may be very handy (and it is) also to check the spectrum, expecially on the lower part of the spectrum that may look trickier on headphones or without a sub.
And so also the scale of the frequency should be more detailed (as logaritmic scale) between 0 to 100 hz to give a more accurate reading of this area, that is something lots of analyzer fail with imo.
Ps: the average knob on mmultianalyzer isn't the same as a an maximum hold peak visualization.
For reference as the analyzer should work, just check the hornet analyzer with peak enabled to see how it behave cause it's well made
The idea is to have a spectrum analyzer that also enable to hold peaks (just check "Hornet MultiFreq" with peak enabled) that shows both tracks simultaneously but just listening one of them (as it is right now).
Otherwise to achieve the same stuff you need to make inconvenient routing making a submix, and stuff i'd love to avoid cause it may mess up with the mix and other stuff
here you find a very raw mockup i made just to give an idea
The reason of this request is because when you have a reference to match may be very handy (and it is) also to check the spectrum, expecially on the lower part of the spectrum that may look trickier on headphones or without a sub.
And so also the scale of the frequency should be more detailed (as logaritmic scale) between 0 to 100 hz to give a more accurate reading of this area, that is something lots of analyzer fail with imo.
Ps: the average knob on mmultianalyzer isn't the same as a an maximum hold peak visualization.
For reference as the analyzer should work, just check the hornet analyzer with peak enabled to see how it behave cause it's well made
Statistics: Posted by Frankie.T — Thu Apr 25, 2024 11:15 am — Replies 0 — Views 25