M2.1

This is a small update to the last Monument Two workflow, based on some of your feedback as well as further refinement needs.

If you’ve just found out about this, the full story begins with the M1 workflow here.

The JSON link is at the bottom of the page.

(if you just landed here for the first time, the latest workflow is the M3 )

The Ui remains largely the same except for the Save group.

The Save group

In prior version, there was only one save folder, which I felt was quite limited from a DAM (Data Asset Management) point of view. I wanted something to save every step automatically without me having to think about it, so I broke the group into 4 sub-groups, one for each level of generation (Base, Upscale1, Upscale2, Upscale 3).

 

Config group

The subgroups were creating title redundancy with the main groups (Controlnet vs Controlnet) and that made the Fast Groups Muter panel confusing. I’ve renamed them to reflect the current hierarchy. You’ll notice I did the same in the Save group and sub-groups.

 

Shedding some node packs

Replaced the DualCLIPLoader (Multi-GPU) and the Load Advanced ControlNet Model with the regular versions. I’ve also replaced some nodes (Get Image Size) from the Masquerade custom node pack so it’s no longer needed. Masquerade seemed to create some dependency errors with some users.

(update March 24th 2025: testing Gumroad for the download and ratings part)

Previous
Previous

M3

Next
Next

Monument Two