Ok, so we actually running into the situation that Traktor also has, the need to configure the routing. We want originally avoid this. It would be great, if we can add rons0's valid use case in a smarter way.
From this point of view, it is a regression compared to Mixxx 2.0
You may put the echo to the quick effect knob. But there you cannot access the single echo parameter.
Let's summarize the issue:
You use a x-Fader for instance cutting like a scratch DJ, this does not work if the echo effect is applied to a track.
The post fader effect feature is also only audible, if you use fast cuts as well. Also with the use of the xFader.
So we have both valid cases, which can be even valid in the same set. I cannot think about a way to auto-detect this.
So we may consider to move the xfader always to the pre fader effect position without a config option. This allows both, pre fader and post fader behaviour, at the same time. Each with a dedicated control.
Ok, so we actually running into the situation that Traktor also has, the need to configure the routing. We want originally avoid this. It would be great, if we can add rons0's valid use case in a smarter way.
From this point of view, it is a regression compared to Mixxx 2.0
You may put the echo to the quick effect knob. But there you cannot access the single echo parameter.
Let's summarize the issue:
You use a x-Fader for instance cutting like a scratch DJ, this does not work if the echo effect is applied to a track.
The post fader effect feature is also only audible, if you use fast cuts as well. Also with the use of the xFader.
So we have both valid cases, which can be even valid in the same set. I cannot think about a way to auto-detect this.
So we may consider to move the xfader always to the pre fader effect position without a config option. This allows both, pre fader and post fader behaviour, at the same time. Each with a dedicated control.
What do you think?