3 ms·

> the gist of the idea is to have a timeline with dataflow elements embedded directly into it so that parts of the score can connect to other parts which happen

> the gist of the idea is to have a timeline with dataflow elements embedded directly into it so that parts of the score can connect to other parts which happen earlier / after. Why not allow nesting both ways? Why not allow timelines to be embedded within dataflow graphs, and then triggered by events that occur at arbitrary times? The outermost container can be a canvas embedding a single timeline if that's your thing. The constant-clockspeed model underlying all track-based sequencers and DAWs is a straitjacket. Arbitrary pauses, jam breaks, and rubato sections make more sense as time-free elements which exist between discrete timelines rather than as modifications to timelines.

jcelerier 6y ago
> Why not allow nesting both ways? Why not allow timelines to be embedded within dataflow graphs, and then triggered by events that occur at arbitrary times? The outermost container can be a canvas embedding a single timeline if that's your thing. That is the case in ossia, timelines can embed flow graphs, and flow graphs can embed timelines (and timelines can embed timelines and flowgraphs can embded flowgraphs... most things are composable). But, unlike Max / PD, cables can be connected across hierarchy levels so 99% of the time you don't need to resort to a specific "subpatch", you just connect things in the timeline itself. > and then triggered by events that occur at arbitrary times? However, the timeline has a built-in mechanism for that - see "open the floodgates" here : https://ossia.github.io/score/first_steps/time_approach/index.html https://ossia.github.io/score/first_steps/time_approach/inde... the doc is pretty outdated but this should give an idea :)