Basic camera/zm settings (I read all the FAQ's)

Forum for questions and support relating to the 1.32.x releases only.
Post Reply
winstontj
Posts: 28
Joined: Tue Aug 06, 2019 7:56 pm

Basic camera/zm settings (I read all the FAQ's)

Post by winstontj »

Starting a new thread so I don't hijack another... Read the FAQ and am looking for help so I don't fill up hard disks like crazy.
snake wrote: Mon Sep 09, 2019 4:47 pmHijacking this thread, but the solution to this problem is H264 encoding and H264 Passthrough.


Thanks snake... You said H264. We are doing this at our home so she and I have both made changes on things. When I log into the actual cameras I see that she's got the main stream set as H264 but the sub stream is set to H265. When I click the dropdowns I see that we have a choice of H264, 265 and 265+. (I'll Google it and the differences)

We have our resolutions set at 2048x1536 and frame rate at 15fps. Bit type is "VBR" (no idea what that means). I've read that 3-5fps should be fine and only places like banks/casinos use 15++fps frame rates. When we drop down below 15fps it gets jumpy and playback is terrible. We are having a problem with our neighbor and we want to be able to capture everything we can. If I could I'd increase the frame rate and resolution but at that rate it might be cheaper to start pricing out closing costs and moving trucks vs. the cost of hard drives and maintaining that much data.

Am I asking the impossible/unicorn/doesn't exist? I want max frame rate and resolution at something less than 1tb per week (that's only two cameras and we want to go up to eight). I'll look into 264,5, and 5+ so I understand it better. I'm new to cameras and all this stuff but not new to command line, tech, computers/servers or networking.


I have a couple basic questions and didn't know where to ask them:

Stupid stuff is happening like the reflection of the clouds (yeah clouds in the sky) in her and my car windshields are causing motion events. We don't always park on the same side and we don't always park in the same spot (for example, if I have garage door open working on the honey-do list/projects). I want to record all cars coming/going in our driveway but I don't need a cloud in the sky creating a motion/record event.

Other stupid stuff like the garden/flowers moving when it's windy. or the neighbor's flag blowing in the wind. I want to be able to record/capture all of the foreground (close) and as much accurate background (distant) as I can so when batshit neighbor next to us makes up the next story we can ask "hey neighbor across the street, your car was in driveway, were you home and did you see anything during xyz time" --but I also don't want that same neighbor's American flag blowing in the wind causing constant motion events such that I'm recording 24/7.


What I want is a slow and constant fps capture rate --something like 3-5fps 24/7/365. Then when ZM detects an event I want zm to be able to bump up the fps rate to whatever it wants to (as high as possible for that event). But then when the event is over I want it to drop back down and not keep filling HDD. Currently it's like everything is a motion event and it's constantly recording.


Not sure if I should tweak settings at the camera or at ZM (or some combo of both). At same time I'm being very serious: I've done big data stuff professionally (multiple racked 4u chassis full of 3.5" HDD). I know the cost of data as well as the cost of boxes, packing tape and a moving truck. Neighbor is seriously batshit. I want to cut down (or be able to highly compress and archive) daily data so it's manageable. I just don't know what to expect or if what I want is possible at that resolution and frame rates. We have two cameras and want to get up to 8 cameras ASAP. It would be cheaper to move than buy HDD or pay for online storage at a rate of 4TB/week. I'm even finding that bugs (moths) are creating motion events at night when the IR camera is on.

The local/LAN network infrastructure and resources I'm giving to the ZM esxi virtual machine are plenty fine it's just that the motion events are causing the thing to essentially constantly record. Looking for any tips/pointers on how to filter out certain things (but not others) so it's not constantly recording. Happy to create other VMs to offload some processes. I've done some CUDA and deep learning/AI stuff. I've read that there's face and/or automobile/car/truck recognition software (maybe packages, maybe add-ons??). Is there a way to do something like "that's a car and within 3-5fps it's not moving so put a box around it and ignore motion within that box unless the car moves again? Or a way to filter out bugs/moths at night? Thanks.
CountyLine
Posts: 63
Joined: Thu Aug 29, 2019 5:22 pm
Location: USA

Re: Basic camera/zm settings (I read all the FAQ's)

Post by CountyLine »

VBR usually = Variable Bit Rate. The bit rate varies depending on the amount of data in the stream at any give time. The cameras usually offer fixed bit rates as well. You can try those and see if they make any difference.

To get rid of the bugs at night I had to disable the IR LEDs on the cameras and mount external IR light sources offset several feet from the camera. If there is any other practical way to do it in bug country, I don't know what it is.
Last edited by CountyLine on Mon Sep 09, 2019 10:31 pm, edited 1 time in total.
User avatar
snake
Posts: 337
Joined: Sat May 21, 2016 2:20 am

Re: Basic camera/zm settings (I read all the FAQ's)

Post by snake »

For H264 encoding and passthrough, read this to get an understanding. You should use passthrough if possible for a performance gain. Encode is for MJPEG cameras, typically.
https://zoneminder.readthedocs.io/en/st ... torage-tab

For the zones configuration, this is the link you'll need:
https://wiki.zoneminder.com/Understandi ... or_Dummies
Post Reply