There's a few control messages I really miss:
record (1/0) - it would be great to be able to force it to be recording or not. If I want to do anything that has takes control over recording, I need to compare current state and desired state to see if I should send a record message.start_capture or similar. At the moment, it seems like I have to know the loop length in advance. So I end up with a hack where I set the loop length to be really long, time the recording, and then setloop to that length. It works, but it's pretty hinky. I think it just needs one message to start recording an unknown length loop, as after that play or record as usual could start playing, but it would be very useful to have a message come out somewhere to say how long the final loop is.clear to clear the buffer. Of course, can be done with the buffer object, but it would make things cleaner to do it directly through karma~
There's a few control messages I really miss:
record (1/0)- it would be great to be able to force it to be recording or not. If I want to do anything that has takes control over recording, I need to compare current state and desired state to see if I should send arecordmessage.start_captureor similar. At the moment, it seems like I have to know the loop length in advance. So I end up with a hack where I set the loop length to be really long, time the recording, and thensetloopto that length. It works, but it's pretty hinky. I think it just needs one message to start recording an unknown length loop, as after thatplayorrecordas usual could start playing, but it would be very useful to have a message come out somewhere to say how long the final loop is.clearto clear the buffer. Of course, can be done with the buffer object, but it would make things cleaner to do it directly through karma~