Feature: tactus marking #1021
Merged
Feature: tactus marking #1021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Renames 'weight' to 'tactus' (clapping rate). 'pulse' is another contender.)
Up til now
timeCatwas taking the top level sequence in mininotation as the tactus. Now you can mark where the tactus comes from. E.g."[a b c] d [^e f]"would have a tactus of 6, because the steps are 1/6th of cycle in the marked subsequence. If more than one is marked, then the lcm is taken, so"[^a b c] d [^e f]"would be the lcm of 9 and 6 which is 18.timeCat("[^a b c] d [^e f]", "g h")would then have a tactus of 20.. In practice, you'd probably only want to mark one subsequence.As things stand, if no tactus is marked, then it is taken from the toplevel sequence in mininotation.
*feels like a nice symbol for this. It must be specified at the start of a (sub)sequence, but probably is not practical as it's already used for density, and things quickly get unreadable:"[a b c*4] d*2 [*e*5 f]"=or'might be OK. Or we could use double brackets like `[a b c] d [[e f]]. Making mistakes in bracket matching is never fun in live coding though and that would make it worse.^would be a great choice, except that's proposed for memories in #513, as it is in tidal.update Ok changed to ^ in the PR and above examples to see how that feels. We'd have to change #513 to something else.