-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sequencer.reset doesn't propagate to backend #46
Comments
Thanks for the report, a fix has been committed. I'm not sure if you can get a steady beat that way - it depends on the system scheduler. But it's a fun experiment. I've been thinking about looping in |
yeah, under some load, it losses precision. I made it work by having a whole different idea: a
building on my previous idea: simply resetting all units after a certain time gives a good "physical sequencer feel" IMO. that would require to keep events around so maybe update this argument to smth like |
A looping unit is a nice idea too, I'm putting it on the TODO list with sequencer looping. |
when using a "split" sequencer, it doesn't forward the reset to the backend.
I'm adding a PR showing that in tests.
I was thinking of looping the sequencer quite regularly, such as every seconds, with smth like the following but it doesn't behave as expected.
The text was updated successfully, but these errors were encountered: