rolling beatloop shouldn't alter beatloop size in spinbox

[ronso0]

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.

[Daniel Schürmann (daschuer)]

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://bugs.launchpad.net/mixxx/+bug/1367171

[Be (be.ing)]

> 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.

I don't think there should be a magic number where the behavior changes. Remember when I tried that with the loopauto_toggle Control in https://github.com/mixxxdj/mixxx/pull/1187 ? I think it could make sense to change the beatlooproll_X_activate Controls to not change the beatloop_size value though.

[Be (be.ing)]

> It looks like the underlying issue is that Mixxx only knows a single loop per track.

Yes, but solving that is a much bigger task than changing the behavior of the beatlooproll_X_activate Controls.

[Be (be.ing)]

https://github.com/mixxxdj/mixxx/pull/1428

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8947