ha - yes, but that kind of ruins the render ;)
the issue pops up as we saturate the farm (of course) and I think sys
would have me fired if I did it myself anytime in the next 3 months!
Cheers
JRAB
On 01/29/2013 06:15 PM, Nathan Rusch wrote:
I don't think Nuke will currently let you write arbitrary TIFF
metadata, but a simple solution (if you've got the time to run test
renders) would just be to do a Text node burn-in with [info hostname]
as a text expression.
-Nathan
-----Original Message----- From: John RA Benson
Sent: Tuesday, January 29, 2013 1:08 AM
To: Nuke user discussion
Subject: [Nuke-users] Tiff metadata / tags
Hey out there -
Does anyone know of a way to embed certain tiff tags into a (tiff)
render? A ModifyMetaData node doesn't seem to do it unless there is a
magic key I don't know of.
We are rendering tiffs and having some odd render issues. I'm hoping by
adding TIFFTAG_HOSTCOMPUTER
(http://www.awaresystems.be/imaging/tiff/tifftags/hostcomputer.html) we
might be able to ID the renderbox and discover if it's something to do
with specific machines on the farm.
hmm - possibly some python afterFrameRender trick if there's not a
simple way I've overlooked?
Any other ideas on ID'ing which box a tiff is rendered on is welcome...
rendering uncompressed, 16 bit if that matters.
thanks -
JRAB
_______________________________________________
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
