Hi Frank, this looks awesome. I'm a pipeline TD at our studio and I'm wondering if perhaps one would dare to have nuBridge-downloaded scripts installed in one central place? For example, we have a place on our app server, /usr/nuke/scripts, where anyone can drop scripts and they will become available for everyone, including the farm. This just means that they are available in the nuke path, not that they have been sourced.
Now, we're not Weta, so we notice straight away if something fishy would be going on, and we would know who did it ;) And for the record, this has never been a problem. But when I've been on vacation, users have downloaded scripts installed in the pipeline themselves. Which is always nice (for me). And almost a feature. It would be nice to have the possibility to have nuBridge put its scripts straight in there, perhaps if a certain environment variable is found? I'm thinking NUBRIDGE_PATH=//server/share/folder or something. What do you think? Also, if you published guidelines on how a script should get executed to maximize support with nuBridge, at least I would take the time to update my scripts which are on there. Looking forward to implementing this for our artists! Good job! // F On Fri, Jan 29, 2016 at 4:58 PM Michael Garrett <michaeld...@gmail.com> wrote: > Well said Frank - and thanks for this monumental effort. > > On 27 January 2016 at 21:57, Frank Rueter|OHUfx <fr...@ohufx.com> wrote: > >> Yeah, I'm fully aware of that but decided a long time ago that I don't >> care about those kind of setups any longer. >> Secrecy and security have reached such paranoid and counter productive >> levels in our industry that I won't try and accommodate it anymore. It >> takes the fun out of collaboration and team work. >> >> Years ago, I got grilled just for discussing the concept of the nuBridge >> with people from big studios which was enormously frustrating. All they >> cared about was full control over what the artists do and don't do, rather >> than exploring ways that could benefit everybody involved. >> >> Also, I wouldn't call it useless, since you could still run it on >> dedicated internet machines as a download hub. In fact, if there was >> interest for that sort of application, i'd be happy to explore features to >> support it. >> But I guarantee that politics will get in the way of such a set up. >> >> Sorry for the rant, but I have had a gut full of politics getting in the >> way of good and enjoyable work, and the fact that the vfx houses don't >> stand up to the increasing studio BS. >> >> >> >> >> >> On 01/28/2016 03:42 PM, John Vanderbeck wrote: >> >> Sadly useless for many as more and more studios force artists and >> production machines to be disconnected from the Internet. It looks amazing >> though. >> >> - John Vanderbeck >> - http://www.johnvanderbeck.com >> >> On Wed, Jan 27, 2016 at 6:09 PM, Ivan Busquets <ivanbusqu...@gmail.com> >> wrote: >> >>> Great idea, very useful, and looks very polished. >>> >>> Thanks for all the work that went into it, Frank! >>> >>> On Wed, Jan 27, 2016 at 6:01 PM, Rich Bobo < <richb...@mac.com> >>> richb...@mac.com> wrote: >>> >>>> Cool!! >>>> >>>> Rich >>>> >>>> >>>> Rich Bobo >>>> Senior VFX Compositor >>>> Armstrong White >>>> Email: rich.b...@armstrong-white.com >>>> http://armstrong-white.com/ >>>> >>>> Email: richb...@mac.com >>>> Mobile: (248) 840-2665 <%28248%29%20840-2665> >>>> Web: http://richbobo.com/ >>>> >>>> "If I had my life to live over again, I would have made a rule to read >>>> some poetry and listen to some music at least once a week." >>>> - Charles Darwin >>>> >>>> >>>> >>>> >>>> >>>> On Jan 26, 2016, at 3:23 PM, Frank Rueter|OHUfx < <fr...@ohufx.com> >>>> fr...@ohufx.com> wrote: >>>> >>>> With over 1000 tools in the database it's time for something like this: >>>> http://www.nukepedia.com >>>> >>>> >>>> >>>> -- >>>> <Mail Attachment.png> <http://www.ohufx.com/> *vfx compositing >>>> <http://ohufx.com/index.php/vfx-compositing> | workflow customisation and >>>> consulting <http://ohufx.com/index.php/vfx-customising> * >>>> _______________________________________________ >>>> Nuke-python mailing list >>>> Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>>> >>>> >>>> >>>> _______________________________________________ >>>> Nuke-python mailing list >>>> Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>>> >>>> >>> >>> _______________________________________________ >>> Nuke-python mailing list >>> Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>> >>> >> >> >> _______________________________________________ >> Nuke-python mailing listnuke-pyt...@support.thefoundry.co.uk, >> http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> >> >> >> _______________________________________________ >> Nuke-python mailing list >> Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >> >> > _______________________________________________ > Nuke-python mailing list > Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >
_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
