Skip to content

[codex] Fix Visora EgoForce sync and diagnostics - #2

Draft
gaurangbharti1 wants to merge 4 commits into
dfki-av:mainfrom
gaurangbharti1:codex/fix-visora-egoforce-sync
Draft

[codex] Fix Visora EgoForce sync and diagnostics#2
gaurangbharti1 wants to merge 4 commits into
dfki-av:mainfrom
gaurangbharti1:codex/fix-visora-egoforce-sync

Conversation

@gaurangbharti1

Copy link
Copy Markdown

Summary

  • Fix Visora video processing to select frames from ARKit timestamp rows and read those exact frame indices, avoiding RGB/ARKit/LiDAR desync on VFR MP4s.
  • Disable stale YOLO detector tracking/reuse by default for frame-level EgoForce inference.
  • Add browser-playable Visora runner, jitter analyzer, and pipeline visualization scripts for step-by-step debugging.
  • Make inference imports and RSS lifting more robust in the local environment.

Root Cause

The problematic Visora MP4 could not be reliably processed with naive OpenCV sequential frame reads after seeking. RGB frames, ARKit rows, and LiDAR depth could drift out of sync, making EgoForce outputs look explosively unstable.

Validation

  • python -m py_compile camera_models/__init__.py core/rss.py demo/demo_utils.py demo/inference.py scripts/run_visora_video.py scripts/analyze_visora_jitter.py scripts/visualize_egoforce_pipeline.py
  • Ran row-synced jitter analysis and generated H.264 overlay/pipeline MP4s locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant