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

Feature Request: Different clocks for each sub-sequencer in NoteSeqFu #77

Open
Chaircrusher opened this issue Jul 30, 2021 · 2 comments

Comments

@Chaircrusher
Copy link
Contributor

Instead of having a master clock and divisor controlling each voice (or voice cluster actually), add an optional clock input for each voice. Perfect for sending different 1Pat XOR clock patterns into each voice/cluster individually!

@jeremywen
Copy link
Owner

I like the idea. How would I deal with existing patches? Should this be a totally new module?

@Chaircrusher
Copy link
Contributor Author

That's an interesting question, one Andrew Belt might find interesting to answer. I don't know enough about the internals of Rack modules to know.

As a programmer -- the above lack of knowledge about Rack specifically stipulated -- I think if you read old patch JSON in, and there's no mention of the extra clock inputs, you'd just leave them unconnected.

If changing the number of ports changes a module such that it's no longer compatible with older patches, then I'd think about a second NoteSeqFu module. They could share most of the internal implementation.

Could this be done easier with an expander? Then NoteSeqFu would be compatible with older patches & the new thing with individual clocks would live in the expander. All you'd need in the Sequencer itself would be hooks to use the external clocks if the expander is present.

& again, this is a feature request not a feature deman.

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

No branches or pull requests

2 participants