Image is frozen in event review typically until alarmed frames are reached?

Current Development version likely to have breaking changes
Post Reply
FlasherZ
Posts: 8
Joined: Tue Jan 31, 2023 3:45 am

Image is frozen in event review typically until alarmed frames are reached?

Post by FlasherZ »

Now that the buttons are fixed, I've noticed another problem with event playback -- the video image is frozen in event review until the alarmed frames are reached, then the video plays back just fine.

Take a look here:
https://youtu.be/Pk8zJf7qK8Q

You can see the timestamp is frozen at 14:16:24 until the first alarm frame is hit in the playback, then it jumps to 14:16:37 and plays back to the end of the event.

The monitor is set up for camera passthrough, 15 fps (both camera & monitor)

Monitor buffer settings:
Image Buffer Size: 4
Max Image Buffer Size: 600
Warmup Frames: 0
Pre Event Image Count: 150
Post Event Image Count: 150
Stream Replay Image Buffer: 0
Alarm Frame Count: 1

Note that when I download the .mp4 from the event, it has really weird timing (60,000 hours or so as a duration), and will display about 1 frame every 3-4 seconds in both media player and Windows photos.

This used to work without this behavior prior to 1.37.30, but I can't tell you when it broke. Ideas?
User avatar
iconnor
Posts: 2879
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: Image is frozen in event review typically until alarmed frames are reached?

Post by iconnor »

I made a change to do with locking for freebsd.

This is now the second report of weird things happening as a result (my systems work fine). One thing in common with the other report is the huge pre-event count.

I have to believe that there are tons of warnings in the logs.
FlasherZ
Posts: 8
Joined: Tue Jan 31, 2023 3:45 am

Re: Image is frozen in event review typically until alarmed frames are reached?

Post by FlasherZ »

No warnings at all. I had INF logging turned off, so I just turned it back on to see if it produces any more information, will come back with anything after it records another couple of events.
FlasherZ
Posts: 8
Joined: Tue Jan 31, 2023 3:45 am

Re: Image is frozen in event review typically until alarmed frames are reached?

Post by FlasherZ »

Nothing in the logs for an event tonight... the video starts with a still frame with timestamp 20:50:04, then starts moving at 20:50:18 and then the rest of the clip is just fine...

