ZoneMinder Forums

The width and height you enter should be what the camera is sending... not what you want it displayed as.

The problem with 4k cameras is that everytime you double the resolution, you are actually multiplying by 4. So 4k res takes a lot more ram. default buffers is 50, so 16 cameras * 50 * 3840 x 2160 *4bytes per pixel = 26Gb of ram. Which needs to be < half of ram. So you will be wanting around 64Gb of ...

events delete is fixed in master. mootools error is unrelated.

New up to date packages should be available for jessie, stretch, sid, buster

The code tries to calculate how much time it should sleep to achieve the framerate. But it doesn't know how long ffmpeg will take to do the decoding. You would think that a sufficiently high fps would result in no sleeping but it does. I could probably improve the sleep code, but it is more correct ...

If you want zoneminder with x264 encode you will have to get it from zmrepo. I have just now made available there there requisite mp4v2 libraries and new master snapshot built using it. These are for amd64... still working on raspbian.

I'll be here when you are ready

I should mention... I have been planning... for like 6 months now... to start a youtube channel where I go through a lot of this stuff. So stay tuned. I might get to it soon. (I bought a green screen, so I'm inching towards it)

yes

These logs don't show a failure to connect, they show an unassigned destination image format. Normally we choose this in the monitor... 24bit, 32bit, 8bit whatever. Very wierd.

Some people reported a performance hit but MOST saw a big improvement.

You can still store to jpegs OR you can store to a .mp4, or both.

first step, clear your max fps fields they will just starve ffmpeg for cpu.

second if that doesn't help is upgrade to latest master and see if i havn't already fixed the problem.

I should have buster packages available by tuesday. debian requires using zmrepo.zoneminder.com

The defaults I find don't work well with modern cameras. I start with best high sensitivity and then change the minimums to 1% or less. Keep reducing until I get too many events.

Look guys, I have fixed a lot of issues since 1.32. If you are having troubles, the first thing to do is upgrade to latest master. Then if still having troubles I can probably fix it pretty quick. 1.33 is not the big breaking upgrade that 1.32 was. More of a refinement. Also I need more testers

I don't think this is a ZM problem. The only thing I can think of is that it doesn't like the resolution. It might be interesting to try a more standard res like 640x480.