suggestion : Copy transformation and metadata

Moderator: jsachs

Post Reply
pierrelabreche
Posts: 681
Joined: January 29th, 2019, 11:47 pm
What is the make/model of your primary camera?: Nikon Z8

suggestion : Copy transformation and metadata

Post by pierrelabreche »

If an image is saved from a branch created using a Copy transformation at the top, the metadata is unavailable.
Wouild it be possible to let the metadata from the original image flow through the copy transformation ?
jsachs
Posts: 4690
Joined: January 22nd, 2009, 11:03 pm

Re: suggestion : Copy transformation and metadata

Post by jsachs »

There is code to do this already -- I need more information to reproduce the issue.
Jonathan Sachs
Digital Light & Color
pierrelabreche
Posts: 681
Joined: January 29th, 2019, 11:47 pm
What is the make/model of your primary camera?: Nikon Z8

Re: suggestion : Copy transformation and metadata

Post by pierrelabreche »

Screenshot and script attached
2025-05-20  PWP Copy missing Metadada.jpg
2025-05-20 PWP Copy missing Metadada.jpg (141.93 KiB) Viewed 129 times
test.jpg.script
(4.83 KiB) Downloaded 6 times
jsachs
Posts: 4690
Joined: January 22nd, 2009, 11:03 pm

Re: suggestion : Copy transformation and metadata

Post by jsachs »

Currently this only works if Copy has a single active input. A similar issue exists with other top-level transformations such as Layout or Stack Images that may have multiple inputs. With some work, Copy could be treated as a special case since it only has one input at a time, but it does not work that way now.
Jonathan Sachs
Digital Light & Color
pierrelabreche
Posts: 681
Joined: January 29th, 2019, 11:47 pm
What is the make/model of your primary camera?: Nikon Z8

Re: suggestion : Copy transformation and metadata

Post by pierrelabreche »

A similar issue exists with other top-level transformations such as Layout or Stack Images that may have multiple inputs. With some work, Copy could be treated as a special case since it only has one input at a time, but it does not work that way now.
Because Copy identifies its active input, it is logical to flow down the metadata from the active input.

For stack and layout, it could be useful to define an "Override metadata" transformation that would copy applicable metadata from an identified input image to another. Alternatively the transformations with multiple inputs could have a mechanism to identify which of the inputs is to be used for metadata.
Post Reply