Skip to content

Conversation

@m-RNA
Copy link
Contributor

@m-RNA m-RNA commented Dec 21, 2025

Fix: #24

Summary:

  • Fix FPS computation so 100-frame windows no longer truncate to 0 fps; use math with divide-by-zero guard.
  • Correct initial timestamp handling to avoid incorrect timing on the first logged window.
  • Optimize logging by only doing the 100-frame timing/size calculations when the log level is INFO, minimizing overhead when info logs are disabled.

Before:

I (1863) main_task: Returned from app_main()
I (3863) [STREAM_SERVER]: Size: 5KB, Time: 8341ms (0fps)
I (6109) [STREAM_SERVER]: Size: 5KB, Time: 2245ms (0fps)
I (8360) [STREAM_SERVER]: Size: 5KB, Time: 2251ms (0fps)

After:

I (6330) main_task: Returned from app_main()
I (9513) [STREAM_SERVER]: 100 Frames Size: 4KB, Time: 2250ms (44fps)
I (11788) [STREAM_SERVER]: 100 Frames Size: 4KB, Time: 2275ms (43fps)
I (14031) [STREAM_SERVER]: 100 Frames Size: 4KB, Time: 2244ms (44fps)

@m-RNA m-RNA force-pushed the Fix-FPS-reporting branch 2 times, most recently from 3057b02 to 5bb8c5b Compare December 22, 2025 19:24
@m-RNA m-RNA force-pushed the Fix-FPS-reporting branch from 5bb8c5b to 31f8ac3 Compare December 22, 2025 19:30
@lorow lorow merged commit f1acb5d into EyeTrackVR:main Dec 31, 2025
26 checks passed
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.

Bug: fps reported by STREAM_SERVER LOG is always 0

2 participants