forgot to mention, the same Op allows you to normalize the channel too. On Sat, Oct 13, 2012 at 3:52 PM, Mike Wong | CityU < [email protected]> wrote:
> Hope I am following the point correctly, just want to share that upcoming > Escher has a depthOp which can go through the input frame by frame to > obtain sequence-wide min/max values of a channel and the min/max values of > each frame is also keyframed into a float-pair. Is it useful for the issue > raised ? > > mike > > On Sat, Oct 13, 2012 at 3:05 PM, Diogo Girondi <[email protected]>wrote: > >> For sure we would. >> >> I once discussed an idea with Foundry folks of making the IP button work >> as a conector to a individual DAG for the Viewer where you could build up a >> trees like any other. This would allow you to use a arbitrary number of >> nodes without having to group them or having to cope with loose nodes on >> your project DAG. >> >> Mainly because even though I love the concept of the IP I never been too >> fond of loose nodes with no visible connection in a tree. Which is >> something Fusion has and annoys quite a bit. >> >> So we would basically have a number of "viewer slots" where each slot is >> a DAG. These slots could be set, accessed and maintained from the project >> root, or some more convenient place. And the IP button on the viewer would >> become a IP slot selector instead of just a on/off switch. >> >> This would allow us to have multiple IPs at our disposal at any time >> without having to rename a viewer's input process or the IP nodes. And we >> would still be able to share a IP (slot) across viewers and of course be >> able to set these from a menu.py and whatnots. All this without crowing the >> viewer's menu even more. >> >> Not to mention that this "slot selector" could be made in a way to allow >> for multiple selections, thus allowing people to activate a guide IP, a >> normalizer IP and a CC IP all at the same time without having to combine >> multiple nodes under a single IP node that is lost in a tree. >> >> But then they did the custom viewer process and this became questionable. >> >> >> -diogo >> >> On Sat, Oct 13, 2012 at 3:16 AM, Frank Rueter <[email protected]>wrote: >> >>> you'd still have to use up the input process slot >>> >>> >>> On 13/10/12 7:13 PM, Diogo Girondi wrote: >>> >>> I believe you could use something like this: >>> >>> Group { >>> name dNormalizer >>> tile_color 0x7aa9ffff >>> selected true >>> addUserKnob {20 dnormalizer l dNormalizer} >>> addUserKnob {26 tx l "" +STARTLINE T "Nothing to see here"} >>> } >>> Input { >>> inputs 0 >>> name Input >>> xpos -450 >>> ypos -312 >>> } >>> Dot { >>> name Dot2 >>> xpos -416 >>> ypos -244 >>> } >>> set N23ae8440 [stack 0] >>> Dot { >>> name Dot1 >>> xpos -292 >>> ypos -244 >>> } >>> set N23aeb250 [stack 0] >>> Dilate { >>> size {{input.format.w i}} >>> name Dilate1 >>> label Max >>> xpos -379 >>> ypos -166 >>> } >>> NoOp { >>> name Max >>> xpos -379 >>> ypos -120 >>> addUserKnob {20 User} >>> addUserKnob {18 max l Max:} >>> max {{"\[sample this.input r 0 0]" i} {"\[sample this.input g 0 0]" i} >>> {"\[sample this.input b 0 0]" i}} >>> } >>> push $N23aeb250 >>> Dilate { >>> size {{input.format.w*-1 i}} >>> name Dilate2 >>> label Min >>> xpos -262 >>> ypos -165 >>> } >>> NoOp { >>> name Min >>> xpos -262 >>> ypos -119 >>> addUserKnob {20 User} >>> addUserKnob {18 min l Min:} >>> min {{"\[sample this.input r 0 0]" i} {"\[sample this.input g 0 0]" i} >>> {"\[sample this.input b 0 0]" i}} >>> } >>> push $N23ae8440 >>> Grade { >>> blackpoint {{Min.min i}} >>> whitepoint {{Max.max i}} >>> white_clamp true >>> name Grade1 >>> xpos -450 >>> ypos -13 >>> } >>> Output { >>> name Output1 >>> xpos -450 >>> ypos 92 >>> } >>> end_group >>> >>> Wouldn't it work? >>> >>> >>> cheers, >>> diogo >>> >>> On Sat, Oct 13, 2012 at 2:47 AM, Frank Rueter <[email protected]>wrote: >>> >>>> Same. It would indeed be very helpful. Has somebody sent in a request >>>> yet? >>>> >>>> >>>> >>>> On 13/10/12 6:54 AM, Holger Hummel|Celluloid VFX wrote: >>>> >>>>> yes, you can. >>>>> BUT: >>>>> - it needs manual work: you need to know/find the min/max values. they >>>>> change from pass to pass, actually in most cases from frame to frame. >>>>> - it's quicker when you can just click on button to toggle this. also >>>>> because it does not conflict with some other VIWER_INPUT that might be >>>>> active. >>>>> >>>>> so +1 from me making this a feature request >>>>> >>>>> - Holger >>>>> >>>>> >>>>> jbidwell wrote: >>>>> >>>>>> You can make a grade and group it, then name it "VIEWER_INPUT". The >>>>>> viewer will use that grade in the viewer whenever the IP button is >>>>>> active. >>>>>> >>>>>> - JB >>>>>> >>>>>> ------------------------------------------------------------------------ >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>> >>> >>> >>> _______________________________________________ >>> Nuke-users mailing [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 >>> >> >> >> _______________________________________________ >> 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
