record_or_overdub commands dont work 1st time pressed
Posted: Sat Aug 21, 2010 6:23 pm
Hi - I love sooperlooper so far - Thank you!
I was really happy when I discovered the record_or_overdub* commands because I was trying to do that via OSC myself by first asking the channel how long the loop was and sending /sl/-3/hit record if it was 0 or /sl/-3/hit overdub if it was > 0 (BTW would this add noticeable lag time for a record start?)
But - when I am trying to control the SL AU plugin in mainstage I have noticed is that record_or_overdub commands (except the next and prev variants) dont seem to work 1st time pressed - instead you have to press once, then wait and press again to make them record or overdub. This seems to be the case when using either OSC and MIDI to trigger the command.
My current workaround to get rid of this behavior is by sending /sl/-1/hit record_or_overdub before I start using SL. But this is dangerous, because if I have already started a piece, it will actually start some of the loops recording/overdubbing AND does not apply to loops newly created on the fly.
Is this a bug? If not, is there a way around it?
And another thing while I'm at it, it appears that /set select_next_loop does not work over OSC - I've also tried adding values like /set select_next_loop 1 and /set select_next_loop 73, to no avail. The command works fine via MIDI, and I can use /set selected_loop_num x over OSC just fine.
I was really happy when I discovered the record_or_overdub* commands because I was trying to do that via OSC myself by first asking the channel how long the loop was and sending /sl/-3/hit record if it was 0 or /sl/-3/hit overdub if it was > 0 (BTW would this add noticeable lag time for a record start?)
But - when I am trying to control the SL AU plugin in mainstage I have noticed is that record_or_overdub commands (except the next and prev variants) dont seem to work 1st time pressed - instead you have to press once, then wait and press again to make them record or overdub. This seems to be the case when using either OSC and MIDI to trigger the command.
My current workaround to get rid of this behavior is by sending /sl/-1/hit record_or_overdub before I start using SL. But this is dangerous, because if I have already started a piece, it will actually start some of the loops recording/overdubbing AND does not apply to loops newly created on the fly.
Is this a bug? If not, is there a way around it?
And another thing while I'm at it, it appears that /set select_next_loop does not work over OSC - I've also tried adding values like /set select_next_loop 1 and /set select_next_loop 73, to no avail. The command works fine via MIDI, and I can use /set selected_loop_num x over OSC just fine.