EQs should not process by default
Bug #1305269 reported by
Owen Williams
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Fix Released
|
Wishlist
|
Owen Williams | ||
Bug Description
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)
Revision history for this message
| RJ Skerry-Ryan (rryan) wrote | #1 |
Revision history for this message
| Owen Williams (ywwg) wrote | #2 |
| Changed in mixxx: | |
| status: | New → In Progress |
| importance: | Undecided → Wishlist |
| Changed in mixxx: | |
| status: | In Progress → Fix Committed |
| Changed in mixxx: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #3 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
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.