Smart CODEC Usage Statistics 2021

By Zach Segal, Published Jan 18, 2021, 08:48am EST (Info+)

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.

* ******** ** *** ******* ******** still *** ***** ******, *** ***** has **** * * ********** ***** drop ***** **** (**% **. **%).

***** ***** ***** ****** ***** *********/******* savings **** ********, ****** **** **** said **** **** **** ****** ******* cameras *** ******* *** ******* ** did *** ******* * ******.

*** ********* ***** ***** **** *********** are *****, **** **% ***** **** less **** **% ** *** ****, 30% ***** **** **** **** **% of *** ****, *** *** ********* 45% ***** ** *** ******.

IPVM Image

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

******* *********** ************* *** ******** ** what * ***** ***** **, ******** we ******** **** ********* **** ** 2019. ** **** ******** ***** ********* from **********, ****** *** ******* ***** on ~*** ********* *********.

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

***** *** ******* ***** **** *** 2017, **** **** *********** ***** ***** codecs **% ** **** ** *** time *** ***** *********** ***** ***** codecs **% ** **** ** *** time.

*** ******* ******* ******* ***** ***** codecs **** ***** *******, ********** ***** smart ****** **** ***** ********, * lack ** ****, *** **** ** using * *********** *****; *** ** noticed * ************ ***** ******** ** comments ********** *********** ******.

Bandwidth/Storage *******

** ** **** *** ****, *** most ****** ****** *** ***** ***** codecs *** ********* *** ******* *******:

  • “********** ** **** ******** *** **** Axis ** ****** *** **** **** their ******** ******* ** *** ** them. ** **** *** **** ** a *** ***** ** **** **** bandwidth ******* ****** ******** *****.”
  • “***. ** **** **** **** *** Hanwha **** ****. *** ********* ******* is *** **** ****** *** ***”
  • “[***%] *** *** **** ***** *********”
  • “***% ** *** ****** *********** **** advantage ** ***** ****** ** ****** storage ************, ****** * ******* **** our ******* ** ***********”
  • “***, ***** *******”
  • “**% **** ****. **** *** ** the *** **** ******* **** *** stream ****** **. **** ** * huge ******* ** *******. *** ******* one **** ** ******** *** ***** cameras **** *** **** ******* *** our ******* **** **** ****/******/*** ** 5gb/camera/day”
  • “***% - *** ** *** ** Axis. ***** ** **** **** ** left *** ********** ** **/***. *******, we *** *** ********* *** ********* (cloud) ****** ** ****** *** **/******* or **/**** *** **** **** **** to ****** *** ********** ***** *** increasing ******* (***** ******** *** ** well)”
  • “******** **%. ** **** ***** **** storage *** ***** ******* **** **********”
  • “**% ** **** ** ******* ******”
  • “**%, ***** ********'* ****. ** ***** really **** *** ******** *** ********* and ********** ***** ** ****** ********”
  • “**% - ****** *** **** ******** circumstances, ***** ****** ***** * ********** improvement ** ********* *** *********. ***** really ***'* * ****** *** ** implement ****”
  • “***% ** ******* *** ****** *** Axis. ** **** ***** **** *** savings ** ********* *** ******* ** be ******* **** *** ***** **** of ***** *******”
  • “* *** *.***+ *** ***% ** the ********* ******* * *******. ******* and ********* ******* *** ******”
  • “**% - *** ******* ******* ********* is * **** ******* ** ********. Not *** ******* **** *** ***** compression ******* **** ** ****. *** as ** **** ******* ********* ** nice”

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

** ** ******** *****, **** ********* widespread ************.

  • “***% ****** **** ******** ** *** models”
  • “**%+. **** ******* ******* **** **** of ***** ***** *****, *** ***** such ****** ***** ** ******* *****”
  • “**% ******* ******** ** *** ***** codec. ****** ***** *** *** **** version *** ** **** ********* ** it”
  • “**% **** ********* *.***+, ************ **********”
  • “**% ** **** ***** ** *** cameras”

Compatibility ******

*** ** *** **** ****** ********* from *********** *** **** **** ****** or ***** *** ***** ****** *** lack ** *******, ****** ** *** camera ** *** ****.

  • “**% ******** ** ********* ** *********** between ******* *** ****”
  • “**%. **** *** **** ** ***** recorder *** ****** ************”
  • “**% **** **** **** ** * single *** ** *** ***********, *** can ****** **** ******* **** ****'** worth ** * ***** ***********. ****, have **** ******* ******** ** ****** extreme ** ****** ***** (*** ****** with *** ****** *** ******** ****** with **** ******.)”
  • “**% - **** ***** ** ***** sense. **** **************** ********* ** **** using ** ****”
  • “**%. ********* *** **********”
  • “**% - **** ** *** % of ******** ***** ** *** ***** the **** ****** *** ******** ************”

Performance ********

***** *** * ***** ******** **** previous ***** ** ******** ********** *********** concerns.

  • “***** **%. ** ****** ****** ********* and **** ** ** ** ** at *** ****** ********. ****** ******* I **** ***** **** ****** *** often ****** *** ** ****'* **** as **** ** * ******* ** should.”
  • “**** **** ********* ** ******** ** customer. **** *********** ******.”
  • “* **** **** *.***+ ** ***** 50 ******* ** ** ******* **** year. ****** *********** **** *** ****** video *******. * **** *** * few ****** **** *** ******* ** playback ***** ***** ***** ******.”
  • “**%, * **** *** **** *** certain ******* ***** ***** ** ******** motion, ********* * **** ***** **** they ****** ** ****** ******* *** lose **** ******* ** *** ********* of *** ****** *****.”
  • “* ******* **** ***** ** ******* the ******* ** *** *******. ** I ****** **** ********* **** * would ******** ****** **** *** **** hard ****** ****/**** **'* *** ****** a ******.”
  • “*%. ** ******* ******* ******* ****** busy *****”
  • “*%. * **** **** ****+ ** the **** *** ***** ***** ********* and *** ******* ** ***** *******. Best **** ***** ** ** *******.”
  • “****. * ****'* ****** *** * didn't **** ** ** * ***'* know **** *** *** ************”
  • “* ******* **** ***** ** ******* the ******* ** *** *******. ** I ****** **** ********* **** * would ******** ****** **** *** **** hard ****** ****/**** **'* *** ****** a ******.”

Proprietary ******

******* *********** **** ********* **** *** proprietary ****** ** ***** ******.

  • “*% ******* **** ******** ********* ** avoid ********”
  • “*% ******* ** *** *********** ****** of ***** ******”
  • “*%. ** *** ** *** *** propriety ******* ****** **** ** * vital ******”

Comments (1)

As far as the proprietary concern of using smart codecs, this again (as the article pointed out in the beginning) seems to be a major misunderstanding of what is meant by smart codec. Correct me if I'm wrong, but isn't what is meant by smart codec is variable compression of the image to maximize effectiveness? For example, plain white walls with nothing going on are more compressed in the scene versus other areas of that same scene? So it's all done in the camera, while the output is your standard H264 or H265 codec with nothing proprietary embedded in the stream?

So there isn't anything about the coded stream itself that is proprietary, correct? Could part of the problem be semantics? It's not really a "smart codec" per say, but smart encoding?

Should it really be called "smart encoding" rather than "smart codec"?

Agree: 5
Disagree
Informative
Unhelpful
Funny
Login to read this IPVM report.
Why do I need to log in?
IPVM conducts reporting, tutorials and software funded by subscriber's payments enabling us to offer the most independent, accurate and in-depth information.
Loading Related Reports