controlnet via api request sends double amount of preprocessor images in response with most preprocessors (edit: not relevant - didn't see it's a feature)

[dermesut]

not sure, how to put things in the right words, so i'm trying it here.

• i send a request to the txt2img api.
• response['images'] contains just that: images.
• the order of the images, that are sent back is different from the order of the images when trying the same thing with the a1111 webui (visible if other extension, that deliever image-results are being used). but that's not what i'm getting at.
• if i used 1 controlnet unit to generate an image, i get back the respective results: the txt2img-result, as well as the preprocessor used/generated.
• if i choose an insightface or clip-vit preprocessor, all is as expected: 1 image that is the txt2img-result and 1 image that is the precprocessor-image.
• but: if i choose any of the many other preprocessors (haven't tried ALL of them, because there are so many of them), the response contains 3 images: 1 txt2img-result and 2 images that are the same preprocessor-result, e.g.: 2 identical depth-map from, say, the depth_anything preprocessor, or any othe preprocessor, really.
• this effect also shows itself with multiple controlnet units. e.g. 3 units lead to: 1 txt2img-result and 3*2 preprocessor-results, in total 7 images.

all this happens, if and only if hires.fix is being used in the payload.
if not, the effect does not happen and everything works as expected (except for the different order compared to a1111-responses, but that's ok, i guess).

forge is the only version of the 4 that i have installed, within which that happens (next to forge, the others are: 1. "classic" a1111 1.7.0 via github "manual" installation, 2. "classic" a1111 1.7.0 via "v1.0.0-pre" installation, 3. "classic" a1111 1.8.0 via "v1.0.0-pre" installation.

any idea what might be causing this?

edit:
sorry for the oversight.
i just realised that there is a feature "both, low res only, hi res only" - also in the webui itself.
switching from the standard "both" to another setting solves my issue.