Terrible quality after first batch
Closed this issue · 7 comments
When both batch size and batch count are set to values >1, the first batch is generated normally then only the first image of any successive batches in the job are correct. With batch size 2 with batch count 2 the first 3 images will all be normal quality and the 4th looks similar to generating with a typical negative prompt in the regular prompt field. For batch size 4 with batch count 3, images 1-5 and 9 will generate normally, while images 6-8 and 9-12 will look like negative prompts. This occurs even when not using any of the AND, AND_PERP or AND_SALT keywords.
Browser: Chrome Version 114.0.5735.134
OS: Windows 11 - 22H2 build 22621.1848
WebUI: Automatic1111 v1.3.2 commit baf6946
Python: 3.10.10
Torch: 2.0.1+cu118
Gradio: 3.32.0
xformers: not installed
Commandline_Args: --listen --opt-sdp-no-mem-attention --api --disable-nan-check
Sampling method: DPM++ 2M Karras (didn't test other samplers)
Steps to reproduce:
- Set batch size and batch count both to values of 2 or more.
- Generate a set of images using any prompt and negative prompt combination.
Examples:
Batch count 2, batch size 2 with Neutral-Prompt extension enabled in Extensions tab:
Batch count 2, batch size 2 with Neutral-Prompt extension disabled in Extensions tab:
Prompt: superb, 1girl, multicolored hair, pastel colored hair, pink hair, blue hair green hair, light green eyes, short hair, fluffy hair, curly hair, pixel-print hoodie, leggings, pixel-print sneakers, beautiful 8k wallpaper, extremely detailed, intricate
Negative Prompt: negative_hand, (KHFB, AuroraNegative), (Worst Quality, Low Quality:1.2), border, nsfw, skimpy, grayscale, multiple_girls, (watermark:1.2)
Also, I just realized I generated the set that has Neutral-Prompt disabled with no upscaler selected for Hires fix which is likely the cause for the differences in images 1-3. Obviously the actual problem image is far more than just a difference in upscaler so I won't bother to redo that set.
I went ahead and tried to reproduce the prompt inversion issue with adetailer and neutral prompt active, but I am unable to reproduce.
I updated adetailer to Bing-su/adetailer@a1032d8 (which was the version you were using) and neutral prompt to ab5c46d (latest at this moment).
Adding --opt-sdp-no-mem-attention
to launch args does not change anything.
No problem, thanks for reporting initially. It's good to be aware of these issues in case there is something that can be done by the maintainers.