InvokeAI/invokeai/app
psychedelicious 297408d67e feat(nodes): add control adapter processed images to metadata
In the client, a controlnet or t2i adapter has two images:
- The source control image: the image the user selected (required)
- The processed control image: the user's image after we've processed it (optional)

The processed image is optional because a user may provide a pre-processed image.

We only actually use one of these images when building the graph, and until this change, we only stored one of the in image metadata. This created a situation where only a processed image was stored in metadata - say, a canny edge map - and the user-selected image wasn't provided.

By adding the processed image to metadata, we can recall both the control image and optional processed image.

This commit is followed by a UI-facing changes to support the change.
2024-03-14 12:34:03 -07:00
..
api ui consistency, moved is_diffusers logic to backend, extended HuggingFaceMetadata, removed logic from service 2024-03-13 21:02:29 +11:00
assets/images tweaks in response to psychedelicious review of PR 2023-07-26 15:27:04 +10:00
invocations feat(nodes): add control adapter processed images to metadata 2024-03-14 12:34:03 -07:00
services feat(events): add submodel_type to model load events 2024-03-14 18:29:55 +05:30
shared tidy(nodes): move all field things to fields.py 2024-03-01 10:42:33 +11:00
util refactor(nodes): model identifiers 2024-03-07 10:56:59 +11:00
__init__.py fix: make invocation_context.py accessible to mkdocs 2024-03-01 10:42:33 +11:00
api_app.py feat(api): add ModelIdentifierField to openapi schema 2024-03-10 11:03:38 +11:00