I No trust on camera motion detection, they tends to give many false triggers.Depending on what VMS you use.. you could do something like 4 FPS constant and then bump it up on motion.
Try to keep the motion detection on the camera.. pretty much all cameras support it.. and then there is no load on your CPU.
Your recording storage numbers seem off... I ran them through AXIS Design Tool | Axis Communications which we typically use.. and get way less hard drive usage...
can I have one wins 8 license?...... just asking :-DI just run BI alone on that VM. No biggy since I can license as many copies of windows 8 as I like.
It's a cpu pig. With 8 HD cams @30fps it verages about 33% of an 8 core Avoton and about 3MB ram using the balloon driver.
you can try ZM, this takes weeks to learn configuring OpenSource ZM........
I use Hikvision cameras, so I use their free iVMS-PCNVR software and iOS app. Mainly because it's free, and it allows me to do motion detection on the cameras themselves so the VM has zero CPU usage unless an event is triggered. It runs inside a Windows VM which is also isolated from directly accessing the internet.
I've been wanting to start an open source project for a long time to build a dedicated linux-based IP camera NVR package, but haven't really gotten it off the ground...
I ran ZM for a while. It was maxing out CPU on 2 cameras at the time and using a ton of storage space since it converts everything to MJPEG. It has been around for a long time and I'm not sure if they've updated the internals yet to allow native streams of encoded video from an IP cam versus individual frames from a capture card. This was an active project on their github issue tracker last time I looked at ZM.you can try ZM, this takes weeks to learn configuring OpenSource ZM.
motion detection does not much cpu processing in ZM ( well, depends on configuration that you pick). the most processing bound is during recording.
Ehem; I am using broken LCD core 2 duo laptop, and plan to move to VM (proxmox).
They only stay valid on VMs inside my AD domain. License is via a copy of Server 2012 r2 Datacenter edition. Sorry.can I have one wins 8 license?...... just asking :-D
Zoneminder is FOSS and you can (and should) run it on a hardened Linux machine. There is no other software that comes close to it's motion detection ability IMO.I honestly have no idea what's out there, what they cost and the benefits.
I just know Blue Iris is "clunky" but it works.
I probably wouldn't want to spend more than $200-400$ for Software / OS for the security camera system.
I have 2 mjpeg cameras on my cor2 duo laptop. yap cpu shoots to 80% max when recording mjepg simultaneosuly.I ran ZM for a while. It was maxing out CPU on 2 cameras at the time and using a ton of storage space since it converts everything to MJPEG. It has been around for a long time and I'm not sure if they've updated the internals yet to allow native streams of encoded video from an IP cam versus individual frames from a capture card. This was an active project on their github issue tracker last time I looked at ZM.
Zoneminder is decent enough. I feel like it's a little rough around the edges though.
Good motion detection should allow masking, so you exclude the moving trees.
You should see if you are using libjpeg-turbo or not. Using the other (normally default) libjpeg results in much higher CPU utilization than the optimized libjpeg-turbo.I have 2 mjpeg cameras on my cor2 duo laptop. yap cpu shoots to 80% max when recording mjepg simultaneosuly.
overall current CPU processing is increased greatly. I am no worry running on VM.
if you are running X/H.264, as long as you hardware supports it. ehem... ZM only use whatever OS provides ( hardware enable or not).
I believe running on VM would only support software, Not hardware accelerated. well cpu is fast enough. planning to move proxmox 3.4 with e3 V2.
yes indeed. turbo rules....You should see if you are using libjpeg-turbo or not. Using the other (normally default) libjpeg results in much higher CPU utilization than the optimized libjpeg-turbo.