Anyone know why Zoneminder says "Time to next event = 1594938269 seconds" when attempting to play back recordings & how to fix this? It never used to do behave like this, it only started with software versions released from approx 1.5 - 2 years ago. The number of seconds decrements but I've never waited to see if my next 'event' actually plays.
Time to next event = 1594938269 seconds
Re: Time to next event = 1594938269 seconds
I am also looking for an answer on this. In my case the playback works most of the time. Typically when this happens it is partway through a segment when it displays the text. But if I retry I get it to play sometimes. I searched for fixes for this and only came up with stuff that was over 5 years old. Might want to post your version and some more details. I posted on this in a separate thread yesterday.
Re: Time to next event = 1594938269 seconds
I have the exact same problem after upgrading to 1.34.16 from 1.32.? My detailed previous post relates to "Fast Forward" and "Time to next event" issues.
I initially had my camera's Source incorporating the "Remote" method. After reading a bunch of posts I discovered the preferred method is ffmpeg. Once I reconfigured my cameras to use ffmpeg the "Time to next" reduced significantly. However, it's still there. If you're already using ffmpeg, I have nothing more to offer. I'd be interested in a definitive solution too. Welcome to the club
I initially had my camera's Source incorporating the "Remote" method. After reading a bunch of posts I discovered the preferred method is ffmpeg. Once I reconfigured my cameras to use ffmpeg the "Time to next" reduced significantly. However, it's still there. If you're already using ffmpeg, I have nothing more to offer. I'd be interested in a definitive solution too. Welcome to the club
Re: Time to next event = 1594938269 seconds
Thanks but already using ffmpeg as source.
Re: Time to next event = 1594938269 seconds
There is a lot of work to do in event streaming sadly. I fix one thing, break another.
I'll take a look and see if I can recreate it. May not get the fix in for 1.34.17 but def for .18.
probably what is happening is that we are missing a bounds check and so getting a zero for the timestamp of the current frame, and the next is
1594938269 which is Thursday, 16 July 2020 22:24:29
I'll take a look and see if I can recreate it. May not get the fix in for 1.34.17 but def for .18.
probably what is happening is that we are missing a bounds check and so getting a zero for the timestamp of the current frame, and the next is
1594938269 which is Thursday, 16 July 2020 22:24:29
Re: Time to next event = 1594938269 seconds
iconnor
FWIW, there's a lot of features in 1.34.16 that I didn't know I needed until I saw them. I do understand it takes a LOT to accomplish what you've already done in this new release. Thanks for all your efforts! - Tim
FWIW, there's a lot of features in 1.34.16 that I didn't know I needed until I saw them. I do understand it takes a LOT to accomplish what you've already done in this new release. Thanks for all your efforts! - Tim