Frequency kill not working when using high/low shelf eq

Bug #629065 reported by jus
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Invalid
Medium
Unassigned
1.10
Invalid
Medium
Unassigned
1.9
Won't Fix
Medium
Unassigned

Bug Description

Mixxx 1.8.0 (bzr r2517; built on: Sep 2 2010 ; flags: hifieq vinylcontrol midiscript optimize=1 qdebug)
MacOSX 10.5.8

*Load a skin with HIGH/MID/LOW frequency kill buttons
*In Mixxx` Preferences-->Equalizers deactivate the static EQ`s
*Load and play a track, you will notice the KILL buttons not working as expected any more

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

I can't seem to reproduce with the 1.8 branch. The kills work as expected with static EQs disabled. What are your frequency cutoffs set to for the high-fi eqs?

Changed in mixxx:
milestone: none → 1.8.0
Revision history for this message
jus (jus) wrote :

Mixxx 1.8.0 "(bzr r2395; built on: Sep 8 2010; flags: hifieq vinylcontrol midiscript optimize=2 qdebug)
All preferences on default

Short screencast clearly illustrating the problem
http://screenr.com/HSn

Possible related bug:
https://bugs.launchpad.net/mixxx/+bug/229021

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Ah I see now. Your low and high cutoffs are so close together that the high cutoff kills the whole range. My high-fi eq settings are with the high end at 2.5 kHz and the low end at 200 Hz.

Another issue though is when you pin the ranges together your volume maxes out. I've seen this before but can't reproduce it now. Are you on 32-bit or 64-bit?

If the default preferences leave the high-fi eq cutoffs so close together we should change them to something reasonable like I listed above.

Changed in mixxx:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → RJ Ryan (rryan)
Revision history for this message
jus (jus) wrote :

Im on 32bit.

But this frequency kill behaviour might be only symptom for filter related problem Nick pointed out in 2008 (link in #2) which link to an assert crash https://bugs.launchpad.net/mixxx/+bug/629053

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Yea, looks like that bug is exactly what I saw in your video.

The IIR assert isn't related to this though, because the high-fi EQs don't use the IIR filters, they use Butterworth filters, which is in a different class. (it's even more computationally expensive :-/).

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Hm, this one slipped through. Is it still happening?

Revision history for this message
jus (jus) wrote :

Yes this still happens to be in trunk.
Deactivate static EQ, use the default values ( High 2.47 Khz , Low 249 Hz) and you`ll see the kill switches do not work as expected.

You can also hear a crackling sound when moving the EQ sliders in the preferences while a song is playing and no kill switch is activated.

RJ Skerry-Ryan (rryan)
Changed in mixxx:
milestone: 1.8.0 → none
RJ Skerry-Ryan (rryan)
Changed in mixxx:
assignee: RJ Ryan (rryan) → nobody
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Can you reproduce on the latest trunk? I can't (though I never could).

Revision history for this message
jus (jus) wrote :

Can`t reproduce either.
Works fine with 1.10 final and current lp:mixxx r3100

Changed in mixxx:
status: Confirmed → Invalid
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/5498

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.