Change Details

To test a new workflow at the blender institute we want to use the same meta data as stored in the input file. The compositor already has the ability to keep the meta data when using cryptomatte which we want to use. This is just an experiment and not intended to land in blender master ATM. {F13054689} Metadata for single layered textures are stored as ImBuf.meta_data (Properties) I expect that in `void OutputSingleLayerOperation::deinit_execution` we could fill them with information that we get from COM_MetaData. We should then also fill the meta data in `ImageOperation`.

To test a new workflow at the blender institute we want to use the same meta data as stored in the input file. The compositor already has the ability to keep the meta data when using cryptomatte which we want to use. This is just an experiment and not intended to land in blender master ATM. {F13054689} Metadata for single layered textures are stored as `ImBuf.metadata` (Properties) I expect that in `void OutputSingleLayerOperation::deinit_execution` we could fill them with information that we get from COM_MetaData. We should then also fill the meta data in `ImageOperation`.

To test a new workflow at the blender institute we want to use the same meta data as stored in the input file. The compositor already has the ability to keep the meta data when using cryptomatte which we want to use. This is just an experiment and not intended to land in blender master ATM. {F13054689} Metadata for single layered textures are stored as `ImBuf.meta_data` (Properties) I expect that in `void OutputSingleLayerOperation::deinit_execution` we could fill them with information that we get from COM_MetaData. We should then also fill the meta data in `ImageOperation`.