02/02/23 20:50:07.692532 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 35100 - Capturing at 15.02 fps, capturing bandwidth 507518bytes/sec Analysing at 15.02 fps]
02/02/23 20:50:14.352019 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 35200 - Capturing at 15.02 fps, capturing bandwidth 507054bytes/sec Analysing at 15.02 fps]
02/02/23 20:50:17.265446 zmc_m1[4113].INF-zm_monitor.cpp/2077 [Driveway: 35242 - ExtAlm - Gone into alarm state PreAlarmCount: 0 > AlarmFrameCount:1 Cause:Motion:Downroad]
02/02/23 20:50:17.278796 zmc_m1[4113].INF-zm_monitor.cpp/2199 [Driveway: 35218 - Opening new event 3830042, alarm start]
02/02/23 20:50:17.279391 zmc_m1[4308].INF-zm_videostore.cpp/553 [some options not used, turn on debugging for a list.]
02/02/23 20:50:17.456965 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35221 - Gone into alert state]
02/02/23 20:50:17.677644 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 35224 - ExtAlm - Gone back into alarm state]
02/02/23 20:50:17.721521 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35225 - Gone into alert state]
02/02/23 20:50:18.081500 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 35230 - ExtAlm - Gone back into alarm state]
02/02/23 20:50:18.401580 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35235 - Gone into alert state]
02/02/23 20:50:19.532013 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 35252 - ExtAlm - Gone back into alarm state]
02/02/23 20:50:21.028134 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 35300 - Capturing at 14.98 fps, capturing bandwidth 504532bytes/sec Analysing at 14.98 fps]
02/02/23 20:50:23.740658 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35315 - Gone into alert state]
02/02/23 20:50:24.411575 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 35325 - ExtAlm - Gone back into alarm state]
02/02/23 20:50:26.342361 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35354 - Gone into alert state]
02/02/23 20:50:26.767760 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 35360 - ExtAlm - Gone back into alarm state]
02/02/23 20:50:27.695050 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 35400 - Capturing at 15.00 fps, capturing bandwidth 471601bytes/sec Analysing at 14.85 fps]
02/02/23 20:50:34.354734 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 35500 - Capturing at 15.02 fps, capturing bandwidth 516435bytes/sec Analysing at 14.42 fps]
02/02/23 20:50:41.028895 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 35600 - Capturing at 14.98 fps, capturing bandwidth 481730bytes/sec Analysing at 15.58 fps]
02/02/23 20:50:47.346299 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35669 - Gone into alert state]
02/02/23 20:50:47.701313 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 35700 - Capturing at 14.99 fps, capturing bandwidth 490159bytes/sec Analysing at 15.14 fps]
02/02/23 20:50:47.963951 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 35678 - ExtAlm - Gone back into alarm state]
02/02/23 20:50:48.801903 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35691 - Gone into alert state]
02/02/23 20:50:49.288632 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 35698 - ExtAlm - Gone back into alarm state]
02/02/23 20:50:49.332323 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35699 - Gone into alert state]
02/02/23 20:50:49.683617 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 35704 - ExtAlm - Gone back into alarm state]
02/02/23 20:50:49.738445 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35705 - Gone into alert state]
02/02/23 20:50:50.491355 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 35716 - ExtAlm - Gone back into alarm state]
02/02/23 20:50:51.421282 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35730 - Gone into alert state]
02/02/23 20:50:54.364977 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 35800 - Capturing at 15.01 fps, capturing bandwidth 503371bytes/sec Analysing at 15.01 fps]
02/02/23 20:50:56.946643 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 35813 - ExtAlm - Gone back into alarm state]
02/02/23 20:50:57.337335 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35819 - Gone into alert state]
02/02/23 20:51:01.030543 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 35900 - Capturing at 15.00 fps, capturing bandwidth 508374bytes/sec Analysing at 15.00 fps]
02/02/23 20:51:03.755126 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 35915 - ExtAlm - Gone back into alarm state]
02/02/23 20:51:06.202803 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 35952 - Gone into alert state]
02/02/23 20:51:07.699202 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 36000 - Capturing at 15.00 fps, capturing bandwidth 505166bytes/sec Analysing at 15.00 fps]
02/02/23 20:51:14.366210 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 36100 - Capturing at 15.00 fps, capturing bandwidth 509471bytes/sec Analysing at 15.00 fps]
02/02/23 20:51:15.482156 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 36091 - ExtAlm - Gone back into alarm state]
02/02/23 20:51:16.015535 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 36099 - Gone into alert state]
02/02/23 20:51:16.674863 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 36109 - ExtAlm - Gone back into alarm state]
02/02/23 20:51:16.752165 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 36110 - Gone into alert state]
02/02/23 20:51:18.015928 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 36129 - ExtAlm - Gone back into alarm state]
02/02/23 20:51:18.328408 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 36134 - Gone into alert state]
02/02/23 20:51:18.958526 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 36143 - ExtAlm - Gone back into alarm state]
02/02/23 20:51:21.027193 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 36200 - Capturing at 15.01 fps, capturing bandwidth 505003bytes/sec Analysing at 15.01 fps]
02/02/23 20:51:25.329348 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 36239 - Gone into alert state]
02/02/23 20:51:25.416241 zmc_m1[4113].INF-zm_monitor.cpp/2111 [Driveway: 36240 - ExtAlm - Gone back into alarm state]
02/02/23 20:51:25.594033 zmc_m1[4113].INF-zm_monitor.cpp/2132 [Driveway: 36243 - Gone into alert state]
02/02/23 20:51:27.690376 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 36300 - Capturing at 15.01 fps, capturing bandwidth 509931bytes/sec Analysing at 15.01 fps]
02/02/23 20:51:34.353710 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 36400 - Capturing at 15.01 fps, capturing bandwidth 509655bytes/sec Analysing at 15.01 fps]
02/02/23 20:51:35.592058 zmc_m1[4113].INF-zm_monitor.cpp/2139 [Driveway: 36393 - Left alarm state (3830042) - 1343(595) images]
02/02/23 20:51:35.592154 zmc_m1[4113].INF-zm_monitor.cpp/2147 [Driveway: 36393 - Closing event 3830042, alarm end]
02/02/23 20:51:41.034773 zmc_m1[4067].INF-zm_monitor.cpp/1718 [Driveway: 36500 - Capturing at 14.97 fps, capturing bandwidth 505284bytes/sec Analysing at 14.97 fps]
FlasherZ
Posts: 8
Joined: Tue Jan 31, 2023 3:45 am

Re: Image is frozen in event review typically until alarmed frames are reached?

Post by FlasherZ »

I did some more experimentation today and reduced the number of pre-event count by a factor of 2, then another factor of 2. In each case it cut down the number of frozen frames/duration of frozen video by half, but the video doesn't update until I hit the alarm/trigger frames.
User avatar
iconnor
Posts: 2879
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: Image is frozen in event review typically until alarmed frames are reached?

Post by iconnor »

I set a cam to 150 pre event count and my events play perfectly. So, going to need a level 4 debug log. And maybe a sample .mp4
ScottyG
Posts: 6
Joined: Sat May 22, 2021 12:33 am

Re: Image is frozen in event review typically until alarmed frames are reached?

Post by ScottyG »

I too am having the same issue, it began with v1.37.31... i downgraded to 1.36.32 for now.... thanks.
User avatar
iconnor
Posts: 2879
Joined: Fri Oct 29, 2010 1:43 am
Location: Toronto
Contact:

Re: Image is frozen in event review typically until alarmed frames are reached?

Post by iconnor »

Problem is fixed in both master and proposed.
FlasherZ
Posts: 8
Joined: Tue Jan 31, 2023 3:45 am

Re: Image is frozen in event review typically until alarmed frames are reached?

Post by FlasherZ »

Confirmed. Thank you!
Post Reply