Quote:
Originally Posted by geraintluff
Be mildly warned: Spectrum Matcher uses more CPU than you might expect (it's basically a 30-band EQ - I considered using FFT instead, but there are reasons to do the analysis this way.). Rather than have 10 instances running at once, I personally use this correction as a preview, and then use the correction curves to create a matching curve in ReaEQ. (If you hover over the top graph, it should show you the frequency/dB values of its correction curve.)
|
That could be automated - we can create ReaEQ bands and set parameter values from Reascript. But the corrected data should be exposed as parameter values...
Would it be possible to store the curve (gain values) to, for example, 30 hidden sliders?
Really great work, thank you