Hi Den, in my experience, if the data is non-image, then the metadata route is the best place to pass data through the pipe. If artists are likely to change or move the node setup, then your receiver node can simply pop up a warning if it expects some metadata and doesn't receive it.
Another way of doing things is having a node that looks up-stream for a particular "data source node" any time the original node's input is changed (although I don't know if the inputChanged event is fired in Python.) Searching the DAG upstream is relatively quick, and it only happens when the input is changed. (Although it won't fire if an upstream node's input is changed. You'd need to perform separate hash checking to test for that.) Hope that helps, Dan. On Fri, Sep 11, 2015 at 12:11 AM, Den Serras <[email protected]> wrote: > Hey all, I'm wondering if people have favorite ways of passing data down a > pipe, and the pros and cons. I am thinking of using metadata, though the > artist could strip it by accident. Then there's channels, with similar > problems, but the advantage of holding a lot more data in a matrix. I also > thought about having a separate database stored in root, but then I'd have > to parse the upstream which can get heavy. Could also use variables in > custom knobs or filenames, but that seems easy to get messed up if an > artist duplicates a knob or moves it. I'm sure I'm also missing some other > method... > > My goal is when the artist creates or moves an in-house Node it > auto-populates with data from upstream. > > Thanks! > Den > > > > _______________________________________________ > Nuke-python mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > -- Dan Ring, Ph.D. Senior Research Engineer The Foundry 5 Golden Square London W1F 9HT Tel: +44(0) 20 7479 4350 Web: www.thefoundry.co.uk Email: [email protected] The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
