Skip to content
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 engines - clock by trigger or clock mult/divide #118

Open
eh2k opened this issue Dec 13, 2024 · 1 comment
Open

sequencer engines - clock by trigger or clock mult/divide #118

eh2k opened this issue Dec 13, 2024 · 1 comment

Comments

@eh2k
Copy link
Owner

eh2k commented Dec 13, 2024

I would like to make a request on the sequencers machines. Rather than advance with respect to the clock, would it be possible to have them advance on a trigger? This would allow for greater flexibility in interacting with the sequencers, as well as driving it from external clocks. Alternatively, a clock mult/divide to better separate them from the 4PPQN signal could be equally helpful.

Originally posted by @d-huck in #1 (comment)

@eh2k
Copy link
Owner Author

eh2k commented Dec 13, 2024

hi @d-huck

thanks for the suggestion.

I need to think this through. I wanted to add a swing to the global clock next. But the clock mult/devider also makes sense. Alternative clock with trigger wouldn't really be a big deal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant