Closed olamedia closed 12 months ago
For openpose, if you have a script that can improve detection accuracy, I would suggest directly add that to ControlNet's openpose detection preprocessor, instead of doing a post process script.
Also, for now if you really want to correct the inaccurate detections in openpose, we have the integrated openpose editor to do that job: https://github.com/huchenlei/sd-webui-openpose-editor
It's to modify already generated maps. For openpose it should be possible to calculate and fix impossible angles and proportions (for specific body type) automatically.
I like this editor, but script would be able to perform this in batch.
An example of postprocessing for openpose can be opensim which can "constraining angles to a biomechanically accurate model" - a conversion to the opensim is already exists as https://github.com/perfanalytics/pose2sim#with-openpose
Here is another example of correction script https://github.com/DGS-Korpus/Public-Corpus-OpenPose-error-corrector
What problem the feature is trying to solve: Postprocess generated maps. For example, script that loads openpose json, and trying to fix pose using various models.
Expected workflow for user:
Expected workflow for script: