erkme73
Silver Member
Okay downloaded Blue Iris... free 15 day demo version. Plugged in a camera to the POE switch I added to the network. Stuff not mounted just trying it out.
Had a little trouble getting the camera to be recognized. Wouldn't 'auto find'. Logged into my router and found the static IP for the camera 'on the map'. Added that and I got the old familiar colored vertical rainbow bars (remember those... when the TV network went off air late at night?). A few seconds later the camera went live!
First thing I noticed is that all the youtube videos I watched on set up of Blue Iris need to be watched again!
Second thing I noticed is that the default settings just for one 5Mp camera was taxing my CPU and RAM. Looked at my MacBook details and learned that my 2.9Ghz Intel Core i7 processed w/16GB memory appears not nearly close enough if I am to run multiple cameras at high res. I'm thinking my MacBook isn't allocating enough RAM and CPU to my parallels desktop. I am running Windows 10 on it. More research I guess.
Third thing I noticed is that I could adjust the frame rate down from 30fps to 10fps and that helped but for some reason I could not lower the camera resolution from 2560x1920.
At least I know I can set up the cameras but I am going to need some computing power. Looks like I am going to need a dedicated PC/NAS to run this with 6+ cameras. Ugh!
This is not for the faint of heart... or should I say computer illiterates. A Lorex box system is soooo much simpler if you aren't a tinkerer.
If you're running Windows as a virtual machine (sorry, don't know how the macs work with Windows), then I suspect you're not able to utilize the full power of the hardware.
As for Blue Iris, again I would recommend going to ipcamtalk - they have a section dedicated to BI setups and configurations to eek out the most performance with the least hardware.
There are global and per-camera settings that you can configure in BI that will reduce the CPU and storage load without compromising clarity and fluidity. For example, one option is the direct-to-disc recording option - where the images from the camera are sent directly to the storage drive without first re-encoding to a different profile. It eliminates overlays and other manipulations, but it spares the CPU from having to redraw every frame from every camera.
There are also options to offload some of the computations from the CPU to the graphics processor (GPU) from certain hardware manufacturers (i.e. Nvidia or Intel graphics cards).
Reducing the frame rate to 10 yields reasonably fluid recordings, while reducing the system load by 60%. Here's a nice comparison of frame rates: CCTV Security Camera Video Recording Frame Rate Comparison - YouTube
High-traffic areas you may want to keep at 15 or 20, and those with little activity or lower interest, keep them at 10. But, by far, the single biggest improvement on CPU load is the reduction of the resolution of the camera.
FWIW, you can pick up higher-end windows PCs (including current generation i7s) as manufacturer refurbs for around $500. I picked up an Acer years ago, and it's running w/o any issues. I don't have anything hooked up to it (no keyboard or monitor) as I use free TeamViewer to log in when needed.
And with Blue Iris recently adding UI3 web interface, you can make many of the per-camera changes from any browser on your network.