Description
Feature Idea
My previous post where I thought something was wrong, but apparently "working as intended":
#620
request: using text metadata only shouldn't break or lose web UI functionality
-
There's nothing in the user settings that indicates that this is the intended behavior. At the very least, the tooltips should indicate this -- I spent considerable time trying to diagnose this. Intuitively, a user would expect that the web UI is fully capable of reading both/either image or text file metadata.
-
Arguably, the point of a GUI is to make things easier for the user. It seems counter-intuitive to lose some web UI functionality because the metadata is saved elsewhere.
-
Metadata is a vital part of working with any image generation software. Losing ability to work with it in the GUI is very inconvenient.
-
Privacy and control over data. It's entirely reasonable that people would not want metadata embedded in their images. Should these people suffer reduced functionality because of this?
A compromise: If this is too laborious to code and debug, might I suggest that the metadata text file contain the ComfyUI workflow instead? At least that way people can easily copy-paste or drag-drop it into ComfyUI if they need to re-use parameters.
Or perhaps ComfyUI metadata can be added as an additional option next to "SaveTextFileMetadata" so we can have both types saved.
Other
No response
Activity