Comment 4 for bug 1159243

Cool. Thanks. (The bug was set to "fix committed" - I'm assuming that was a mistake, so I changed it to confirmed.)

I think default behaviour for beatloops should probably be to start at the current play position if no loop is active, or at the currently active loop in point if a loop is active - so if the user activates different length beatloops one after the other, the loop length is changed by moving the loop_out point. (Except for not respecting manually set loop_in points as I've described above, this is the current behaviour).

It might also be interesting to provide a beatloop function that respects the end_point, and changes loop length by moving the in point. This might allow for a bit of a different effect.