This might be hard since the user might want to control when the effect consumes CPU.
Which such a approach the effect will always require CPU, unless it is able to reside to switch of itself.
Traktor should have the same issue, how it is solved there?
I am also struggling with our Mix (D/W) Knob. It is useless for many effects, but consumes always screen.
Maybe we have to rethink it and replace it with something more usable.
This might be hard since the user might want to control when the effect consumes CPU.
Which such a approach the effect will always require CPU, unless it is able to reside to switch of itself.
Traktor should have the same issue, how it is solved there?
I am also struggling with our Mix (D/W) Knob. It is useless for many effects, but consumes always screen.
Maybe we have to rethink it and replace it with something more usable.