New loop in point uses old loop out point
Bug #1800869 reported by
Matthew Nicholson
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
Using the Mixxx 2.2 beta. I was playing around with a loop and when setting a new loop in point, after disabling the loop, it would re-use the old loop out point and re-enable the loop. Setting a new loop in point when no loop is enabled should require a new loop out point too before the loop is enabled.
| Changed in mixxx: | |
| assignee: | nobody → andy (andy-xyz) |
| Changed in mixxx: | |
| status: | New → Confirmed |
Revision history for this message
| ronso0 (ronso0) wrote | #1 |
| Changed in mixxx: | |
| assignee: | andy (andy-xyz) → nobody |
| importance: | Undecided → Low |
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.
The downside of this change is that when loop_in is moved to adjust the current loop the loop_out is removed unexpectedly.
So maybe simply not (re-)enable a loop if it was disabled and previous loop_in/out is moved?