EQs should not process by default

[mixxxbot]

Reported by: ywwg
Date: 2014-04-09T19:31:26Z
Status: Fix Released
Importance: Wishlist
Launchpad Issue: lp1305269

---

A lot of our users never touch the EQs at all, and asking them to specifically disable EQ processing is an extra step. Instead, we could simply disable EQs at startup, and if the user tweaks a knob, then we enable EQs. The user can still explicitly override EQs, but this pattern would save tons of CPU for many users transparently without affecting actual DJs. (We crossfade, so there won't be a click when they first tweak the knob)

[mixxxbot]

Commented by: rryan
Date: 2014-04-09T19:43:43Z

---

Yea, good idea. We had a bug for this a few years back but since we weren't crossfading there was clicking so we didn't do it.

[mixxxbot]

Commented by: ywwg
Date: 2014-04-10T14:59:25Z

---

#227

[mixxxbot]

Issue closed with status Fix Released.