5 ms·

Had the chance to meet Miller as he was part of my phd jury, as most of the time for persons of this caliber and with such a large impact, he was super nice and

Had the chance to meet Miller as he was part of my phd jury, as most of the time for persons of this caliber and with such a large impact, he was super nice and humble. Regarding > There’s a problem in Max and in Pure Data, which is that you’re writing these things in terms of how they act. You’re making an instrument. But someone wants to store a score in the thing, and then do things that refer to objects in the score. So far, there’s no good design — or at least I haven’t seen a good design — that actually marries these two ideas in a single environment that works. I'm working towards it in https://ossia.io https://ossia.io - 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. This allows to easily make instruments that evolve in time... though most of its users use it to make scores instead of instruments. (this leads to trying to answer the question "what happens when two connected nodes of a dataflow graph execute for t=[0; 5seconds] for the source node, and t=[3; 7seconds] for the sink node").

qmmmur 7y ago
I really love the idea of ossia but it had some rough edges when I gave it a try. I'll give it a revisit sometime soon :)
- jcelerier 7y ago
  definitely, I've been working on a new v. for almost a year but hard to find the time to fix things :p
rectang 7y ago
> 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 7y 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 :)

qmmmur 7y ago

I really love the idea of ossia but it had some rough edges when I gave it a try. I'll give it a revisit sometime soon :)

jcelerier 7y ago
definitely, I've been working on a new v. for almost a year but hard to find the time to fix things :p

rectang 7y ago

> 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 7y 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 :)