I’m fascinated by seeing how far MuBu went.
For a new art project, I have to design a live performance system based on a graph.
The graph description is not yet defined, but we can imagine a graph, with branches.
Each branche has to store values evolving all along the branch itself and sporadic events too.
I think MuBu could really fit this requirement as a branch could be implemented like this;
- continuous evolving parameters could be tracks
- sporadic events could be markers (I don’t know if we can have different markers layers, or if a marker can have multiple properties
I think it fits well.
I’d need a graph.
So This graph would mean n-branches.
I guess I can design a system based on branches names, a branch refers to stored data, I “load” a branch it loads these data and I can move all along my branch reading/recalling and interpolating data.
Then, when I go to the next branch, it switches, load the new branch’ data etc.
Is there a better way to do this as a graph ?
I’d have something like only 20 evolving tracks for each branch + 50 markers MAXIMUM.
My main spotted and imagined issues:
- loading time (getting everything in RAM could be better but heavy, maybe). I can preload adjacent branches etc but I’m afraid of issues especially while unloading (would it really unload?)
- easy way to “join” my tracks’ value across branches. I mean: I create a track with a starting value 0.5 and I evolve, evolve, ending at 0.9. I do that for all my branches with different values. I’d need to run a script that would take the previous branch’ end value to 0.5 and the next branch’ start value to 0.9 … avoiding jump. (I know I could interpolate for big jump using a smoothing line… but…)
ANY ideas would be very appreaciated