Write metadata in exr

Anyone know how to set the metadata “Owner” when exporting .exr seq?
I need to change it to a specific name.

The request comes from Resolve that need it embedded in the file.
ps: I can’t use directory structure to pass on the Information on this project

I’m about 90% sure flame can’t do this. There may be some post-export app that can, but Flame’s not great at putting metadata back in and there are a handful of feature requests about the issue.

1 Like

If anybody would know, it might be @Josh_Laurence

Isn’t this something you would do with a command line after export? Like chown?

When we need to have specific EXR layer naming or other MetaData, we run the exports thru Nuke as a wrapper. It is shameful that Flame can not do this.


Sorry, haven’t been asked for this yet, and if @ALan and @andy_dill say it doesn’t work yet, I’ll take that for gospel. Maybe @fredwarren has a handle on the horizon for this feature?

This is Stephane Labrie territory.

Yep, right know i’m exporting exr, change metadata in nuke and exporting the sequence again.
It’s not too bad but is not always easy to free up a nuke licenses each time i have to export a new version of a shot.
It would be cool to have some matchbox or a python script to work like ModifyMetaData node and CopyMetaData the node in nuke.
Should i open a feature request?

1 Like

I would recommend OIIO as simple comand line utility to create and change metadata.
oiiotool: the OIIO Swiss Army Knife — OpenImageIO 2.4.0 documentation.

If you need to execute a python script after the images render, OIIO comes with Python bindings so once the module is in the python path the code is simple:

img = ImageBuf ("foo.jpg")
# Add a caption:
img.specmod().attribute ("ImageDescription", "Hawaii vacation")
# Add keywords:
img.specmod().attribute ("keywords", "volcano,lava")
write_image (img, "foo.jpg")



Thank you,
I’m a real beginner in coding and i don’t know if this question make sense, but could you give me some direction on how to make the bindings available within flame python console?
I’ve never add new module before and i don’t want to guess with stuff i don’t understand.

Installing OpenImageIO binaries should be straight forward in Linux os OS x using yum and homebrew respectively.
Importing the module in the Flame Python API could be trickier if OIIO is compiled against a different version of Python. So probably best to try to run OIIO as a system process from within Python.
I’ll try to put something together when I get some time.

1 Like

@milanesa Thank you so much.