[Draft] Discuss options for exposing original image metadata in upscaled images (Issue #6291)#8660
Conversation
|
Here's my 2c (with apologies for taking so long to join the conversation). While it is more elegant to maintain a reference to the source metadata via the existing What do you think of the idea of generalizing this so that if there is a chain of source images (e.g. a series of upscales are applied), the metadata from each upscale operation is presented as well. |
|
Thanks for the feedback, I agree. Relying solely on I also agree that generalizing this to include the full chain of source images (e.g. multiple upscales) would be beneficial, and I’m happy to proceed in that direction. |
|
Why not do both by adding the 'upscale_initial_image' inside the 'source_image_metadata' so for people that do keep everything they have a way of traversing back to the original. |
|
I like @skunkworxdark's idea of having both the original and upscale with full metadata and pointers to each other. |
|
@Filippo-Venturini Do you plan to do any more work on this PR? If not, I will close it. |
|
Hi! Thanks for the ping. I don’t have bandwidth to continue this right now, so please go ahead and close it. If I pick it up again in the future, I’ll open a fresh PR. Appreciate the patience! |
Summary
This draft PR is meant to continue the discussion from [Issue #6291] and the related Discord conversation regarding original image metadata for upscaled images.
Currently, upscaled images store a reference to the source image via
upscale_initial_image, but the full metadata (prompt, seed, scheduler, etc.) is not stored.Two alternatives are under discussion:
source_image_metadata) for external/export use.This PR does not include any implementation; it is intended to facilitate review and discussion among maintainers.
Related Issues / Discussions
QA Instructions
Not applicable — no code changes in this PR.
Merge Plan
Checklist