Closed KingaJanicka closed 6 months ago
Did some testing and confirmed it's not due to CPU load - we're sitting at comfy 38% atm
This still happens when the sequencer is paused, I'm guessing it's not the tick function then. Reducing the sample rate by half didn't seem to impact the glitching either
I've confirmed it's down to how tick()
and tick_callback()
is written - if I set the sequencer to fire a print()
instead I don't get the glitching
Fixed by bypassing the tick()
function and calling the callback directly
I think it's down to my janky implementation of Isobar timeline object in
sequencer.py
and the action/lambda. A less cobbled together code will run well