Using loop_move control can interupt playback, needs track eject to restore deck state
Bug #1424057 reported by
jus
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Fix Released
|
High
|
Owen Williams | ||
Bug Description
Latest master OSX 10.9.5
Train wreck alert
Using the loop_move controls ( currently in Deere skin, or mapped to a controller) you can bring a playback to a halt / confuse the decks state. You can not safely use the deck until you eject the old and load a new track to the deck.
All you have to do is set a loop and press the loop_move control. Bug occurs semi-random when moving loop fore- or backwards. Does not matter if quantization is activated.
See screencap
| Changed in mixxx: | |
| assignee: | nobody → Owen Williams (ywwg) |
| importance: | Undecided → High |
| milestone: | none → 1.12.0 |
Revision history for this message
| Owen Williams (ywwg) wrote | #2 |
Revision history for this message
| Owen Williams (ywwg) wrote | #4 |
Revision history for this message
| Owen Williams (ywwg) wrote | #5 |
| Changed in mixxx: | |
| status: | New → Fix Committed |
| Changed in mixxx: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #7 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
What version of mixxx is this? Is it the alpha, or is it a trunk build? and if it's a trunk build, which number?