github invoke-ai/InvokeAI v4.2.2post1

latest releases: v5.4.1rc2, v5.4.1rc1, v5.4.0...
5 months ago

This release brings many fixes and enhancements, including two long-awaited features: undo/redo in workflows and load workflow from any image.

If you missed v4.2.0, please review its release notes to get up to speed on Control Layers.

📈 Patch Nodes for v4.2.2post1

v4.2.2 had a critical bug related to notes nodes & missing templates in workflows. That is fixed in v4.2.2post1.

✨ Undo/redo in Workflows

Undo/redo redo now available in the workflow editor. There's some amount of tuning to be done with how actions are grouped.

For example, when you move a node around, do we allow you to undo each pixel of movement, or do we group the position changes as one action? When you are typing a prompt, do we undo each letter, word, or the whole change at once?

Currently, we group like changes together. It's possible some things are grouped when they shouldn't be, or should be grouped but are not. Your feedback will be very useful in tuning the behaviour so it un-does the right changes.

✨ Load Workflow from Any Image

Starting with v4.2.2, graphs are embedded in all images generated by Invoke. Images generated in the workflow editor also have the enriched workflow embedded separately. The Load Workflow button will load the enriched workflow if it exists, else it will load the graph.

You'll see a new Graph tab in the metadata viewer showing the embedded graph.

Graph vs Workflow

Graphs are used by the backend and contain minimal data. Workflows are an enrich data format that includes a representation of the graph plus extra information, including things like:

  • Title, description, author, etc
  • Node positions
  • Custom node and field labels

This new feature embeds the graph in every image - including images generated on the Generation or Canvas tabs.

Canvas Caveat

This functionality is available only for individual canvas generations - not the full composition. Why is that?

Consider what goes into a full canvas composition. It's the product of any number of graphs, with any amount of drawing and erasing between each graph execution. It's not possible to consolidate this into a single graph.

When you generate on canvas, your images for the given bounding box are added to a staging area, which allows you to cycle through images and commit or discard the image. The staging area also allows you to save a candidate generation. It is these images that can be loaded as a workflow, because they are the product of a single graph execution.

👷 Other Fixes and Enhancements

  • Min/max LoRA weight values extended (-10 to +10) @H0onnn
  • Denoising strength and layer opacity are retained when sending image to initial image @steffy-lo
  • SDXL T2I Adapter only blocks invoking when dimensions aren't multiple of 32 (was erroneously 64)
  • Improved UX when manipulating edges in workflows
  • Connected inputs on nodes collapse, hiding the nonfunctional UI component
  • Use ctrl/cmd-shift-v to paste copied nodes with input edges
  • Docs updates @hsm207
  • Fix: visible seams when outpainting
  • Fix: edge case that could prevent workflows from loading if user hadn't opened the workflows tab yet
  • Fix: minor jank/inefficiency with control adapter auto-process (control layers only)
  • Internal: utility to create graph objects without going crazy
  • Internal: rewritten connection validation logic for workflows with full test coverage
  • Internal: rewritten edge connection interactions
  • Internal: revised field type format

💾 Installation and Updating

To install or update to v4.2.2post1, download the installer and follow the installation instructions.

To update, select the same installation location. Your user data (images, models, etc) will be retained.

Missing models after updating from v3 to v4

See this FAQ.

What's Changed

New Contributors

Full Changelog: v4.2.1...v4.2.2post1

Don't miss a new InvokeAI release

NewReleases is sending notifications on new releases.