Key ********
***** *** ******* *** takeaways **** *** *****:
- **% ******* ******** **** low ***** **** (*-* FPS) ** ******* (**-** FPS):** *******, ****** **** low ***** **** ** 10-15 *** (******* ** ************) ******** ** * ~15% ******** **** ***** smart ******, *** ~**% without, **** **** ********** discussed *****.
- ****** ******** (~**%) **** average ***** **** ** high:******** ********* **** ************* when ****** **** **-** FPS ** ** ***, about **% **** ***** codecs *******, *** ******** higher (~**%) **** **** disabled.
- ***** ****** ************* ****** bitrate ** *** ***** rates:***** ****** ******* ******** significantly **** *** ** night ** *** *** levels ******, ************* ~**% in *** ******** ******* scenes *** **-**% ** more ******* **** ******** night *****, ********** **** our **** *****.
- ***** ****** ****** ********* from ****** ***** *****:** **** *** *** night ******, ** *** resolutions, ***** ****** ******** the ******* ********* **** when ********** ***** ****.
- *.*** ****** ********* ** H.264:** *** *****, *.*** camera ******** ****** ************* similarly ** *.***, **** smart ****** **** ** and ***, ****** ******** were ******* ***** ** 20-30%.
- ** ******** ***** ** high ***** *****:**/*** ****** ******** ********* more ******* **** ***** and *** ******* ** high ******** ******, **** than ******** ******* **** 1 ** ** ***, while ***** *********** ********* by ~**-**%.
***** ** ***** ********, we ******* *** *** recommendations:
Recommendation *: *** ***** ******
*** ** ***** *********** benefits ** *** ***** rates ******, ** ********* that ***** ********* ****** frame ***** *** ***** codecs ******** ********. *** only ** **** ******* overall ***** ******** ****** all ***** ***** (~**-**% day/low ****** *** ~**% night/high ******), *** **** reduce *** ****** ** increased ********, ** ****. For *******, ********** ***** rate **** * *** to **-** ******* ** a ~**% ******** ***** smart ******, *** **** 30% *******.
Recommendation *: **-** *** ******* *** **** ************
***** ** ***** *****, 10-15 *** ** *********** the "***** ****" ** the ******** ******* ***** rate *** *********. ****** to **-** *** **** 3-7 *** ********* ******** by ***** **-**% **** using ***** ****** (**-**% without) ******** ** *-* FPS. ** ********, ****** from **-** *** ** 30 *** ** * much **** ******* ********, ~30-35%, ****** ** * much **** ********* ******** for *** ******* ***** additional ****** ******* ** most ************.
30 ***: +**% ******* *** +***% ******
*******, **** **** ***** 30 *** ******** ~**% more ********* **** **-** FPS, **** ***** *** find **** * ********** trade *** *** ***% more ******, ** ***% vs. ** ***. **** may ** **** ****** in ************ **** **** movement, **** ** **** intersections ** **** ******** areas ***** **** ** or ** *** *** miss ****** ********* ** for ***** **** ****** storage ******* *** ****** wish ** ******* *** most ****** ****** ********.
Note: *** * ********
**** **** ******* ** this **** **** **** to ****** ****** ** frame **** ***************. ******** ***************** ************ ************, ****** ** view *** ***** ******** varied ***** ******. ******* of ****, ******* ****** not *** ***** ************ to ******* ** ******* between ******** ******* ** resolutions. ** **** ** perform ************ ******* ** more ******* ** ******* scenarios ** *** ****** months ** ****** **** ********.
Low ****** *******
** ******* *** ***** in * ****** ******* interior *****, **** *** motion, *** ****** ***** rate **** * ** 30 *** ** **** camera.
**** ***** ***** ******, bitrates ********* ** ******* of ~**% **** ******** from * *** ** 10-15 ***, **** ******* for ************. ** ********, increasing **** ** *** to ** *** ********* bitrates ** ~**%, * more *********** ******.
**** **** ***** *** and ***/** *********** ****** fairly ********* ** **** scene, ***** ******* ****** to ******** **** ******** from *-** ***, **** a **** ******* **** at ** ***.
********* ******* ***** ****** enabled **** ******, ~**% when ******** **** * to ** ***. ** 1080p *******, ******* ********* faster ** ****** *** settings, **** ******* ********* when ****** **** * to * ** ** FPS, ******* ** **** smart ****** **** *******. Also *******, ** ****** resolutions, ******** ********* ****** at ***** ********, **** 1 ** * *** the ******* ********** ********.
Note: **** ***** ****** ***** **** ** ****
**** **** ** **** cameras, ***** ****** ******** to ***** ****/*** **** when ***** * *** frame *****, **** ******** much ****** **** ***** settings. *** *******, ** the********* **-**********-*, ******** **** ******** highest ** * *** with ***** ****** *******.
*******, ******* ** * stream ********, ** ******* that ******* *** *** disabled **** *** ****** was *** ** * FPS **** *.***+ ****** on, ***** ** ***** frame ***** ** ****** to ~** *******.
High ********** *********
** *** *** ******** increased ** **** ******* scenes, ** ****** ** a **** ***** (~*.* Lux) **** ** **, with ***** ****** ****** throughout *** *****.
***** ****** **** ******* less ********* ** *****, with ******** ~**% ***** than ***-***** ***** *********, less **** *** ~**% reductions **** ** *** daytime ***** *****.
**** ******* ** **** scene, ***/** ****** ******** increased **** **** ******* than *** ** ***** cameras **** ********** *******. While ***** ***** ***** and *** ******* ********* only ~**% ** ******* when ****** **** * to ** ******** ** ** ***, average ******** ** ***/** cameras **** **** ****** when ******** **** * to ** ***, *** increase ** **** **% when ****** **** ** to ** ***.
*** **** *** **** with ***** ****** ********. 1080p *** *** ******* both ********* ********, *** less **** ******, ***** 8MP/4K ****** ******** **** than ******. **** **** 1080p/4MP ********* **** **** significant **** **** ***** codecs *******, ~**-**% **** moving **** *-** *** (vs. ~**%) *** **-**% when ******** **** ** to ** *** (**** vs. ~**%)
H.265 ****** ********* ** *.***
****** *** ****** ******, H.265 ****** ********* ** H.264, **** ********** ***** overall ********. ***** *.*** models **** ******, ****** because ***** ****** *** available, *** ****** ******** overall *******.
*** *******, ** *** nighttime **** ********** *****, both *.*** *** *.*** trended ******* ** ******* rates. *.*** ******** ******** about **% ***** ** this *****.
**** *** **** ** all ****** ******, *******, nighttime, **** *** ******* smart ******.
Cameras ******
*** ********* ******* **** used ** **** ****:
- **** *****-*** ** **
- **** *****-***
- **** *****-***
- **** *****-*** ** **
- ********* **-**********-*
- ********* **-**********-*
- ********* **-*********-***
- ****** ***-*****
- ****** ***-*****
- ****** ***-*****
Comments (9)
Sergey Bystrov
01/23/19 09:02pm
MPEG(H.264, H.265) compression is based(among other things) on image correlation between frames. More noise => less correlation between frames => less compression.
Big sensors => small pixel size => more noise(especially at night) => less correlation between frames => less compression.
But still surprised 8MP did so much different at night.
Looks like such cameras frequently should be used with a lower resolution during the night. If let's say 4 pixels downscaled to 1(which I believe camera simply does if the smaller image size is requested, it's denoise spatial filter by itself ).
I wonder how your 8mp cameras would behave at night if used as 2MP camera. And are the results consistent across cameras in this case?
Create New Topic
Donald Gordon
Great article. Your findings correlate well with what we have identified during our day and night testing with 1080p cameras and 8MP cameras. In a site with several hundred cameras, we always see a handful of 8MP cameras that increase their nighttime bandwidth well beyond the other cameras (20mbps to 100mbps). These cameras typically have much more digital noise caused by a number of factors including dirty lenses, IR illuminator energy reflecting off of adjacent structures, IR illuminator energy from other adjacent cameras illuminating the problem camera, street and building lights shining into the cameras, floating debris in the air (dust and dirt), and insects flying around the cameras.
Create New Topic
Vin Imbesi
Great article! It would be nice to add a section regarding the impacts that these compressions have on server and workstation system requirements.
Minimal improvements in throughput, for example, may not be worth the additional horsepower that would be necessary in these scenarios.
Create New Topic