| 2017-10-06 21:33:33 |
ronso0 |
description |
This is a bug only if you use beatlooproll like I do:
I have a 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 '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. |
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. |
|
