Yes it would be great to see simple solutions to the overall issue you've
brought up, like say a "Dot" being purely an interface element.  I've
requested this in the past.

But also being able to easily copy camera values into metadata would be
nice, or ideally like you say I would really want to just have metadata in
the camera stream, grabbed form the Camera knobs if necessary.

On a general level, if it can be done, how do you copy a knob value into a
metadata key?  It doesn't seem to resolve expressions in the "value" field.



On 11 August 2011 13:20, Paul Raeburn <[email protected]> wrote:

> I wondered about that, but metadata node dont work in camera pipes, so I
> ran into a dead end.  Getting the name of the camera node node world be
> great (as per Ivans recommendation).  Ideally it would be great to et the
> data from the camera pipe directly, so it can be modified by downstream axis
> etc, but I assume that a foundry question.
>
> Any suggestions on how to access the metadata of the camera pipe?
>
>
> On 12 August 2011 05:51, Frank Rueter <[email protected]> wrote:
>
>> Try "[topnode]" which will give you the top most node of a stream.
>> Obviously it won't work if the camera's parent pipe is connected. In that
>> case you will need a script that walks upstream and returns the first camera
>> node, then use that in your expression. Or use meta Data to make the camera
>> info flow in the stream which is more elegant and probably faster.
>>
>>
>>
>> On Aug 10, 2011, at 8:24 PM, Paul Raeburn <[email protected]>
>> wrote:
>>
>> >
>> > We have been using references tot he input node and then values to get
>> values from a camera node.  ie. NoOp1.input.focal
>> >
>> > This works fine but breaks if there is anything in between the NoOp and
>> the camera, so you can tidy up the script with Dots or end up with multiple
>> cameras just to be tidy.
>> >
>> > Is there a way to get camera stream directly, or even the name of the
>> camera node from the stream?
>> >
>> > thanks
>> >
>> > Paul Raeburn
>> > _______________________________________________
>> > 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
>
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users

Reply via email to