Disabled effect in chain should bypass instead of silence
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
Medium
|
Jan Ypma |
Bug Description
I'm using the Deere skin, and trying to set up some advanced effects. To this end, I'm putting 3 effects into one effect chain, e.g. Bitcrusher -> Echo -> Reverb.
I'm hitting seemlingly a bug in the audio processing under the following conditions:
- There is more than 1 effect in the chain
- The first effect is off, the second effect is on
- The Dry/Mix knob is anywhere less than 100%, e.g. 95% to the right
Under these conditions, no dry signal hits the second effect AT ALL. Only an attenuated input signal is present, no effect is heard. Now, when the Dry/Wet is moved to 100%, the sound does hit the second effect (full-on, of course). Moving Dry/wet slightly to the left again kills all FX input signal. Any reverb or echo tail does ring out.
This bug is not present when effect 1 is also on; dry/wet then works as is expected (that is, as it would in a DAW).
So it seems that:
- When Dry/Wet is at 100%, switching effect 1 off is a "bypass" of the effect, routing the input signal on to the next effect on the chain
- When Dry/Wet is <100%, switching effect 1 off kills the complete remainder of the effect chain
Forum link: http://
Changed in mixxx: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → 2.1.0 |
tags: | added: effects |
Changed in mixxx: | |
status: | Confirmed → Fix Committed |
assignee: | nobody → Jan Ypma (jypma) |
Changed in mixxx: | |
status: | Fix Committed → Fix Released |
I think I found the problem, looks like an oversight in the initial effects code.
PR with a possible fix is here: https:/ /github. com/mixxxdj/ mixxx/pull/ 989