The longer Pi5 is up, the more frameskips are likely to happen.
Simple countermeasure:
In order to get better timestamp.py analysis with "--narrow" option in case frameskips are likely, I added "narrow" environment variable handling to GScrop:
https://gist.github.com/Hermann-SW/e604 ... 4e0e9f6b9c
Only two frameskips for requested 536fps framerate not that bad for 4 days uptime:
P.S:
Reading bash man page, this was what I needed:empty if "narrow" environment variable is undefined, otherwise "--narrow".
Simple countermeasure:
reboot before final recording
In order to get better timestamp.py analysis with "--narrow" option in case frameskips are likely, I added "narrow" environment variable handling to GScrop:
https://gist.github.com/Hermann-SW/e604 ... 4e0e9f6b9c
Only two frameskips for requested 536fps framerate not that bad for 4 days uptime:
Code:
pi@raspberrypi5:~ $ uptime 21:11:06 up 4 days, 19:22, 2 users, load average: 0.60, 0.57, 0.38pi@raspberrypi5:~ $ pi@raspberrypi5:~ $ narrow=1 GScrop 224 96 536 2000/dev/media2...Total: 1054 frames (1053 samples)Average: 1.870 ms / 534.697 fpsMinimum: 1.861 ms at frame 146Maximum: 3.737 ms at frame 129Outliers: 0 (100%) 2 (10.0%) 2 (1.0%) 1022 (0.1%)P.S:
Reading bash man page, this was what I needed:
Code:
${narrow:+--narrow}Statistics: Posted by HermannSW — Fri Jan 19, 2024 8:10 pm