1.29.0 feed delay...?

[McFuzz]

I have a 5 camera setup - 4 are wired and one is wireless. Three of the cameras record on motion, one (wired) records on trigger only (from any of the three that record on motion) and the wireless one is simply a baby monitor.

I discovered that one of my record-on-motion cameras has had its feed delayed by nearly 10 seconds. Viewing it on the cameras own interface shows perfect sync but not through ZoneMinder (though alerts were recorded properly). Had to reboot the ZM box before it synced properly.

Any ideas or is this something to just live with?

[knight-of-ni]

Did you place a value in either of the MAX FPS fields?

[McFuzz]

Yes I did - but they are identical to across all my motion-recording cameras.

[knight-of-ni]

Is the value in the MAX FPS field equal to or less than the fps coming from the camera?
If yes, then there is your answer. You are describing the very symptom why we put a big red CAUTION note indicating you should read the help text.

[McFuzz]

Hrm - I think I know what's going on. The MAX FPS is not more during the day, but during the night, when IR kicks in, the actual FPS gets halved...

Anyway to combat that?

[knight-of-ni]

Those fields do not work for ip streams the way you want them to. That is why we put the warning there.

The simplest thing to do would be to put a value in there that is higher than the camera's frame rate, at any time of the day. The only reason to do this is to keep your cpu from jumping to 100% if one of the cameras falls off the network. If this has not been an issue for your system/network, then you should leave these fields empty.

[McFuzz]

Ahhh - ok; I'll put them at 0 and double check on stuff but it shouldn't be a problem. These cameras are pretty solid.

[knight-of-ni]

I would leave them empty, rather than put a zero in there. Not sure if it makes a difference, but if it just happens that it does make a difference, it won't be good.