Skip to content
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.

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

[bug]: Control Parameters Not Recalled When Loading Images from Version 4.x After Upgrade to 5.x #7154

Open
1 task done
ufuksarp opened this issue Oct 21, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@ufuksarp
Copy link
Contributor

ufuksarp commented Oct 21, 2024

Is there an existing issue for this problem?

  • I have searched the existing issues

Operating system

Windows

Version number

5.2.0

Browser

Edge latest

What happened

After upgrading from version 4.2.7 to 5.2, I'm experiencing a significant issue when recalling images generated in version 4.x. (Probably the same for any version before 5.0) Specifically, all the additional control parameters such as IP adapters, control adapters, and initial image (used for Image to Image generations) are not being recalled. Only the general parameters like prompts, model, seed, LoRAs, steps, scheduler, and CFG are retained. The rest of the parameters are completely ignored in the new canvas-based workflow.

Steps to Reproduce:

  1. Generate an image in version 4.2.x using IP adapters, initial images, and other control adapters.
  2. Upgrade to version 5.2.
  3. Try to recall the previously generated image.
  4. Observe that while basic parameters (like prompts and model settings) are recalled, critical control inputs (like IP adapters and initial images) are missing.

Expected Behavior:
When recalling images generated prior to Invoke 5.0, all parameters, including control adapters, IP adapters, and initial images, should be retained and properly loaded into the canvas mode of version 5.2.

Actual Behavior:
Only the basic parameters are loaded, while all the advanced control settings are ignored. No errors are displayed, but these key inputs do not appear in the canvas, effectively breaking the ability to accurately reproduce prior images.

Workaround:
Currently, the only way to address this issue is to manually read the metadata of each image and attempt to recreate the settings in the canvas mode. However, this is highly inefficient and not a sustainable solution to an issue that should be handled automatically by the program.

@ufuksarp ufuksarp added the bug Something isn't working label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant