-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: hires.fix denoising strength always saved as 0.4 value in image metadata if ADetailer is active #552
Comments
I came for the same issue, I can confirm it's happening for me as well, I always use external TXT files but it's in the image metadata as well, always stuck at 0.4 its very annoying I can't compare generated images anymore or reproduce them accurately |
I haven't cared about metadata for a long time, so I'm not sure, how long has this been an issue? |
Since quite some time so it seems 😄 |
Maybe about a week ago |
The image that is processed through adetailer becomes a product of img2img as a result. Right now, this seems like a tough problem to solve, since denoising strength in hires and denoising strength in img2img have the same name. |
And there is no way to catch the hires.fix denoising strength value and send it over to the img2img process? |
Oh should have made the request to the dev branch. My bad :| |
Describe the bug
ADetailer version: 24.3.2
If hires.fix is enabled, hires.fix denoising strength will be "always" saved as 0.4 value in the metadata of the result image (no matter what i set the value to originally).
As soon i disable ADetailer, hires.fix denoising value is saved with the correct value.
Screenshots
No response
Console logs, from start to end.
List of installed extensions
No response
The text was updated successfully, but these errors were encountered: