interceptintercept
I'm playing around with loop_button and have noticed that there's a ~4 second timeout if the button isn't triggered a second time, preventing it from being used for medium/long loops. Is there any way to bypass this timeout (without manually recreating the loop_button logic)?
Thanks!
b8322
Thanks!
b8322
Posted Mon 23 Sep 24 @ 3:44 am
locoDog
It's not time based, it's beats, 8 to be exact.
Posted Mon 23 Sep 24 @ 4:11 am
interceptintercept
Hi Loco,
I thought it was based on beats at first, but changing the bpm doesn't affect the max length. 120bpm = 8 beats = 4s, 60 bpm = 4 beats = 4 seconds, 240 bpm = 16 beats = 4s.
Either way, there's still an artificial limitation I'd like to bypass :)
I thought it was based on beats at first, but changing the bpm doesn't affect the max length. 120bpm = 8 beats = 4s, 60 bpm = 4 beats = 4 seconds, 240 bpm = 16 beats = 4s.
Either way, there's still an artificial limitation I'd like to bypass :)
Posted Mon 23 Sep 24 @ 12:58 pm
locoDog
Looks like you might have to fashion something yourself.
I'd still probably have some sort of limit in there, just in case you bail on the idea mid setting.
cycle a variable, if 1 ? loop in, start a rsi looking for loop engaged in X seconds, if so ? nothing : if not return var to 0 : if 2 ? set loop out, start a rsi watching for external loop 0, if so ? return var to 0, stop rsi : if no loop 0 do nothing : if var 0 ? end rsi, loop exit
something like that.
I'd still probably have some sort of limit in there, just in case you bail on the idea mid setting.
cycle a variable, if 1 ? loop in, start a rsi looking for loop engaged in X seconds, if so ? nothing : if not return var to 0 : if 2 ? set loop out, start a rsi watching for external loop 0, if so ? return var to 0, stop rsi : if no loop 0 do nothing : if var 0 ? end rsi, loop exit
something like that.
Posted Mon 23 Sep 24 @ 4:20 pm