Home Creators Posts Import Register Favorites Logout

Downloads

Content

Video - https://youtu.be/5TQulYkuiw8

Overview

Z-Image-Turbo is a great Free & Open Source Model and now I've powered-up my Z-Image workflow with even more things! The best bits being EVEN MORE DETAIL and HIGHER RESOLUTIONS! This workflow version now includes:

Union ControlNet Support

Power LoRA Loader

Detail Daemon

Detail Demon Split-Sigmas

Ultimate SD Upscale (go beyond 2048x2048!)

Improved AI Prompt Enhancer

Additional compare groups

Personally I wasn't too impressed with the Union ControlNet, so do let me know if you get any amazing results as most things I tried were a bit pants ;) It seemed to be even worse when combined with LoRAs, but it is still early days yet. Who knows, maybe it's a code thing or perhaps we'll get a better model soon? Either way, there's a group for that now!

After testing a lot of LoRAs, only the one from Ostris himself seemed to be any good with all of the other ones seeming to be way over-trained and actually producing worse images than with just prompting alone. Lowering the strength on a number of them helped, but once again it hasn't been long since the model was even released, so hopefully everything will get up to the same level as the one Ostris did (which is indeed a fun LoRA!)

On the flip side, Detail Daemon and Ultimate SD Upscale both work a treat and give you great control over the amount of detail you can get in your generations. Ultimate SD Upscale may take a while, but it's the only way to get over 2K resolution images without everything degrading.

Some of my other favourite examples...

Workflow Information

There are two versions of the workflow attached - the full version and one without AI Prompt Enhance.

For the full version you will need Ollama installed, along with downloading any ollama models of your choice. Mistral 3 is a great option, as is IBM Granite or Gemma 3.

Out of the various LoRAs tested, the Children's Drawings and UltraReal (at low strength) were my favourite:

Do let me know if you find any other you like!

The default Detail Daemon setting are very light:

If you set the bias to 0, you will likely need to lower the detail amount as well. Around 0.25 is a good place to start, and the start value seems to have a variable "tipping point".

For example, this is too much detail (detail 1.5, start 0, end 1, 0 for everything else):

With a detail amount of 0.7 and a start of 0.2. the detail is very high, but it still close to the standard, baseline (TTI) image:

A start of 0.07, however, gives a very different result:

When using the High Res Fix, don't forget you can choose which latent to use:

By default it is set to the Detail Daemon Split Sigma, but you can chose LAT_DD (from the Detail Daemon group) or LAT_TTI (the basic Text-to-Image generation) as well.

You can, of course, also set the scale_by value to your own preference.

The same goes for the Ultimate Upscale:

Again, by default it is set to the Detail Daemon Split Sigma generated image, but you could also pick any of the other IMG options.

Use a fairly low starting resolution (under 1920x1920), set it to IMG_HRF and you can get both the extra detail from the HiResFix option AND the Ultimate upscale ;)

For the Image Compare groups, you can also select which images IMG_*)to compare:

With the Detail Daemon Split Sigmas, you may like to switch outputs:

The "safe" option of denoised_output is the default.

First order samplers DO NOT WORK WELL if you use the plain (not denoised) output option:

If using that option, you'll do best with an *_sde option...

... or seeds2/3/sa_solver (or other options such as those from RES4LYF (res2s, res2m, etc)). Basically, any second or third order sampler should give better results.

Have fun!

Files

Comments

william smith

The trouble with "upscale latent by" is that you need a high denoise in the subsequent sampler, because (for whatever reason) upscaling the latent looks horrible with a low denoise. I took one of your workflow, removed "upscale latent by" with "upscale image by" (and obviously a vae decode and vae encode), then took the denoise way down to 0.2 or so. Then I got good upscale with no big image changes.

Star Hawk

The SampleCustomAdvanced node is blowing up for me. I've tried several different ComfyUI installations that are good for everything else so idk. I have Triton/Sage working fine, any ideas? Work arounds?

James Harrison

The problem with control nets and Loras, from what I understand, is the Z-Image base hasn't been released yet, just the distilled Z-Image Turbo. Even the controlnet, was released without access to the base model, which is why it's applied as a model patch. I expect they'll release the base in the new year and things will improve. I'm looking forward to outpainting functionality myself.

Neskweek

First of all, thank you for your content. Although I’ve been having fun with ComfyUI for several years now, I had never thought it was possible to arrange the nodes in this way. A big thank you for that. Also, with this particular workflow, you taught me that a daemon detailer existed, and it has radically changed my compositions. Just for that, I’m really happy to contribute. But, with all humility, I’d like to point out one thing in this workflow which, in my opinion, might help with your LORAs problem: Your handling of CLIP seems incorrect to me. I would have gladly added a screenshot of what I think is correct, but I’ll try to explain: - In the “Prompt Encoding” group, you should have a SetNode on the output of “Load CLIP” (CLIP_BASE) that is not connected to anything. - In the “Model” group, a GetNode that calls CLIP_BASE, connected as input to the “Power Lora Loader” node. - In the “Model” group, a SetNode “CLIP_LORA” connected to the output of the “Power Lora Loader” node. - In the “Prompt Encoding” group, a GetNode “CLIP_LORA” as input to “CLIP TextEncode”. As an additional remark, just for your information, I’m having concern with your implementation of HiresFix, which is very “random”, to my taste, in terms of quality of the output. FYI, I prefer using the “HiResFix” node from the “comfyui-easy-use” custom node (for which you already have dependencies, I think), together with the filters/upscale_models 4x_NMKD-Superscale-SP_178000_G.pth or 4x-AnimeSharp.pth (sorry, I don’t remember where I downloaded them from, it’s been some time). I find the result to be much better and more consistent. Thanks again. Regards,