> currently, there is no way to do dynamic patching in nova, mainly > because i haven't thought of a powerful way to do it. so on the side of > the language, patching features are still missing. > > i was thinking about using a messagebus like "thiscanvas" or > "thispatcher" or a |thispatcher| object in order to send messages to > the > canvas, which could be used for dynamic patching, but i haven't found a > good solution, yet. the problems are mainly:
hm some brainstorming is needed .. > - how do you get the message to the canvas (message bus or special > object?) an advantage of an object could be an outlet giving some feedback after doing a modification. i.e. it could output the uuid of the last created object. otherwise i see no dis/advantage about message bus vs. object do you? i think it's nice to have a similar syntax or at least similar wording as a patch file is written. in pd the msgs for dynamic patching are very close to patching with the mouse (i belive). > - how do you reference objects in a patch (pd uses integer indexes, > which are very fragile, dyn~ uses symbolic names, which it maintains > itself, nova internally uses uuids, but i doubt you would want to use > them for dynamic patching) i must admit don't dynamically create connections, i have very good experience with only creating/destroying abstractions that have an id as argument used for send and receive. all i need are some subpatches with unique names. modifying all patches / subpatches / abstractions from anywhere within nova would be awesome though, but then "this" would not work. i've seen uuid's are stored inside the .nbx file. to brainstorm and sketch some ideas how uuids could be used without directly touching them i would like to know: - should it be possible in nova to run multiple instances of the same patch? - is there some kind of name, id, $0, uuid for patches? (i didn't find that in the .nbx file) - is a object (uuid) a child of a patch (DOM style)? hopefully i can give some inputs/inspiration. > dynamically modifying the dsp graph is not a problem in nova, the > generation of the dsp chain is done in a background thread. yeah, that's good news! thanks, enrique _______________________________________________ nova-dev mailing list [email protected] http://klingt.org/cgi-bin/mailman/listinfo/nova-dev http://tim.klingt.org/nova
