Skip to content

[Draft] Discuss options for exposing original image metadata in upscaled images (Issue #6291) #8660

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −0
Open

[Draft] Discuss options for exposing original image metadata in upscaled images (Issue #6291) #8660

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions invokeai/frontend/web/src/features/nodes/util/graph/buildMultidiffusionUpscaleGraph.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,6 +178,17 @@ export const buildMultidiffusionUpscaleGraph = async (state: RootState): Promise

const modelConfig = await fetchModelConfigWithTypeGuard(model.key, isNonRefinerMainModelConfig);
const upscaleModelConfig = await fetchModelConfigWithTypeGuard(upscaleModel.key, isSpandrelImageToImageModelConfig);

// DISCUSSION: Currently we store only a reference to the original image
// via `upscale_initial_image`. The full metadata of the source image
// (prompt, seed, scheduler, etc.) is not included here.
//
// Two options could be considered:
// 1) Expose a UI way to jump to the source image in the gallery (leveraging this reference).
// 2) Store all original image metadata under a separate field (e.g., `source_image_metadata`)
// for external or export use.
//
// This PR is meant to discuss which approach is preferred before implementing.

g.upsertMetadata({
cfg_scale,
Expand Down