I reported that more than a year ago, exactly the same problem you have. I
hope a solution come someday...

2011/10/6 <nuke-dev-requ...@support.thefoundry.co.uk>

> Send Nuke-dev mailing list submissions to
>        nuke-dev@support.thefoundry.co.uk
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
> or, via email, send a message with subject or body 'help' to
>        nuke-dev-requ...@support.thefoundry.co.uk
>
> You can reach the person managing the list at
>        nuke-dev-ow...@support.thefoundry.co.uk
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Nuke-dev digest..."
>
>
> Today's Topics:
>
>   1. ValueProvider example (Stephen Newbold)
>   2. [Nuclear blast from the past] - engine() ChannelMask
>      weirdness (Paolo Berto)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 05 Oct 2011 12:43:52 +0100
> From: Stephen Newbold <stephe...@moving-picture.com>
> Subject: [Nuke-dev] ValueProvider example
> To: Nuke plug-in development discussion
>        <nuke-dev@support.thefoundry.co.uk>
> Message-ID: <4e8c42f8.8050...@moving-picture.com>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> Hi,
>
> The NDK docs say there is an example of the use of valueProviders but I
> can't see this anywhere. Anyone know if this is hidden away somewhere or
> have an example I can look at?
>
> The NDK contains a ‘ValueProviderOp’ sample which demonstrates a simple
> case using a ValueProvider to link a /Color_knob/
> <
> http://docs.thefoundry.co.uk/nuke/63/ndkdevguide/knobs-and-handles/knobtypes.html#knobs-knobtypes-color-knob
> >
> and a /MultiFloat_knob/
> <
> http://docs.thefoundry.co.uk/nuke/63/ndkdevguide/knobs-and-handles/knobtypes.html#knobs-knobtypes-multifloat-knob
> >.
> If you’re looking to link non-axis knob types, you may want to check out
> the /The knob_changed() Method/
> <
> http://docs.thefoundry.co.uk/nuke/63/ndkdevguide/knobs-and-handles/knobchanged.html#knobs-knob-changed
> >
> section.
>
> Cheers,
> Steve
>
> --
> Stephen Newbold
> Compositing Lead - Film
> MPC
> 127 Wardour Street
> Soho, London, W1F 0NL
> Main - + 44 (0) 20 7434 3100
> www.moving-picture.com
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 6 Oct 2011 18:41:47 +0800
> From: Paolo Berto <pbe...@jupiter-jazz.com>
> Subject: [Nuke-dev] [Nuclear blast from the past] - engine()
>        ChannelMask     weirdness
> To: Nuke plug-in development discussion
>        <nuke-dev@support.thefoundry.co.uk>
> Cc: The Foundry Support <supp...@thefoundry.co.uk>
> Message-ID:
>        <CALD5EGwW-BYJE9LqJO5Yj+BwOfz0=694b81v6qhs6_rpraa...@mail.gmail.com
> >
> Content-Type: text/plain; charset=UTF-8
>
> Adding in cc Foundry's support & the oracle (Jonathan).
>
> This oldie but goldie needs some love: it is just too common to have
> many channels in a node nowadays, and suddenly requesting multiple of
> them rather than the only one needed is a total waste.
>
> Could some Nuklear Scientist @ Foundry assign a bug ID and look into this?
>
> Best,
> Paolo
>
> On Wed, Jul 28, 2010 at 6:16 AM, Moritz Moeller
> <realr...@virtualritz.com> wrote:
> > My plugin has a lot of channels users can request. Now I use a Shuffle
> > after to request individual ones while testing.
> >
> > Let say I request 'point'.
> > All fine, engine gets called with a mask set to 'point'.
> >
> > Next I switch the Shuffle to 'normal'.
> > Now I'd expect engine() to be called with a channel mask for 'normal'
> > but instead the mask is 'point,normal'.
> >
> > Likewise, if I now request 'motion' next, engine() will be asked for
> > 'point,normal,motion'.
> > However, if I now modify any setting on my plugin itself to force a
> > re-render, my engine() will correctly only be called with 'motion', as
> > one would expect.
> >
> > Wtf is going on here?
> >
> > I really like to find out how I can only render the channels that end up
> > being used.
> > Some of the channels my Iop outputs are literally 50times as expensive
> > as others. So in the not uncommon case that a user has started rendering
> > an expensive channel, switched the Shuffle to one of the cheap ones,
> > Nuke will still request the expensive channel (and the cheap one) from
> > my node, even though the former's data is never being used downstream!
> >
> >
> > I also noticed that if I call writable_channels() (undocumented)) on the
> > Row passed to engine() it will sometimes contain only contain those
> > channels that one would expect to be requested (i.e. 'motion' in above
> > example) -- but only sometimes.
> > But most of the time it is empty. So I intersect the mask passed to
> > engine() with row.writable_channels() if the latter is /not/ empty. And
> > that sometimes gives me what I expect -- sometimes.
> >
> > I'm looking forward to understand what is going on here. :)
> >
> >
> > .mm
> > _______________________________________________
> > Nuke-dev mailing list
> > Nuke-dev@support.thefoundry.co.uk
> > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
> >
>
>
>
> --
> paolo berto
> jedi rock & dub band lead
> /*jupiter jazz*/ visual research — hong kong
> www.jupiter-jazz.com
>
>
> ------------------------------
>
> _______________________________________________
> Nuke-dev mailing list
> Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
>
>
> End of Nuke-dev Digest, Vol 55, Issue 3
> ***************************************
>



-- 
Abraham Martin

R+D Department
Next Limit Technologies
_______________________________________________
Nuke-dev mailing list
Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev

Reply via email to