diff options
| author | Jake Zerrer <him@jakezerrer.com> | 2025-11-21 11:51:47 -0500 |
|---|---|---|
| committer | Jake Zerrer <him@jakezerrer.com> | 2025-11-21 12:00:35 -0500 |
| commit | 183f346fa51a6a60c5550e9906ef885fd23c16fc (patch) | |
| tree | 4f4d76554fdf9d3aa5632e9abec45c8d40606feb | |
| parent | 52a68dc56db4dbf6c1295d3122dcfce32c1b55e5 (diff) | |
Update devlog
| -rw-r--r-- | DEVLOG.md | 29 |
1 files changed, 29 insertions, 0 deletions
@@ -282,3 +282,32 @@ part of the query? Right now, phrases are eagerly composed together. This means that if you redefine part of a piece, you have to redefine all of its dependents, too. This might make interactive development annoying. + +# November 21st, 2025 + +## Key insights + +There is no need for a minimum rhythmic division! Just use fractions of a beat, +all the way down to the time-object / interval tree. It seems obvious in +hindsight. + +## New ideas + +Phrases can be named (at invocation time, not definition time). This will allow you to quickly jump to a phrase. + +Then, in the UI, we can the tell you where you are and where you can jump to. + +Note that since phrases can be nested, phrase names are concatenated into a +vector of [outer inner], arbitrarily many deep. + +Looping can be enabled / disabled for a named phrase. + +When the playhrad rolls into an enabled loop, it will play until the end of the +phrase, at which point it will jump the timeline back to the start of the looped +phrase. This works with nested phrases / loops. If nested loops are enabled, the +innermost loop takes precedence. + +## TODO: +Document the bug that could occur if two tim object flows invocations shared an identity +Write down idea about the difference between a tree and a dag +Write down the static topology decision / summarize theory of time. |
