Time to next event = 1594938269 seconds

Forum for questions and support relating to the 1.34.x releases only.
Post Reply
B F
Posts: 29
Joined: Sat May 05, 2012 5:06 pm

Time to next event = 1594938269 seconds

Post by B F » Fri Jul 17, 2020 8:35 am

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.png
time-to-next-event.png (10.66 KiB) Viewed 384 times

JimS
Posts: 13
Joined: Sun Feb 18, 2007 3:16 pm

Re: Time to next event = 1594938269 seconds

Post by JimS » Fri Jul 17, 2020 11:15 am

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.

brazil
Posts: 5
Joined: Thu Mar 15, 2012 1:12 am

Re: Time to next event = 1594938269 seconds

Post by brazil » Sat Jul 18, 2020 2:53 pm

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 ;-)

JimS
Posts: 13
Joined: Sun Feb 18, 2007 3:16 pm

Re: Time to next event = 1594938269 seconds

Post by JimS » Sat Jul 18, 2020 4:17 pm

Thanks but already using ffmpeg as source.

User avatar
iconnor
Posts: 1345
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: Time to next event = 1594938269 seconds

Post by iconnor » Sat Jul 18, 2020 4:45 pm

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

brazil
Posts: 5
Joined: Thu Mar 15, 2012 1:12 am

Re: Time to next event = 1594938269 seconds

Post by brazil » Sun Jul 19, 2020 12:05 am

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

Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests