Smart CODEC Usage Statistics 2021

By Zach Segal, Published Jan 18, 2021, 08:48am EST

Smart codec usage has dropped moderately since 2019 despite nearly ubiquitous support for several years and, confusion around what constitutes a smart codec remains high.

IPVM Image

In this note, we examine the adoption rate of smart codecs and share integrators' feedback on why they do or do not use smart codecs in their deployments.

For technical background, see IPVM's Smart Codec Guide. This report is a successor to our 2019 usage and 2017 usage Statistics.

* ******** ** *** cameras ******** ***** *** smart ******, *** ***** has **** * * percentage ***** **** ***** 2019 (**% **. **%).

***** ***** ***** ****** cited *********/******* ******* **** commonly, ****** **** **** said **** **** **** simply ******* ******* *** include *** ******* ** did *** ******* * reason.

*** ********* ***** ***** that *********** *** *****, with **% ***** **** less **** **% ** the ****, **% ***** them **** **** **% of *** ****, *** the ********* **% ***** in *** ******.

IPVM Image

H.265/Manufacturer ****/***** ***** *********

******* *********** ************* *** question ** **** * smart ***** **, ******** we ******** **** ********* than ** ****. ** have ******** ***** ********* from **********, ****** *** numbers ***** ** ~*** remaining *********.

A **** **** ****, ****

***** *** ******* ***** 2019 *** ****, **** more *********** ***** ***** codecs **% ** **** of *** **** *** fewer *********** ***** ***** codecs **% ** **** of *** ****.

*** ******* ******* ******* using ***** ****** **** image *******, ********** ***** smart ****** **** ***** hardware, * **** ** need, *** **** ** using * *********** *****; and ** ******* * particularly ***** ******** ** comments ********** *********** ******.

Bandwidth/Storage *******

** ** **** *** 2017, *** **** ****** answer *** ***** ***** codecs *** ********* *** storage *******:

  • “********** ** **** ******** has **** **** ** Hanwha *** **** **** their ******** ******* ** all ** ****. ** only *** **** ** a *** ***** ** save **** ********* ******* seeing ******** *****.”
  • “***. ** **** **** Axis *** ****** **** year. *** ********* ******* is *** **** ****** for ***”
  • “[***%] *** *** **** width *********”
  • “***% ** *** ****** deployments **** ********* ** these ****** ** ****** storage ************, ****** * concern **** *** ******* IT ***********”
  • “***, ***** *******”
  • “**% **** ****. **** all ** *** *** Axis ******* **** *** stream ****** **. **** is * **** ******* on *******. *** ******* one **** ** ******** all ***** ******* **** all **** ******* *** our ******* **** **** 15gb/camera/day ** ***/******/***”
  • “***% - *** ** use ** ****. ***** to **** **** ** left *** ********** ** 10/LOW. *******, ** *** now ********* *** ********* (cloud) ****** ** ****** Zip **/******* ** **/**** and **** **** **** to ****** *** ********** while *** ********** ******* (using ******** *** ** well)”
  • “******** **%. ** **** using **** ******* *** still ******* **** **********”
  • “**% ** **** ** storage ******”
  • “**%, ***** ********'* ****. It ***** ****** **** for ******** *** ********* and ********** ***** ** client ********”
  • “**% - ****** *** very ******** *************, ***** codecs ***** * ********** improvement ** ********* *** retention. ***** ****** ***'* a ****** *** ** implement ****”
  • “***% ** ******* *** Hanwah *** ****. ** have ***** **** *** savings ** ********* *** storage ** ** ******* then *** ***** **** of ***** *******”
  • “* *** *.***+ *** 100% ** *** ********* cameras * *******. ******* and ********* ******* *** unreal”
  • “**% - *** ******* network ********* ** * nice ******* ** ********. Not *** ******* **** the ***** *********** ******* that ** ****. *** as ** **** ******* Zipstream ** ****”

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

