Hi Johannes, I was trying to avoid using templates for the risk that new code might not get pushed if the developer doesn't remember to make the new template; so building the script on demand with the command line made more sense to me. But I can work around the template shortcoming.
Thanks! Den On Sat, Dec 5, 2015 at 5:50 PM, Johannes Hezer <[email protected]> wrote: > Hey Den, > > what Jimmy said actually should work. > I still dont quite understand what you are trying todo. > > You create a template part of a script for a specific show. The show > requirements change and now this template part needs to changed and updated > in all existing comps too ?! That sounds like the perfect place for a > gizmo.... > Or is it that each show starts with a template and in that template are > reads and writes and whatnot and you are looking for a way to populate it > more automated ? > But each show needs to have its own section in it ? > Either way when launching nuke with -x and point to a python file you can > do anything in there. > Maybe you can explain a bit more in detail where you are stuck? > > And with knob defaults this also depends on whether you are using > nuke.nodes.Blur or nuke.createNode('Blur') > (just as an example) > nuke.nodes.Node will never built upon any knob defaults, but > nuke.createNode('Node') does respect your set knobdefaults.... so maybe > this already helps. > > Cheers > Johannes > > > > > > Am 12/4/15 um 23:56 PM schrieb Den Serras: > > can't... edit... emails... Found that Nuke 9 *CLI* didn't load my > callbacks > > On Fri, Dec 4, 2015 at 2:50 PM, Den Serras <[email protected]> wrote: > >> Hey Hilsen - that was my original setup. But I found that Nuke 9 didn't >> load my callbacks and node defaults which I use to customize the raw >> script, even though they're started by the init.py (not the menu.py). >> >> What I'm aiming for is to solve a workflow problem - for programmers to >> not have to remember to push changes by making a new template with GUI nuke >> or update a separate script. I'm thinking maybe I'll have a .bat which >> updates the template automatically by launching the GUI nuke and a .py >> script which resaves it. That bat can be run any time the code is updated >> in GIT... >> >> On Wed, Dec 2, 2015 at 10:23 PM, Jimmy Christensen < <[email protected]> >> [email protected]> wrote: >> >>> Have you thought about opening a .py file with the Nuke command line? It >>> will simply execute it. I believe you can even read in the template file at >>> the very beginning and end with a nuke.scriptSaveAs(location). >>> >>> I use this to batch convert images etc. The whole script is built from >>> scratch using python (from inside nuke). >>> >>> Hilsen >>> Jimmy Christensen >>> Developer >>> Ghost A/S >>> >>> >>> On 01/12/15 17:38, Den Serras wrote: >>> >>>> Hi all, >>>> >>>> Due to our pipeline, we have to create the Nuke file for the artist. We >>>> currently create a template which is duplicated and moved into the >>>> correct spot, but I'd prefer to do it more dynamically so every time I >>>> push a change to the setup I don't have to generate a new file. I tried >>>> launching the CLI and then saving the file, but none of my init scripts >>>> that actually modify the file seem to be running in the CLI. Don't know >>>> if I'm doing something wrong or this method won't work. Anyone have a >>>> dynamic way to create a script, or are those who prebuild scripts always >>>> using templates? >>>> >>>> Thanks! >>>> Den >>>> >>>> >>>> _______________________________________________ >>>> Nuke-python mailing list >>>> [email protected], http://forums.thefoundry.co.uk/ >>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>>> >>>> _______________________________________________ >>> Nuke-python mailing list >>> [email protected], http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>> >> >> > > > _______________________________________________ > Nuke-python mailing [email protected], > http://forums.thefoundry.co.uk/http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > > > > > ____ ESET 12673 (20151204) ____ > The message was checked by ESET Mail Security. > > > > -- > STUDIO RAKETE GmbH > Johannes Hezer, Compositing TD & Stereoscopic SV > Schomburgstr. 120 > D - 22767 Hamburg > [email protected]:+49 <+49> (0)40 - 380 375 69 - 0 > Fax:+49 (0)40 - 380 375 69 - 99 > > ------------------------------------------------------ > Pflichtangaben laut Handelsgesetzbuch und GmbH-Gesetz: > > STUDIO RAKETE GmbH > Schomburgstr. 120 D - 22767 Hamburg > www.studiorakete.de / [email protected] > > Geschaeftsfuehrer: Jana Bohl > > Die Gesellschaft ist eingetragen im Handelregister des > Amtsgerichts Hamburg unter der Nummer HR B 95660 > USt.-ID Nr.: DE 245787817 > > > > ____ ESET 12677 (20151205) ____ > The message was checked by ESET Mail Security. > > _______________________________________________ > Nuke-python mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > >
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
