Node based DAW

Looks nice. That's essentially like our container structure only with much less parameters. Orb Composer followed a similar approach that fills sections with generative AI. 

If you add parameters and more manual control however, nodes alone don't suffice. You'll eventually end up with a quasi-linear presentation that's similar to Synfire.

Abstract graphical representations of music seem to appeal especially to tech and science people, I guess (me included). Although some musicians and composers are very enthusiastic about algorithmic and generative systems, the vast majority is more comfortable with straightforward writing, recording and editing stuff that emerges in their head.

Synfire is somewhere in between. I think it's important that it continues to support manual editing.

Thanks for sharing, but I may be missing some important point here. What new information exactly is presented in this graph view that Synfire's container nesting does not show? Do you feel this kind of representation is more concise and that way more easy to read for you?

BTW: I feel that Synfire's container structure is more powerful than this tree-like nesting for two reasons: 

1. The containers are represented in time, incl. supporting constraints like that subcontainers must be in strictly consecutive order.
2. The overall form does not need to be strictly hierarchically nested. It can be nested, and this can be very useful, but lower-level containers can also temporarily overlap the boundaries of two higher-level containers (i.e. no strict hierarchic nested), and that is also very useful. This is possible, because in addition to hierarchic nesting, all containers are arranged in time, and not just a tree-like data structure.

Again, I might well be missing something in your suggestion, but so far I clearly prefer what Synfire already offers over a tree-like form representation (and I am saying that as someone who spend a few years developing the latter ;-)