** ** ******** *****, many ********* ********** ************.

  • “***% ****** **** ******** on *** ******”
  • “**%+. **** ******* ******* some **** ** ***** codec *****, *** ***** such ****** ***** ** storage *****”
  • “**% ******* ******** ** use ***** *****. ****** every *** *** **** version *** ** **** advantage ** **”
  • “**% **** ********* *.***+, manufacturer **********”
  • “**% ** **** ***** on *** *******”

Compatibility ******

*** ** *** **** common ********* **** *********** who **** **** ****** or ***** *** ***** codecs *** **** ** support, ****** ** *** camera ** *** ****.

  • “**% ******** ** ********* or *********** ******* ******* and ****”
  • “**%. **** *** **** we ***** ******** *** camera ************”
  • “**% **** **** **** in * ****** *** to *** ***********, *** can ****** **** ******* than ****'** ***** ** a ***** ***********. ****, have **** ******* ******** in ****** ******* ** camera ***** (*** ****** with *** ****** *** constant ****** **** **** detail.)”
  • “**% - **** ***** it ***** *****. **** incompatablities ********* ** **** using ** ****”
  • “**%. ********* *** **********”
  • “**% - **** ** the % ** ******** where ** *** ***** the **** ****** *** recorder ************”

Performance ********

***** *** * ***** increase **** ******** ***** in ******** ********** *********** concerns.

  • “***** **%. ** ****** employ ********* *** **** we ** ** ** at *** ****** ********. During ******* * **** found **** ****** *** often ****** *** ** didn't **** ** **** as * ******* ** should.”
  • “**** **** ********* ** required ** ********. **** experienced ******.”
  • “* **** **** *.***+ on ***** ** ******* of ** ******* **** year. ****** *********** **** and ****** ***** *******. I **** *** * few ****** **** *** quality ** ******** ***** using ***** ******.”
  • “**%, * **** *** them *** ******* ******* where ***** ** ******** motion, ********* * **** found **** **** ****** to ****** ******* *** lose **** ******* ** the ********* ** *** motion *****.”
  • “* ******* **** ***** it ******* *** ******* of *** *******. ** I ****** **** ********* time * ***** ******** enable **** *** **** hard ****** ****/**** **'* not ****** * ******.”
  • “*%. ** ******* ******* quality ****** **** *****”
  • “*%. * **** **** H265+ ** *** **** but ***** ***** ********* and *** ******* ** image *******. **** **** alone ** ** *******.”
  • “****. * ****'* ****** and * ****'* **** it ** * ***'* know **** *** *** consequences”
  • “* ******* **** ***** it ******* *** ******* of *** *******. ** I ****** **** ********* time * ***** ******** enable **** *** **** hard ****** ****/**** **'* not ****** * ******.”

Proprietary ******

******* *********** **** ********* with *** *********** ****** of ***** ******.

  • “*% ******* **** ******** standards ** ***** ********”
  • “*% ******* ** *** proprietary ****** ** ***** codecs”
  • “*%. ** *** ** use *** ********* ******* unless **** ** * vital ******”

Comments (1)

** *** ** *** proprietary ******* ** ***** smart ******, **** ***** (as *** ******* ******* out ** *** *********) seems ** ** * major **************** ** **** is ***** ** ***** codec. ******* ** ** I'm *****, *** ***'* what ** ***** ** smart ***** ** ******** compression ** *** ***** to ******** *************? *** example, ***** ***** ***** with ******* ***** ** are **** ********** ** the ***** ****** ***** areas ** **** **** scene? ** **'* *** done ** *** ******, while *** ****** ** your ******** **** ** H265 ***** **** ******* proprietary ******** ** *** stream?

** ***** ***'* ******** about *** ***** ****** itself **** ** ***********, correct? ***** **** ** the ******* ** *********? It's *** ****** * "smart *****" *** ***, but *************?

****** ** ****** ** called "***** ********" ****** than "***** *****"?

Agree: 5
Disagree
Informative
Unhelpful
Funny
Read this IPVM report for free.

This article is part of IPVM's 6,956 reports, 927 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.

Already a member? Login here | Join now
Loading Related Reports