Decouple display and recording/inference FPS

[C-Achard]

Motivation

This pull request introduces several improvements to multi-camera handling, frame rate configuration, and debugging/telemetry in the codebase.
The main changes include

• Decoupled high-frequency frame processing from display updates in the GUI (set to 30 FPS)
  • Recording should now have more resources to follow requested FPS
  • Inference still uses only the latest unprocessed frame, making speed bottlenecked by inference only
  • GUI display is capped at 30 FPS now (configurable)
• Enhancing telemetry for camera frame rates, and adding utility functions for robust GenTL node values extraction
  • Fixes the incorrect FPS reporting for GenTL

Automated summary

Multi-camera frame handling and GUI update throttling:

• Separated high-frequency frame_ready signal (used for recording and inference) from the new display_ready signal (throttled to GUI_MAX_DISPLAY_FPS for efficient GUI updates) in MultiCameraController, with corresponding handler changes in main_window.py (_on_multi_frame_processing_ready and _on_multi_frame_display_ready). [1][2][3][4][5][6][7][8][9][10]
• Added GUI_MAX_DISPLAY_FPS global setting and related debug flags in config.py.
• Updated signal connections and handler names in main_window.py to reflect the separation of processing and display paths. [1][2][3]

Camera frame rate configuration and telemetry improvements:

• Improved frame rate configuration logic in gentl_backend.py to log before/after states, use more robust node selection, and set the actual FPS based on accepted values.
• Enhanced telemetry reading to prioritize resulting frame rate nodes, fall back to requested rates, and persist more telemetry data (e.g., exposure, gain, throughput, pixel format) for debugging and GUI display.

Debugging and utility enhancements:

• Added _debug_frame_rate_nodes for detailed logging of relevant GenICam node values, aiding in debugging frame rate issues. [1][2]
• Implemented utility methods _node_value, _node_float, and _node_str for robust, best-effort extraction of node values, reducing boilerplate and error handling throughout the code.

These changes collectively make the system more robust for high-performance multi-camera setups and improve the ability to debug and monitor camera settings and telemetry.

[Copilot]

Pull request overview

Decouples high-rate camera frame processing (recording/inference) from GUI display updates by introducing a separate, throttled display_ready signal capped at GUI_MAX_DISPLAY_FPS, and improves GenTL FPS configuration/telemetry with new node-reading helpers and debug logging.

Changes:

• Add display_ready signal and _should_emit_display_ready() throttling in MultiCameraController; restructure _on_frame_captured timing sections.
• Split _on_multi_frame_ready into _on_multi_frame_processing_ready (recording/inference) and _on_multi_frame_display_ready (GUI), and add GUI_MAX_DISPLAY_FPS plus debug-timing flags in config.py.
• Improve GenTL backend: add _node_value/_node_float/_node_str helpers, _debug_frame_rate_nodes, expanded telemetry (resulting vs requested FPS, exposure, gain, throughput, pixel format), and richer FPS configuration logging.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
dlclivegui/config.py	Adds GUI_MAX_DISPLAY_FPS and debug timing flags.
dlclivegui/services/multi_camera_controller.py	Adds throttled display_ready signal and refactors frame handling/timing.
dlclivegui/gui/main_window.py	Splits processing/display handlers and rewires multi-camera signal connections.
dlclivegui/cameras/backends/gentl_backend.py	Adds node-reading helpers, FPS debug logging, and broader telemetry readback.
tests/gui/test_pose_overlay.py	Updates test to use renamed _on_multi_frame_processing_ready handler.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.

[C-Achard]

Caution

Rebase before merging, this has stale duplicate commits from rebasing

[deruyter92]

Good PR, looks good to me!

(Don't forget to flip the log timing config setting back when done debugging, but you've put a reminder)