engine.scratchEnable doesn't work adequate
Bug #1862086 reported by
mevsme
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I don't know how to explain this right
I have been struggling with this bug for quite a lot of time
During the investigation I have found one little bug in my code but this still happens no matter what.
Long story short
when I activate second identical controller and do engine.
and thus jog works without scratch
the second \ third \ n iteration - everything works fine
Revision history for this message
| mevsme (mevsme) wrote | #1 |
| Changed in mixxx: | |
| status: | New → Invalid |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #2 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
One more artifact of this.
When something is with scratch.... actually it is something wrong with engine. Because when I init two midi controllers, and don't use scratch but try to make engine.brake() - mixxx stops instead of braking.