File Output Node does not save Metadata #108103

Closed
opened 2023-05-20 14:34:35 +02:00 by Steve Gaskell · 7 comments

System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA RTX A4500/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15

Blender Version
Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b
Worked: unaware

Short description of error
Files output from the File Output compositor node do not contain the metadata specified in the Output Properties

Exact steps for others to reproduce the error

  1. Create any scene
  2. Ensure the output properties have some metadata selections (the default ones are fine) and set the output format to JPG.
  3. Add a file output node to the compositor that saves the file (using "use node format" option)
  4. Render the scene with Cycles
  5. Manually save the rendered output image (use a different name to that used in the File Output node)

The result is two JPGs, one output from the File Output node and one saved manually.
The one saved manually contains all the correct metadata. The one saved using the file output node contains none.

I rely on the metadata in JPGs to track back to the blend file that created it. This enables me to keep track of lots of output that I generate and go back to the blend if needs be to tweak the output.

I also cannot understand why TIF files do not have blender metadata written to them - I actually use TIF files by default and have to manually save a JPG annex file with the same name just to get the metadata!. If it is possible to raise this as a request, could you let me know how?

**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA RTX A4500/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15 **Blender Version** Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: `1be25cfff18b` Worked: unaware **Short description of error** Files output from the File Output compositor node do not contain the metadata specified in the Output Properties **Exact steps for others to reproduce the error** 1. Create any scene 2. Ensure the output properties have some metadata selections (the default ones are fine) and set the output format to JPG. 3. Add a file output node to the compositor that saves the file (using "use node format" option) 4. Render the scene with Cycles 5. Manually save the rendered output image (use a different name to that used in the File Output node) The result is two JPGs, one output from the File Output node and one saved manually. The one saved manually contains all the correct metadata. The one saved using the file output node contains none. I rely on the metadata in JPGs to track back to the blend file that created it. This enables me to keep track of lots of output that I generate and go back to the blend if needs be to tweak the output. I also cannot understand why TIF files do not have blender metadata written to them - I actually use TIF files by default and have to manually save a JPG annex file with the same name just to get the metadata!. If it is possible to raise this as a request, could you let me know how?
Steve Gaskell added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-05-20 14:34:36 +02:00
Iliya Katushenock added the
Interest
Compositing
Interest
Nodes & Physics
labels 2023-05-20 14:35:51 +02:00
Steve Gaskell changed title from File Output Node does not generate Metadata to File Output Node does not save Metadata 2023-05-20 14:40:35 +02:00

is someone working on this ? I would like to take up this issue as my Good First Issue.
Module owner please let me know... If not.. I'm happy to take this up

is someone working on this ? I would like to take up this issue as my Good First Issue. Module owner please let me know... If not.. I'm happy to take this up

From what I can see, this isn't implemented in compositor, so this is not a bug. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

From what I can see, this isn't implemented in compositor, so this is not a bug. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Blender Bot added
Status
Archived
and removed
Status
Needs Triage
labels 2023-05-25 05:13:12 +02:00

@Agastya Happy to hear that, I would consult this on blender.chat platform with developers. @OmarEmaraDev Can you perhaps give more concrete pointers where to look and who is best contact point?

@Agastya Happy to hear that, I would consult this on blender.chat platform with developers. @OmarEmaraDev Can you perhaps give more concrete pointers where to look and who is best contact point?
Member

@Agastya No one is working on this as far as I know. You should probably consult @Jeroen-Bakker if you would like to work on this.

@Agastya No one is working on this as far as I know. You should probably consult @Jeroen-Bakker if you would like to work on this.
Member

Is related to #97905

Is related to https://projects.blender.org/blender/blender/issues/97905
Author

Sorry to see this is flagged as "not a bug" because it isn't implemented. Presumably then it would need to be a "suggestion" or "user request"? This seems like semantics. If the functionality of saving renders follows the parameters as laid out on the File Output properties then so should the File Output node. There is nothing in the documentation to say that it wont do that, and sheer common sense says that it should. "If I save it this way I get one thing, but if I save it that way I get another" should not occur and, in my long years of software development manger, I would consider that a bug. The fact that someone forgot to do it doesn't make it any less a bug. But I guess that's what I would do and you guys have your own procedures, which is fair enough.

Just for clarity, I'm happy to raise this on the Right Click Select, but comments below the closure seem to indicate that @Agastya may pick it up anyway? If someone can let me know whether I should raise or not, thanks.

Steve

Sorry to see this is flagged as "not a bug" because it isn't implemented. Presumably then it would need to be a "suggestion" or "user request"? This seems like semantics. If the functionality of saving renders follows the parameters as laid out on the File Output properties then so should the File Output node. There is nothing in the documentation to say that it wont do that, and sheer common sense says that it should. "If I save it this way I get one thing, but if I save it that way I get another" should not occur and, in my long years of software development manger, I would consider that a bug. The fact that someone forgot to do it doesn't make it any less a bug. But I guess that's what I would do and you guys have your own procedures, which is fair enough. Just for clarity, I'm happy to raise this on the Right Click Select, but comments below the closure seem to indicate that @Agastya may pick it up anyway? If someone can let me know whether I should raise or not, thanks. Steve
Member

@squawk The linked issue #97905 is already marked as a To Do and some experiments were already done, so a topic in RCS is probably not necessary.

@squawk The linked issue #97905 is already marked as a To Do and some experiments were already done, so a topic in RCS is probably not necessary.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#108103
No description provided.