javascript mapping bug in [EffectRack1_EffectUnitN], super1
Bug #1607127 reported by
Sébastien BLAISOT
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Invalid
|
Undecided
|
Unassigned |
Bug Description
In Javascript, this doesn't work:
engine.
whatever the value (>0), this has no effect.
But if first set super1 to zero like
engine.
engine.
This works.
You need to "reset" super1 to 0 before being able to actually set it.
Only the first time.
The same applies to all EffectUnit
Tested on mixxx 2.0.0 (64 bits) on windows 10 (64 bits).
summary: |
- javascript mapping bug in [EffectRack1_EffectUnitN]super1 + javascript mapping bug in [EffectRack1_EffectUnitN], super1 |
To post a comment you must log in.
It sounds like an softtakover issue.
If you have not not control the CO before, the first value is ignored.
This is required to detect the knob turning direction with the second value.
If the second value crosses the current value the control "Snaps in".
You can bypass this behavior by engine. setParameter( ).
But be aware that this leads probably to unwanted value jumps after using the GUI controls.
Does this explain your issue?