Replies: 7 comments
-
I'm not sure about the implementation, but would the "+" character be a reasonable choice? Carries the connotation of adding something, and also looks like a "t" for "tie". The main conflict might be confusion with its use in a numeric context, but other than being a potential part of a scientific notation representation of a |
Beta Was this translation helpful? Give feedback.
-
Maybe
Still, if we have decided a symbol, the actual implementation might be tricky, if not impossible without dirty tricks. But it would be immensely useful for reading and writing longer rhythms with syncopation |
Beta Was this translation helpful? Give feedback.
-
It would be possible to implement within the mini-notation parser, because that has access to the sequence structure before turning it into a pattern. It would indeed be problematic as a strudel function though. I think the answer to this kind of issue is to extract/formalise the workings of the mini-notation into DSL for patterns-as-sequences, that sits well with the current patterns-as-signals. I'm working on this.. |
Beta Was this translation helpful? Give feedback.
-
If/when there's a 'cyclewise mode' vs a 'beatwise mode', then it would make sense for |
Beta Was this translation helpful? Give feedback.
-
being able to unnest a pattern could be a step in the right direction to solve this: https://strudel.tidalcycles.org/?v5Dalvj2JIxH |
Beta Was this translation helpful? Give feedback.
-
ties can also be solved like this: #193 (comment) |
Beta Was this translation helpful? Give feedback.
-
as pointed out by @yaxu , the & symbol could be used for ties, like in bol processor: https://bolprocessor.org/polymetric-structure/ |
Beta Was this translation helpful? Give feedback.
-
It would be great if the mini notation somehow supported ties like this:
"[c3 e3] t"
"t" is just a placeholder here for a symbol that we haven't yet chosen. This would then have the output as:
without that, writing syncopations is really clumsy:
This works, but it's hard to read and you have to pack 2 "bars" into one package, at least if you want to do that inside a larger context. Here is a more real world example:
https://tinyurl.id/hTySd
I am pretty sure this feature cannot be implemented with patterns, as we have 2 (or more) seperate events that depend on each other. So the "e3" in the example has to "know" that the "t" is coming after it to have the proper duration. But this is impossible because the "e3" could probably be scheduled before the t.
TLDR to make this work, the tie notation needs to be converted to the clumsy notation before constructing the pattern.
For me, it would be the most logical to just use "_", but this would be a deviation from how it works in tidal for some cases.
Maybe "=".. ?
Beta Was this translation helpful? Give feedback.
All reactions