managing exr metadatas

[William Eguienta]

Hi,
Gaffer is writting many things in metadatas that I don't need
Is there a way to prevent gaffer writing, for example,  all context variables in exr metadata ?
i see that a can delete them with a node, then rewrite with imageWriter but it doesn't helps

Also, if I try to add metadata using the "imageMetadata" node, it always add a EXR prefix.
it will be written as "exr/input/timecode" and not just "input/timecode" as expected.

any way to write metadata without prefix ?

thanks

[John Haddon]

On Sun, Jul 11, 2021 at 7:36 AM William Eguienta <kaiz3...@gmail.com> wrote:

Gaffer is writting many things in metadatas that I don't need
Is there a way to prevent gaffer writing, for example,  all context variables in exr metadata ?

Currently there is no way of turning that off. Are the extra fields causing specific problems for you? Some of them (e.g. `gaffer:sourceScene`) are necessary for certain Gaffer functionality to work as expected.

Also, if I try to add metadata using the "imageMetadata" node, it always add a EXR prefix.
it will be written as "exr/input/timecode" and not just "input/timecode" as expected.

any way to write metadata without prefix ?

Where are you seeing this "exr/" prefix? Testing here, I don't see it either in the metadata loaded via an ImageReader or in the output from `exrheader`. Is it possible that you are looking at it in Nuke (I have a dim memory that maybe Nuke adds the prefix on loading?). If you're seeing it in Gaffer or `exrheader`, could you provide an example file with an ImageMetadata and ImageWriter node that shows the problem?

Cheers...

John

[William Eguienta]

Hi John,

Yes I see the exr prefix in nuke, i have tried importing the exr with custom timecode metadata to resolve,
It doesn't see it too as a timecode, so I guess there is something added that doesn't fit nuke and others expectations

here are 2 files, one with timecode made in gaffer
the other is the same + timecode made in nuke (nuke's TC works in other softwares)

https://fromsmash.com/TF~~9Hz1Ga-ct

cheers

[John Haddon]

On Tue, Aug 3, 2021 at 12:56 PM William Eguienta <kaiz3...@gmail.com> wrote:

i have tried importing the exr with custom timecode metadata to resolve,

It doesn't see it too as a timecode, so I guess there is something added that doesn't fit nuke and others expectations

Timecodes are a custom data type, rather than just being a string (it looks like maybe you just added it as a string in Gaffer?). Gaffer can round-trip them (if you read and write your nuke example, the timecode is preserved), but I don't think we have a node to change the timecode yet. I have a feeling a proprietary one exists internally somewhere, so I'll make some enquiries.

Cheers...

John

[John Haddon]

In lieu of a dedicated node for setting timecode, I've opened a PR that allows the standard ImageMetadata node to be used to set timecodes, if used with an appropriate expression :

https://github.com/GafferHQ/gaffer

I've also attached a file which demonstrates how it can be used.

Cheers...

John

[William Eguienta]

Hey John,

sorry for the very late answer and thank you for the example file and update, helps a lot

thanks