-
Notifications
You must be signed in to change notification settings - Fork 2
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
nsfwrecog_v1 censors too much #76
Comments
When selecting this model I get |
thank you for your reporting
you can add the following ["EXPOSED ANUS",
"EXPOSED ARMPITS",
"COVERED BELLY",
"EXPOSED BELLY",
"COVERED BUTTOCKS",
"EXPOSED BUTTOCKS",
"FACE F",
"FACE M",
"COVERED FEET",
"EXPOSED FEET",
"COVERED BREAST F",
"EXPOSED BREAST F",
"COVERED GENITALIA F",
"EXPOSED GENITALIA F",
"EXPOSED BREAST M",
"EXPOSED GENITALIA M",
"EXPOSED BACK F",
"EXPOSED BACK M",
"DILDO"] |
Another bug: neither nsfwrecog_v1 nor any other module that works with object classes will restore its configuration, even if it is saved using A1111's Setting > Other > Defaults > View changes > Apply sequence. This sequence saves changes to uddetailer's config into webui/ui-config.json. Most settings are restored, with the exception of object classes. Here's what appears in the ui-config.json:
However, after A1111 is restarted, these object classes are not loaded. Moreover, as MitPitt commented last week, object classes do not even appear next to the combo box. One has to select a different detection model, then re-select nsfwrecog_v1 to just make the selection box show up, and then re-select all the object classes. Suggestion: display object classification list correctly after restart; load object classes on startup. |
Besides NSFW, it also detects face and covered parts of the body. Instead, it should be possible to choose which classes are to be censored.
The text was updated successfully, but these errors were encountered: