Skip to content

Fix DLCLive custom processor not running on every frame - #128

Open
C-Achard wants to merge 1 commit into
masterfrom
cy/fix-processor-per-frame
Open

C-Achard wants to merge 1 commit into
masterfrom
cy/fix-processor-per-frame

Conversation

@C-Achard

@C-Achard C-Achard commented Nov 3, 2026

Copy link
Copy Markdown
Member
  • _process_frame calls DLCLive._post_process_pose after runner.get_pose, with the frame's timestamp as frame_time
  • Without it, a custom processor receives only the init_inference pose, and poses stay in model-input coordinates when resize or cropping is set
  • Regression test added to run the worker against the real _post_process_pose with only the runner faked

- _process_frame calls DLCLive._post_process_pose after runner.get_pose, with the frame's timestamp as frame_time; the call was commented out in #114
- Without it, a custom processor receives only the init_inference pose, and poses stay in model-input coordinates when resize or cropping is set
- Regression test runs the worker against the real _post_process_pose with only the runner faked and resize=0.5: one process() call per frame, with its timestamp, in frame coordinates
@C-Achard C-Achard added bug Something isn't working processor Custom DLC-live processors: either base class, public API, docs or new custom examples labels Nov 3, 2026
@C-Achard C-Achard self-assigned this Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working processor Custom DLC-live processors: either base class, public API, docs or new custom examples

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant