Show HN: Parametric Equalizer for PulseAudio (opens in new tab)

> is compiled with -ffast-math and gcc vectorizes it

Automatic vectorization is extremely limited, in all compilers.

Check this out, feel free to merge if it works in reality not just in the test: https://github.com/Const-me/prettyeq/tree/master

fftw3 is extremely fast and vectorized well. Why write your own FFT implementation?

Did you test against pulseeffects cpu usage?

you likely want -O3 -march=native if building for your own machine, this way you get more than the SSE2 baseline if available

Hah, pulseeffects was why I wrote this project. It has tons of latency, very sluggish UI, not nice to use.

I have an HTPC hooked up to my speakers in my living room that I often SSH into in order to play music while I work, hence the need for a CLI EQ.

This is pretty accurate. I wrote it to tweak songs to my speakers when I'm streaming music. I wanted something very fast, no configuration, pleasant graphics.

While probably not suited for production work, the design is based off of existing production tools that I am very familiar with (Channel EQ from Logic Pro X, Parametric Eq 2 from FL Studio).

> These days, especially in EDM / Hip Hop, slight clipping in bass in somewhat stylistic.

No it's not, it's just widespread incompetence and has ruined lots of music I would have liked. Having better software tools that alert when clipping is happening would be a good thing (i.e. it needs to alert when crossing over from 0dB to a distorted wave form, not just hitting 0dB without distorting, which is fine).

If the equalization is done near the end of the audio output chain (ex: music player, defaults at 100% volume -> user sets master audio output volume to 50% -> EQ is applied) then a pre-amp is not strictly necessary if the EQ can take advantage of the extra headroom in the output channel. Otherwise, an adjustable pre-amp / gain setting would be nice, preferable with the option for it to automatically set itself to reduce by the maximum gain the EQ is applying to avoid clipping. But yeah, it should be optional; if the user wants stuff to clip, let it clip.

That makes me so happy to hear! Since this thread is getting less active, feel free to email me at kevin@segfault.fun if you need anything else.

It’s turned in to nagware.

a thanks, silly me. I wondered what that was.

Thanks!

First try I got: equalizer/equalizer.pro:10: Parse Error ('pretty.h')

Then I removed the extra pretty.h line and got: ../../gui/prettyshim.h:4:10: fatal error: QObject: No such file or directory #include <QObject>

which is beyond my time to dig right now :/