Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No default cutoffs for high-fi EQs. Leads to incorrect EQ behavior. #5338

Closed
mixxxbot opened this issue Aug 22, 2022 · 8 comments
Closed

No default cutoffs for high-fi EQs. Leads to incorrect EQ behavior. #5338

mixxxbot opened this issue Aug 22, 2022 · 8 comments
Labels
Milestone

Comments

@mixxxbot
Copy link
Collaborator

Reported by: cle1911
Date: 2010-02-24T18:20:24Z
Status: Fix Released
Importance: Medium
Launchpad Issue: lp527249


I'm running the 1.8.0 beta1 on ubuntu 9.10 32bit (amd 64 X2 DualCore 4200+, 2gb ram)
"cat /proc/asound/cards" tells
0 [NVidia         ]: HDA-Intel - HDA NVidia
                          HDA NVidia at 0xf9ff8000 irq 21

(onboard Realtek HDA card)
MIDI devices are not in use

I can't control the high- band- and lowpass filter separately. Changing band- and lowpass filter or killing these ranges won't do anything, the highpass controller and its kill switch affect the song on all ranges, so that killing highrange kills the whole song.
There are no error messages when running mixxx from the console.

@mixxxbot mixxxbot added the bug label Aug 22, 2022
@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2010-02-24T21:06:42Z


Hey Clemens,

Are you using the high quality EQs or static EQs? You can configure the EQs from the preferences menu. It may very well be that our static EQ settings are bad or at least unsuitable for the type of music you are playing. What kind of music are you playing?

Thanks,
RJ

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2010-02-24T21:07:11Z


Also, did you use 1.7.2? Does this occur in 1.7.2 for you?

@mixxxbot
Copy link
Collaborator Author

Commented by: cle1911
Date: 2010-02-28T14:28:31Z


static EQ works, it really seems to be a problem with the high quality EQ settings, I'll check that.

@mixxxbot
Copy link
Collaborator Author

Commented by: cle1911
Date: 2010-02-28T14:29:17Z


and yes: in 1.7.2 it worked

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2010-09-22T08:47:58Z


What are your high and low filter EQs cutoffs set to? Can you try setting your top one to 2.5 kHz and your bottom to around 100 Hz and see if that helps?

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2010-12-06T23:56:45Z


Finally realized this is because the default when you install mixxx is static eqs. If you turn off static-eqs, then your high-fi EQ cutoffs both default to 0. We should set some sane defaults, like 250Hz for the low and 2500Hz for high (those are arbitary). With both cutoffs at 0, the high EQ is the only knob that has any effect.

@mixxxbot
Copy link
Collaborator Author

Commented by: bkgood
Date: 2011-01-23T19:18:52Z


Fixed in lp:mixxx/1.9 r2664 like 3 weeks ago and forgot to mark it here :/

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Released.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
@mixxxbot mixxxbot added this to the 1.9.0 milestone Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant