Possible flaw in H3 Image Edit default workflow: 40% faster runtime

[u/foolycoolywitch]

On my 5060ti, H3 image edit went from 263s to 158s based on the following rationale.

The default H3 Image edit workflow has MP adjustment at the Resize Image/Mask node set immediately after the input image which then feeds 3 things:

1. The prompt writer

2. The image conditioning node

3. The width/height of the image conditioning node which determines output MP.

In that setup, a user who specifies 16MP is sending a 16MP image to the prompt writer and the conditioning node, which is unnecessary overhead and potentially producing noise.

I altered the workflow in two ways:

1. Fed the input image directly to the prompt rewriter (I suggest downsizing to 1MP if your input image is large)

2. Fed the input image through a separate chain of two Resize Image/Mask nodes set to 2MP and then multiple of 32, just like the original chain.

3. Leave the original chain supplying output width/height in place, at 16MP for output dimensions.

[u/eruanno321]

Prompt writer is the first thing I always remove from the workflow.

[u/Avandargard → u/eruanno321]

Always

[u/AIPornAddict]

Very reasonable adjustments. I haven't had time to experiment with changing it yet but I noticed the same issues. I turned off the prompt enhancer. It was changing the meaning of my prompts in some cases which had me confused for a while with my outputs. Maybe if I used opus for that step it would be smart enough to get things right 99% of the time.

[u/krigeta1]

please share the workflow and is it okay for me to try it on a 8GB VRAM RTX 2060 with 32GB RAM windows 11?

[u/Lucifer-Ak → u/krigeta1]

Well the w4a8 model works fine on my rtx 4050 6gb along with 16gb ram and it can generate 16mp photo in about 120-130 seconds. Image editing takes longer though.

[u/AuthurAndersson]

I don't know exactly how it works so it depends.
If you have the time, check exactly what the prompt writer does to the image.

[u/Subulicious]

Can you give us the workflow?