rolling beatloop shouldn't alter beatloop size in spinbox
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
This is a bug only if you use beatlooproll like I do:
I have 4 buttons on my controller to activate 4 rolling beatloops (1/4, 1/2, 1, 2 beats) and it's fun to use them as a stutter effect and for 'glitchy transitions'. Another button is mapped to beatloop_activate and uses beatloop_size.
Any rolling loop deletes/overwrites the last enabled loop, places loop markers on the waveform and alters beatloop_size shown by the spinbox.
Point is, I don't want to recall those spontaneous, tiny rolling loops later, more likely they would overwrite an intro loop that I'd like to save.
Would it make sense to ignore *rolling* beatloops that are shorter than -let's say 1 beat or ignore them generally? Manually set and normal loops by any size would still saved, of course.
| description: | updated |
| Changed in mixxx: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| Daniel Schürmann (daschuer) wrote | #1 |
| Be (be.ing) wrote | #2 |
| Be (be.ing) wrote | #3 |
| Changed in mixxx: | |
| importance: | Wishlist → Low |
| assignee: | nobody → Be (be.ing) |
| milestone: | none → 2.1.0 |
| Changed in mixxx: | |
| status: | Confirmed → In Progress |
| Be (be.ing) wrote | #4 |
| Changed in mixxx: | |
| milestone: | 2.1.0 → 2.2.0 |
| Changed in mixxx: | |
| milestone: | 2.2.0 → 2.3.0 |
| Changed in mixxx: | |
| assignee: | Be (be.ing) → nobody |
| milestone: | 2.3.0 → none |
| Changed in mixxx: | |
| status: | In Progress → Confirmed |
| Swiftb0y (swiftb0y) wrote | #5 |
| lock status: | Metadata changes locked and limited to project staff |
It looks like the underlying issue is that Mixxx only knows a single loop per track.
Mabe this can be solved along with a new CUE editing GUI like proposed here:
https:/