Feat (ui): Add VAE Model to Recall Parameters

[StefanTobler]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update
• Community Node Submission

Have you discussed this change with the InvokeAI team?

• Yes
• No, because: it is 2 am est

#4796

Have you updated all relevant documentation?

• Yes
• No

I don't believe there is any documentation explicitly referencing the recall parameters.

Description

This code changes allows users to recall the VAE model as a Recall Parameter. The VAE model is now part of the "recall all parameters" setting. There is room to add the VAE Precision to the metadata and also making that a recall parameter..

Related Tickets & Documents

• Related Issue [bug]: VAE is not changing when "Use all" #4796
• Closes [bug]: VAE is not changing when "Use all" #4796

QA Instructions, Screenshots, Recordings

1. Generate an image using a VAE other than default.
2. Select that generated image, change the VAE model, and select "Use All"
3. VAE model should change in the UI.
4. VAE model is available in "recall parameters" of the metadata section.

vae_recall.mp4

Added/updated tests?

• Yes
• No : no frontend test suite

[optional] Are there any post deployment tasks we need to perform?

[StefanTobler]

This PR may not be considered "complete" as it does not recall the "default" VAE model if that is selected. I think that this would need the addition of adding the default VAE to the metadata, as of right now, if the VAE model is default it is not added in the generated images metadata. Sorry tired and I was not thinking, ofc I can add this, just check for a null VAE. I can add this tomorrow.

[StefanTobler]

Last note for tonight, I also noticed that the naming for VAE is a bit inconsistent around the frontend, it seems it is either VAE or VAE Model, but they both refer to the same thing.

[psychedelicious]

Yep as you noted, lets add some additional logic to check if the vae is nullish when recalling all, and if so, set it to null.

Looking good otherwise!

Stretch goal: check the RTK Query cache when recalling the VAE to ensure it is actually available on the system. Happy to have this be a future change, and we should do the same for when we recall a main model.

[StefanTobler]

@psychedelicious added the check for nullish variables. It is a bit verbose imo, but I am not sure if it is worth making it harder to read to reduce the code.

Also debating on adding similar logic to ImageMetadataActions.tsx so that vae is displayed as "Default" when nullish. I am ignorant as to when this would be used in the event that VAE is not present for a reason. I guess it seems strange to me to be making all the exceptions for this one field but not all the others when null. Maybe overthinking.

[StefanTobler]

I guess it lead me to question, if the VAE is undefined, it is okay to assume we oughta force the default VAE model on the parameters?

[StefanTobler]

[Millu]

I guess it lead me to question, if the VAE is undefined, it is okay to assume we oughta force the default VAE model on the parameters?

This behavior makes sense to me

[StefanTobler]

Agreed, I added that in the latest commit.

[psychedelicious]

Thanks @StefanTobler !