You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I won't go into depth describing the bevavior. Because either I am completely missing something and there's no bug or it is apperent that something is wrong and must be looked into further anyway.
BUG:
"Kill Mid" button and "High" knob affect each other in the Waveform Display when using "Filtered", "RGB" or "Stacked" Waveform Type. This does only affect the Waveform Display as the audio output is as expected.
Image shows two cases (there are more) where the display is incorrect.
edit: Just noticed the "Kill High" button does not affect the Waveform Display.
Version
2.4.1, 2.6-alpha-136-g894e96f9b2 (main)
OS
Linux 6.11.9-arch1-1
The text was updated successfully, but these errors were encountered:
As far as I can tell, the issue is that the high kill does nothing and the middle kill kills high and mid bands. Lows work as expected. Affected waveform types are (Mixxx 2.4) "Filtered", "Filtered (GLSL)"m "Filtered (legacy, GL)", "RGB", "RGB (GLSL)", "RGB (legacy, GL)", "RGB L/R (GLSL)". Does that match your observation @g-rden?
EDIT: this list only applies to the mid+high issue... Others are also affected by missing eq high handling...
Bug Description
I won't go into depth describing the bevavior. Because either I am completely missing something and there's no bug or it is apperent that something is wrong and must be looked into further anyway.
BUG:
"Kill Mid" button and "High" knob affect each other in the Waveform Display when using "Filtered", "RGB" or "Stacked" Waveform Type. This does only affect the Waveform Display as the audio output is as expected.
Image shows two cases (there are more) where the display is incorrect.
edit: Just noticed the "Kill High" button does not affect the Waveform Display.
Version
2.4.1, 2.6-alpha-136-g894e96f9b2 (main)
OS
Linux 6.11.9-arch1-1
The text was updated successfully, but these errors were encountered: