You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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!
The text was updated successfully, but these errors were encountered: