Video Quality / Compression Tutorial

By: IPVM Team, Published on Oct 17, 2018

While CODECs, like H.264, H.265, and MJPEG, get a lot of attention, a camera's 'quality' or compression setting has a big impact on overall quality. In this training, we explain what this level is, what options you have and how you should optimize it.

To start, review these two images, (A) and (B):

camera a camera b

And answer this question before continuing:

With the information presented, the best answer is that it cannot be determined. We used the same camera for each image and simply increased compression for the 'B' image (while keeping everything else the same, including resolution and codec).

The fact that two exact shots with the same resolution can look significantly different has a number of important implications. Inside, we explain why, covering:

  • Quantization levels
  • Bandwidth vs. quality loss
  • Image quality examples
  • Manufacturer differences
  • MBR/VBR/CBR impact
  • Smart codec impact
  • Recommendations

Quantization Levels

Regardless of codec used (H.264, H.265, MJPEG, etc.), all IP cameras offer quality levels, often called 'compression' or 'quantization'.

H.264 and H.265 quantization is measured on a standard scale ranging from 0 to 51, with lower numbers meaning less compression, and thus higher quality. If this seems counter intuitive to you, it is understandable, but these are simply the measurements defined in H.264 and H.265 standards.

Key Tradeoff: Bandwidth Vs. Quality Loss

The key tradeoff in setting quantization is determining how much 'loss' you are willing to accept for a particular decrease in bandwidth. All production surveillance video compression is 'lossy', meaning that some information will be lost when video is compressed, making a crucial configuration decision:

***** ******, **** *.***, H.265, *** *****, *** a lot ** *********, * camera's '*******' ** *********** setting *** * *** impact ** ******* *******. In **** ********, ** explain **** **** ***** is, **** ******* *** have *** *** *** should ******** **.

** *****, ****** ***** *** images, (*) *** (*):

camera a camera b

*** ****** **** ******** before **********:

**** *** *********** *********, the **** ****** ** that ** ****** ** determined. ** **** *** same ****** *** **** image *** ****** ********* compression *** *** '*' image (***** ******* ********** else *** ****, ********* resolution *** *****).

*** **** **** *** exact ***** **** *** same ********** *** **** significantly ********* *** * number ** ********* ************. Inside, ** ******* ***, covering:

  • ************ ******
  • ********* **. ******* ****
  • ***** ******* ********
  • ************ ***********
  • ***/***/*** ******
  • ***** ***** ******
  • ***************

************ ******

********** ** ***** **** (H.264, *.***, *****, ***.), all ** ******* ***** quality ******, ***** ****** 'compression' ** '************'.

*.*** *** *.*** ************ is ******** ** * standard ***** ******* **** 0 ** **, **** lower ******* ******* **** compression, *** **** ****** quality. If **** ***** ******* intuitive ** ***, ** is **************, *** ***** are ****** *** ************ defined ** *.*** *** H.265 *********.

Key ********: ********* **. ******* ****

*** *** ******** ** setting quantization ** *********** *** much '****' *** *** willing ** ****** *** a ********** ******** ** bandwidth. *** ********** ************ video *********** ** '*****', ******* **** **** information **** ** **** when ***** ** **********, making * ******* ************* decision:

[***************]

  • ******** ***********/***** *** ******* level *** *** **** on *********, *** ****** quality.
  • ******** *******/****** *********** *** you *** **** ****** details, *** *** **** bandwidth *** ****** ******* time.

Demonstrated ** ********

*** ***** ***** ***** the ****** ** ******** quality ******. ** ***** to **** ****, ** took ******** **** *** scenes (****** / ****** and ******* / *******) and ******** *******. *** quantization ****** *** ** seen ********** ** **** scenes ** ******* **** up. *********, ***** ******* increases, **** **** ********** and ******** ** *******.

Manufacturer **********

*** ************* *** ******* quality ******. **** ** you ***** ***** ***** settings, *** ************ **** make * ****** *** you. *******, **** *** **** majority ** ************ *******, ************* options *** ********* ** let ******** ***** ****** this.

*****, ** **** ** a *** ************* ** better *********** ***** **********. However, ******* ****** *** our ** ****** ************ *********** Comparison **** *** **** ******* of **+ ************* *********** scales *** *** ** default ***** ******* ** "average" ***********. ** ******* from ****:

Axis *** **. *** *** *********

**** **** *** ********* web **********. **** ******* cameras *** *** ********** ***** ******* *** **** *********** and **** *** ******* browser ******* *** *.***/*.*** video. **** *** *** old *** *** ***** to ******* ** "***********", with ****** ******* ***** more **********/***** *********. ****** of ****, ** ************* users *** ****** ******** the ***** ******** ** increases ***** *******. 

*** *** *** ********* uses * ******/****** *****:

***** *** *** ********* simply ****** **** *****:

********** ** ***** ** is ****, **** *********** 30 ******* ** ~** on *** ************ *****.

*****

*****'* ***** ***** ***** quantization ** *-******, **** I-frames ******* ** **** by * ******** ****** ("I/P-frame ***** **" *****). So ** *-****** *** set ** ** *** I-frames *** ** -*, I-frames **** *** * minimum ** ** ************. This ***** ** ******** to ******* ************ ** a ******** *****, ********* some ***** *** ***** in * ***** ***** to ******.

callouts

*********

*********'* *********** ******** *** under *** *****/***** ***, on * ***** ** "lowest" (**** ***********) ** "highest" (***** ***********), ********** to "******." ***** ******** are ****** ** ******** quantization ******, ******* **** ~20-35. ***** ******** *** corresponding ************ ****** *** the **** ***** **** H.264 *** *.***.

Important: ***/***/*** ******

**** ************ *********** *** variable *** **** ********* (VBR), ***** ****** ********* in ***** ** ******** a ***-*** ******* *****, sometimes **** * ******* bit **** *** (****** MBR). *** ****** *** above ****** *** ************ level *** ****** ** targeting, *.*., ** **** camera **** ****** ************ level **, **** ******* increasing *** ********** ** necessary.

*******, ** ******* *** set ** ******** *** rate, quality ***** ** *** configurable ******* *** *** rate, ** ********** ** 'constant', **** ******* ***** automatically ******** ** **** bandwidth *** ****. *** instance, ** *** **** a *** ***** ****** set ** ***/* ******* at * ***** ****, the ****** *** *** a '****' ******* ***** since ** ** **** to ********. *******, ** the ****** *** ****** off *** * **** is ***** ** ***** of *** ******, ** *** need ** **** **** to '***' ******* ** maintain *** **** ***/* constant *** **** ** compression ** **** *********.

*** **** ** *** key ****** ** ***** streaming *****, *** ****** ** *** ** MBR - ************ ********* ********.

Smart ***** ******

***** ************ ******** *** ************ level ****** ********* ***** of *** ***** / frame / *****. ************, a ****** ************ ***** was **** *** ** entire *****. **** ***** codecs, *** ****** ************* between *** **********, ********* it * ****** ************ (thereby ********* **** *********) vs ******* **** * lower ************ *****. ** an *******,  * ****** or ******* ****** ******* a ******* *** **** be higher *******, ***** ****** cars *** ***** ** the ********** *** ***** quality. *** *** ** lowering ******* ********* ***** maintaining ******* *** ********* objects.

*******, ** ******** ********* readers **** ***** ****** in *** ***** ***** the ****** **** ** installed, ** **** ******** image ******* ******* *** be ****. *** *******, in *** ** *** tests, ****** ****** ** smart ***** ******** ****** blurring/smearing/artifacts ** *** *****, visible ** *** ******* and ********** *****. ******** ****** be ********* ******** ** avoid ***** ******.

******* ****** **** *** our ***** ***** ***** *** **** *********** ** these *** ***** **************.

What ****** *** ***?

**********, *** **** ********* question **: **** ******* setting is ********* ** *** camera's application?

*************, ** ** ********** to **** * ********* answer **:

  • *** ***** ***** ** a ********** ******** ****. Changing **** * ************ level ** ** ** 29 ** **** ** to ** ******** ** magical **********. ***** *** changes *** ****** ************* and *********.
  • *** ***** ***** ******* on *** ********** ** the *****. **** ******* scenes (**** ** ************) will ********* ******* **** a ****** ******* ****** than * ****** ***** (like * *********). *** smaller *** ******** ***** observed (**** * ****** across ** ************), *** more ****** ******* ****** can ******* ********** *******.

*******, ***** ***** *****, ** ***** *** key ***************:

  • ************ ~** ** *** "sweet ****":***** ** ***** ** ongoing *******, ** **** found ** ** ***** the **** ********* ******* bandwidth *** ***** *******. Many ************* ******* ** 28-30, ****** ***** ****** see *** ** ****** ************ *********** Comparison *** **** ******* ** *** to *********** ******.
  • *** ***** ****** (*** carefully):******* ** ***** ******* bitrate ********** ** **** scenes, ** ********* ***** codecs ** **** ******** possible, ** ***** *** be **** ** ******** image ******* ***** *********, while ******** ****** ***** than ******* ******. 

