Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Improve documentation around Rhythm values
See original GitHub issueI see that to specify a Rhythm we can either use absolute values (time in seconds) or a kind of rhythmic notation, which is an integer + n or t
I see it has to do with compound times, and by testing it, I saw that #n represents a time span of 2/# seconds, and #t represents a time span of 4/(3#) seconds. So if we have a 4t and a 2n, the first one will make 3 beats for every beat of the second one.
However, I can’t figure out what’s the logic behind this, or I can’t find any reference on this notation (I don’t know how is it called). Or also why we don’t have a 2t or 1t. It would be good to have a bit more documentation around this.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
All great points, I will take a pass at this and hopefully shed some light on the notation!
Ha you’re totally right. Nice catch!