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

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...
Last Chance - Camera Course Winter 2020 on Jan 30, 2020
This is the only independent surveillance camera course, based on in-depth product and technology testing. Lots of manufacturer training exists...
Testing Bandwidth vs. Frame Rate on Jan 23, 2019
Selecting frame rate has a major impact on surveillance bandwidth and storage consumption. But with smart codecs now common and cameras more...
Bandwidth vs Low Light Shootout - Avigilon, Axis, Bosch, Dahua, Geovision, Hanwha, Hikvision, Uniview, Vivotek on Feb 08, 2019
Nighttime bandwidth spikes are a major concern in video surveillance, but do all manufacturers' cameras perform the same? Are some more consistent...
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...
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...
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...
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...
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...
Axis Live Privacy Shield Analytics Tested on Jun 25, 2019
Privacy is becoming a bigger factor in video surveillance, driven both by increased public awareness and by GDPR. Now, Axis has released Live...

Most Recent Industry Reports

Every VMS Will Become a VSaaS on Feb 21, 2020
VMS is ending. Soon every VMS will be a VSaaS. Competitive dynamics will be redrawn. What does this mean? VMS Historically...
Video Surveillance 101 Course - Last Chance on Feb 20, 2020
This is the last chance to join IPVM's first Video Surveillance 101 course, designed to help those new to the industry to quickly understand the...
Vulnerability Directory For Access Credentials on Feb 20, 2020
Knowing which access credentials are insecure can be difficult to see, especially because most look and feel the same. Even insecure 125 kHz...
AI/Smart Camera Tutorial on Feb 20, 2020
Cameras with video analytics, sometimes called 'Smart' camera or 'AI' cameras, etc. are one of the most promising growth areas of video...
China Manufacturer Suffers Coronavirus Scare on Feb 20, 2020
Uniview suffered a significant health scare last week after one of its employees reported a fever and initially tested positive for coronavirus....
Cheap Camera Problems at Night on Feb 19, 2020
Cheap cameras generally have problems at night, despite the common perception that integrated IR makes cameras mostly the same, according to new...
Milestone Launches Multiple Cloud Solutions on Feb 18, 2020
Milestone is going to the cloud, becoming one of the last prominent VMSes to do so. Milestone is clearly late but how competitive do these new...
Video Surveillance Architecture 101 on Feb 18, 2020
Video surveillance can be designed and deployed in a number of ways. This 101 examines the most common options and architectures used in...
UK Stands Behind Hikvision But Controversy Continues on Feb 18, 2020
Hikvision is exhibiting at a UK government conference for law enforcement, provoking controversy from the press, politicians, and activists due to...
IronYun AI Analytics Tested on Feb 17, 2020
Taiwan startup IronYun has raised tens of millions for its "mission to be the leading Artificial Intelligence, big data video software as a service...