Generally, cutting more than boosting is a pretty good rule of thumb.ĮQing as a process alters the phase of your program material-this may be important or not to your particular needs, but it is one significant feature that distinguishes EQ processors. If you synthesize your own sounds, try making their EQ clean from the get-go, and you don't have to EQ as much to get them to fit in the mix.
If you hold Ctrl while dragging the EQ band, it drags more precisely.Ĭheck reference mixes if you feel that helps. Pay close attention to how the EQ edit you are doing changes the sound, and try to find middle ground don't neglect to boost very high, then cut very low, to narrow in on that optimal gain on the EQ band. Some tips I would give for cleaner EQing (less overboosts, less excessive cuts, etc) are: I don't use that quite as much, though, for typical EQing, since it is more RAM-heavy and really accomplishes the same thing with negligibly higher precision (plus it doesn't have as good of a visualization feature IMO).
I do also have FabFilter Pro-Q, which is a more precise EQ plugin that has a standard deviation of 0.01 dB, as compared to Fruity Parametric EQ 2, where its standard deviation is 0.1 dB. I still love to use Fruity Parametric EQ 2 for its visualization feature, and I'm probably not going to stop using it anytime soon.