[[****: **** **** *** originally ******* ** **** but ************* ******* ** 2015, ****, *** **** to ******* ******* ***** options, ***** ***** *****, and ** ** **** recommendations]]

Comments (3)

*** **** **** **** from *********** ** **** precise ****** **** ***** and ******. **** ****** more ******* ********** *****. There *** **** **** degrees ***** *** ******* of ****** *** *********. 

 

*** **** ********* ******...

* ***** *********** ***-**** is ********* ******* * think ******* *** **** bit **** **** *** camera ** *** ** is **** *********. * say **** ******* **** something ******* *** **** need ** ****** *** incident **** **** ****** it **** ***** ** the **** ***. **** need **** ******* ******* to ****. *** **** not ***** ***** ** capacity ** **** ****.

Login to read this IPVM report.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

Related Reports

Video Surveillance Cameras 101 on Feb 25, 2020
Cameras come in many shapes, sizes and specifications. This 101 examines the basics of cameras and features used in 2020. In this report, we...
Glossary / Acronyms for Video Surveillance on Feb 10, 2020
This directory provides definitions and explanations for over 70 common video surveillance industry terms, including links to related IPVM...
Bandwidth Fundamentals For Video Surveillance on Jan 13, 2020
Bandwidth is the most fundamental element of computer networking for video surveillance systems. Because video surveillance can consume an immense...
IPVM Opens 12,000 Sqft Testing Facility on Dec 16, 2019
IPVM is proud to announce the opening of the world's first video surveillance testing facility that will allow us to significantly expand our...
Wide Dynamic Range (WDR) Guide on Oct 01, 2019
Understanding wide dynamic range (WDR) is critical to capturing high quality images in demanding conditions. However, with no real standards, any...
False Verkada 'Unrivaled' Low Light Performance Claim Removed on Jun 12, 2019
Verkada falsely claimed that it delivered 'UNRIVALED LOW LIGHT PERFORMANCE' until IPVM questioned. In fact, Verkada's low light performance is...
Smart CODEC Usage Statistics 2019 on Jun 03, 2019
Smart codecs are now nearly a standard feature in IP cameras, but our statistics show integrator adoption has not increased at the same rate. In...
Verkada Video Quality Problems Tested on May 23, 2019
Verkada suffers from numerous video quality problems, not found in commercial IP cameras, new IPVM testing of Verkada vs Axis and Hikvision...
Average Frame Rate Video Surveillance 2019 on May 23, 2019
What is the average frame rated used in video surveillance systems? In IPVM's 2011 statistics, the average was 6-8fps increasing to ~10fps in...
H.265 Usage Statistics on Apr 19, 2019
H.265 has been available in IP cameras for more than 5 years and, in the past few years, the number of manufacturers supporting this codec has...

Most Recent Industry Reports

USA's Feevr Thermal Temperature System Examined on Mar 31, 2020
This US company has burst on to the scene, brashly naming itself 'feevr' and branding itself as a "COVID 19 - AI BASED NON CONTACT THERMAL...
JCI Coronavirus Cuts on Mar 31, 2020
JCI has made coronavirus cuts, the company told employees in an email that IPVM has reviewed. Inside this note, we examine the cuts made, the...
Add Door Operators To Fight Coronavirus on Mar 31, 2020
IPVM recommends that integrators advocate and end-users consider adding door operators to fight the spread of coronavirus. This delivers...
Video Surveillance Business 101 on Mar 30, 2020
This report explains the fundamental elements of the video surveillance business for those new to the industry. This is part of our Video...
FDA Gives Guidance on 'Coronavirus' Thermal Fever Detection Systems on Mar 30, 2020
The US FDA has given IPVM guidance on the use of thermal fever detection systems being marketed for coronavirus, as an explosion of such devices...
Worsen: Integrators Hit Even Harder By Coronavirus on Mar 30, 2020
Integrator's problems have worsened over the past 2 weeks, according to new IPVM survey results. Inside this report, we share statistics and...
Pivot3 Mass Layoffs on Mar 27, 2020
Pivot3 has conducted mass layoffs, the culmination of grand hopes, a quarter of a billion dollars in VC funding, and multiple failures to gain...
Athena CEO Criticizes 'Deplorable' 'Nitpicking', IPVM Refutes on Mar 27, 2020
UPDATE: NBC News Report Cites IPVM On Coronavirus 'Fever Detection' Cameras Athena Security's CEO Lisa Falzone has strongly objected to IPVM's...
Hikvision Admits Sanctions Harming Its Financial Performance on Mar 27, 2020
While Hikvision initially downplayed being sanctioned for human rights abuses, the company is now admitting a significant impact in a new PRC...