Weird problem here.
The 2-3 first frames in the stream are out of sequence, like this:
Frame Id Type Time Stamp Time Delta Score
1 Normal 12:12:05 0.00 0
2 Normal 12:12:05 0.03 0
3 Normal 12:12:05 0.06 0
4 Normal 12:12:04 -1.56 0
5 Normal 12:12:04 -1.53 0
6 Normal 12:12:04 -1.50 0
7 Normal 12:12:04 -1.46 0
8 Normal 12:12:04 -1.43 0
Check out the time stamp! And it screws up the stream playback...
The setup:
- ZoneMinder 1.28.0
- Fedora 20 running kernel 3.17.3
- Two local cameras: The one with smaller resolution works perfectly fine. The
Creative Live with 1280x720 has this artefact.
- SHM settings: kernel.shmall = 268435456, kernel.shmmax = 536870912
- 16 GB memory
Both cameras worked until recent kernel update. Perheps the cam driver "fixed" something.
Cannot find anything relevant in the change logs though.
Could well be my settings, but cannot really find anything to tweak...
Best
Dag
Frames out of sequence
-
- Posts: 43
- Joined: Sat Oct 26, 2013 2:58 pm
Re: Frames out of sequence
I've had a similar issue, but mine freezes up also.. I'll check the timestamps as you've done..
My thread is here: http://www.zoneminder.com/forums/viewto ... 32&t=22701
My nest thing to try is to reduce the resolution of the images from the camera, as they are a bit excessive, this will reduce load on the system.
Cheers, Scott
My thread is here: http://www.zoneminder.com/forums/viewto ... 32&t=22701
My nest thing to try is to reduce the resolution of the images from the camera, as they are a bit excessive, this will reduce load on the system.
Cheers, Scott
Re: Frames out of sequence [SOLVED]
Found the reason.
Had set up the amount of frames to save before an event to 50.
Setting this to a smaller 40 made the beginning work perfectly fine again.
Guess:
There is a bug in a circular buffer handling that makes setting this value "too big" grab
some frames from a newer point in time when saving the event.
Anyway it works now.
Had set up the amount of frames to save before an event to 50.
Setting this to a smaller 40 made the beginning work perfectly fine again.
Guess:
There is a bug in a circular buffer handling that makes setting this value "too big" grab
some frames from a newer point in time when saving the event.
Anyway it works now.