I'll go your script a go when I get home, looks very cool! As far as I understand the "diffuse" channel could be an arbitrary channel right? My reason for defending classic broken out compositing is that me and many others find it easier to read and interpret the graph.
12 nov 2013 kl. 14:24 skrev Johannes Hezer <[email protected]>: > Hi Elias, > > I also ran into this situation... > > I wrote a little python script that should ease the pain a bit. > > http://pastebin.com/msENxWH3 > > if you put that into your menu.py you can give it a try.... > > import sr_channelView > [yourChoice].addCommand('set Viewer to node Channel', > 'sr_channelView.channelView()', 'v') > > What it does is when selecting a node that is on the "diffuse" channel, it > takes the currentViewer and inputs that node to the viewer on input 7 (I > hardcoded that) and sets the viewer to display the "diffuse" channel. > When pressing "V" again on the same node it toggles the viewer back to rgba... > Also when no node is selected it sets the currentViewer to RGBA... > > To me this changed a lot. It is not many lines of code but I would say I use > them a lot. > > Cheers > Johannes > > > > > On 11/12/2013 07:56 AM, Elias Ericsson Rydberg wrote: >> As much as I like the multichannel capabilities of nuke and exr. I prefer to >> shuffle out the channels I'll be using. There are scripts for splitting out >> all channels, search nukepedia. As long as you organise your nodes as you >> go, your script will be a lot easier to read for other artists and yourself. >> >> An other benefit of splitting out is that you don't run the risk of >> forgetting to switch channel in the viewer. I know I've confused myself in >> past by simply viewing the wrong channel. >> >> Cheers, >> Elias >> >> 12 nov 2013 kl. 04:41 skrev HSK <[email protected]>: >> >>> Hi again, >>> >>> quick question regarding using channels vs a spider web of nodes :) >>> >>> when going about multi-channel compositing... >>> >>> in order to have all your channels flow from beginning (ie from >>> multichannel exr) >>> to the end (write node) >>> >>> would I have to set "also merge - all" on all merge nodes? >>> >>> and all channels in write node? >>> >>> or is there another method? >>> >>> >>> _______________________________________________ >>> Nuke-users mailing list >>> [email protected], http://forums.thefoundry.co.uk/ >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >> >> >> ____ ESET 8964 (20131025) ____ >> The message was checked by ESET Mail Security. >> > > > -- > STUDIO RAKETE GmbH > Johannes Hezer, Compositing TD > Schomburgstr. 120 > D - 22767 Hamburg > > [email protected] > Tel:+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 / Hans-Martin Rickers > > Die Gesellschaft ist eingetragen im Handelregister des > Amtsgerichts Hamburg unter der Nummer HR B 95660 > USt.-ID Nr.: DE 245787817 > > > ____ ESET 8964 (20131025) ____ > The message was checked by ESET Mail Security. > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
