Comment 20 for bug 1481170

> If the user doesn't want the effect to fade out why does he/she turns the effect off in the first place?

Without any auto fade out the user has the full control, he can left click to disable the input and let the effect do what is should do without any input, or he can right click to stop the effect mediately. In case of echo, the user can also use the feedback knob and the dry/wet knob to control how the effect fades out.

For 1) this seams to be the default for implementation on competitor devices.

For 2) this is already possible with the dry/wet knob. Once the effect is fully dry, the user can right or left click the enable button.
For a bit crusher, the result will be the same since it has no internal buffer.

For 3) I understand the demand, but do not see how this will work without an additional preference option.
I cannot think about a way to predict the fade out behavior for any type of effect or use case.
It makes sense to add a preference or a parameter to set the fade out time individual.
The echo already has such an parameter (= feedback)

Has Traktor such a parameter?

How about postpone the decision, until we have merged the general "input_enabled" control and Nicus LV2 branch.
This way we have the chance to play with it before doing to much work.