Page 4 of 4
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Sat Nov 23, 2024 12:27 pm
by eggenbef
iconnor wrote: ↑Mon Nov 18, 2024 9:28 pm
How stable is the timestamp from the cameras? Are they using ntp?
You can send me a debug level 3 log from one of them and maybe I can figure it out.
yes, both cameras are synchronized twice daily with ntp. i've attached the log to my original post on this issue (
viewtopic.php?p=136168#p136168).
please let me know should any further information/data be of help to find the root cause. thank you!
Re: zm_videostore.cpp warning on 1.36.18, was also present on 1.36.17
Posted: Mon Jan 27, 2025 1:44 am
by Quantum
domlin wrote: ↑Tue Nov 19, 2024 9:36 pmFinally out of desperation I changed network method from TCP to UDP ('Method' under 'Source' in the Monitor settings) and the issue was instantly fixed for all 3 of my monitors/cameras. Not sure if this is unique to my setup but thought i'd share in case it can help anyone else.
Thanks
Hmm, ZM 1.36.35 and MonitorSettings|Storage|OptionalEncoderParameters|reorder_queue_size=50 didn't help at all.
Which makes sense as TCP should automatically order packets at lower levels. This ffmpeg option -must- apply only to UDP. My journal is flooded.
Unfortunately I've tried setting my cameras to UDP before and it didn't work. Time to try a little harder. Should be UDP anyway...