Closed swimmingyoshi closed 1 month ago
The YOLO model's filename shows what it predicts. If we support selecting certain classes, how does the user know which class names are supported by their YOLO model? I tried to make this easier for the user without adding more "need to know" for the user, but I couldn't. I can't think of a better way than the current structure.
This feature isn't implemented because of UI problems, not implementation difficulties.
Is your feature request related to a problem? Please describe.
I have a trained YoloV8 model, that detects multiple classes. When i use it with adetailer it will always detect and detail ALL detected areas.
currently adetailer only supports classes for "-world" models. i tried changing the model name to have "-world" in it but it always returned an error.
Describe the solution you'd like
Other detailers allow you to set the classes that you want to be detailed so that the rest are ignored. for example, image contains (head, hands, and eyes) but i only want to detail (eyes, hands). the way most other detailers work is by detecting everything and then filtering the results to only keep the wanted areas.
Describe alternatives you've considered
I managed to find a work around but it involved changing the code inside of ultralytics.py. (im not 100% if i broke anything)
for it to show the "classes" text input in the UI you can just change your model to have "-world" in the name but that can be confusing, so you can also edit ui.py so it detects a new name.
in my example code, i used the word "Bean" because my models were named "YOLO_BeanV8.pt"
Additional context
No response