Smart CODEC Usage Statistics 2019

By IPVM Team, Published Jun 03, 2019, 11:21am EDT (Info+)

Smart codecs are now nearly a standard feature in IP cameras, but our statistics show integrator adoption has not increased at the same rate.

free image

In this note, we examine adoption rates 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 2017 Statistics.

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

* ***** ******** ** *** ******* deployed ** *********** *** ***** ***** codecs.

Piechart 2019

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

*** ********* ***** ***** **** * clear ******** ** *********** *** ***** codecs **% ** **** ** *** time.

2019

H.265/Smart ***** ********* *** ************* ********

**** **** *** ** *** *********, about ** ************* *** ******** ** conflated ******** *.*** **** ***** ******, almost ** **** ** **** **** never *** ***** ******. ** **** excluded ***** ********* **** **********, ****** numbers ***** ** *** *********.

******.******* ******* **** ******* ******* ** our *****, ** ** ********* **** smaller **** ******* ******** ***** ***** codecs. *** ****.*** / **** ***** *********** ********* *******.

Similar ******* ** ****

********** **** *** ******* *********** ***** 2017, **** **** ***** *** ******/***** use ***** ****** *** ***** *** always/almost ****** *** **** **** ******** by * *** ********** ******.

**** ** *** ***** *********** (**-**%, 30-39%) **** ******* ******** ********, ***** 50-59% *** ******* **.

smart-codec-comp-2017-2019

Bandwidth/Storage *******

** ** ****, *** **** ****** answer *** ***** ***** ****** *** bandwidth *** ******* *******:

  • "***% ** *** ******* *** ****** H.264+ *.***+ *** *********. ***? ** use ***** ****** ** **** **** the ******* ****** ** ***** ******* and *****. **** ** **** * great ****** ******* **** ***** ** use *** *** ******** ******* *** using *.***+."
  • "***% ***** ******* *** ********* *****. Current ********** (*** ******** **** ******) so ***’* **** ********* ********* ** tech ****’* *** *******."
  • "**%. ******* ** ********* *** *******. There *** **** *********** *** ** have ********* **** ****** **** ******* to ******* ******* ** ******, ***. But *******, *** **** ************* **** simple ****** ********, **** ** ** easy *** ** **** ** ******* and ***** *** ****** ** ************* that ** **** ** *** ********."
  • "***% **** ** * ***** *** to ******** ******* ******* *** ********** cost ******* **** *** ******."
  • "**% ******* ** *** **** *** milestone ****** *********** *** *** *** take ********* ** **"
  • "* **** **** *******, ****** ******* 90%. *** **** ** *** ****** storage *** ********* ************ **'** **** advantage."
  • "**% ** *** *** *** ****** support ** *** ****** *** *** network ********* *** *******."
  • "***% *** ******* ********* *** *******."
  • "***%, ****** ***********, ****** *********."

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

******, *********** ********* ***** ***** ****** because **** *** *** ******** ** cameras **** ****. ** ****, ** is **** ****** * ************ **** offer ***** ****** **** ***, **** many ******** *** ******* ****** ****** their ****** ****, ********* *** ****, high ***, *****, ***, ***** ******, fisheye, ***.

  • "***% *** *** *** ** ** seeking **. **’* **** * ** facto ******** ***** ****."
  • "***%. ** ************* *** **** ******* and ***** ***** *** ***** **."
  • "***% * **** ** **** **** with '******' *************. ** ********* ********** the **** *** *******, ** * stick **** ********* ************* *** **** all *** ***** ****** ** **** degree."
  • "**%. *** ******* ************ ** *** have ****."
  • "**+% ** *** ****** ************* *** Axis *** ********* ** **** ** help ****** *** ******** ******* ************ for *** ************ ********."
  • "* ***** *** **% ** *** cameras ** ******* *** ***** ******. Most ** *** ******* ** ******* have ***** ****** ***** **. *** bad **** ** **** *** *********** don’t ****** ****** ** **** ** the ***** ******."
  • "**%+ ******* *** ****** ** *** most **** **** *********."
  • "* ******* ****** ***. ******** ** camera ****** ** ******** **** ***** included."

Less ********* ** ****** ********

******** ***** ************ ********* ****** ******* concerns ** *** ** ***** ******* for ***** ***** ******:

  • "** **** **** ****/********* ******* ** appears ** **** *** ** ********** confidence **** ** ******* ***'* ***** their ******* ***** ***** * **** for **."
  • "******** *** ******* ********* ***** ** concerns ** ******* ** ********"
  • "**% ** *** ******* *** ***** codecs. *** ****** ***** **** ******* through ******* ********. ** ****** ** always **** *** *** ******* ********* at **** ****, ******* **** ** not ****** * ***********."
  • "**** **** ***% ** *** ******* installed *** ***** ******. ** **** stuck ******** ** *** **** * series ******* *** ******* * ******* so *** **** ****. *** ******* reason *** **** ** **** *** work *** **** ********* **** * small ****** ** ********** ******* **** have **** ** *** *********/****** ******* reduction ** ** **** ** *** production ******* **** ** *** ****."
  • "**% ** ********* ******* ** *** the ***** ***** *.*** *** ******** wise ****** ** *** ****** ******* cameras. ***** ** *** ********* *** less ********** ** ******* *******"

Compatibility ******

*** **** ****** ******** **** *********** who **** **** ****** ** ***** use ***** ****** *** **** ** support, ****** ** *** ****** ** VMS ****.

  • "****, ***** **** *** *** **** our ********* *** ***** ** *** support ***** ******"
  • "*% - ** *** *.*** *** everything - ************* ****** *** ****."
  • "codecs, *** ******** (**** ** ****) so ** ********* ******."
  • "*** ******* **** ** ******* **** with *.***+. *** **** ** * benefit ** ** ****** ***** **** our *** **** *** ******* ** (Luxriot)."
  • "**** ** *** **** *** ****** installations ** *** *** **** **** not ******* **** ******* ** *** system **** **** *** ******* **** vendor's *************** (******** **** *** ******* Zipstream, ********* **** *** ******* ******** Smart *****)."
  • "*% ** *** ************* ** *** primary ******* **** ** ***** ******* which ** *** ******* ****. ** are ****** ** ******* ** **** and ***** ***** **** ******."
  • "**%. **** ** *** *******."

**** **** ** ******* ** ***********, as *** **** ******** ** ******* produced ** **** ******* ***** ******, and *** ************* *** **** ***** in *** *******. ****** **** ** jerky ******** ** **** ******* ******** are ***** ********, ****** ********.

Storage ********

******* *********** **** **** **** *** not *** ***** ****** ******* ******* was "*****" ** *** **** ** a *******. **** *** ******** ***** in ********** ***** **** ***** ************ *********, ** ****.

  • "****** ****. ** **** ****** **** H.264. ** ***'* **** ****** ***** we *** ******* *** ******* **** that *** ***** *** **** ***** them. ******* ** ********** *****."
  • "***** ****** ******* *********** ******** ****** we ********* **** **** *** ** storage ** *** **** * ******* and **** **** ** ****** ******* smooth *********** ** *** ********** ********."
  • "*% *)******* ** (**********) *********** *** smaller *************. *)****** ************ ********* ***** have ******** ***** *** *** ********* to ***** ******."
  • "* *** ****. ** ***'* *** them. ******* ** **** *****."

******, ****** ** ******* **** **** steadily ******** ** ****** *****. *** example, *** ****** *** ******* ~$***-*** *****, ***** ** **** it **** ~$***, * **-**% ****.

Future ***** ** *********

*******, * *** *********** ********* **** they *** *** ***** ***** ****** today, *** **** ***** ** ** so ** *** ******, **** **** selling ***** ***** ******* ******* ******* (but *** ***** *** *******) *** others ******* ** ***** ***** ******* them.

  • "****, *** ** *** ***** *** it *** "******-********" *** ********* *****. It's *********, *** ***** ** ***** a ******** ** *** **** *** there **** ***'* ** **. * expect **** ****** ** **** ************* by **** **** **** ****."
  • "**** ***** *** **** **** ** changing. ********* *** ********** **** ******* to ** ***** ** ******** ******* and **** **** ***** **** ******* bogging **** *** ******."
  • "** **** *** **** ***** ****** yet. ** *** * ******* ********** but *** ******* ** ********* ***'* and **** *** ****** ** *** future"

Comments (15)

Undisclosed Manufacturer #1

06/03/19 05:18pm

One thing that comes up with smart codecs is image quality variances with codec on compared to codec off.

Has IPVM done a shootout of identical cameras, with identical scenes and compared the live and playback video quality with smart codec active and inactive?

Seems to me, bandwidth is generally not an issue these days and any degradation of video quality (typically background) is quickly recognized, particularly in live monitoring environments. 

While background scene degradation doesn't really matter that much practically, it is still observable, noticed and perceived as a deficiency by users. 

Additionally, I'm sure that all smart codecs are not created equal, so there may be variances from codec to codec. 

Very interested to hear what you think!

Agree: 2
Disagree
Informative
Unhelpful
Funny: 1

John Honovich

IPVM | In reply to Undisclosed Manufacturer #1 | 06/03/19 05:21pm

any degradation of video quality (typically background) is quickly recognized, particularly in live monitoring environments.

Oh, I see you, you are not familiar with Verkada...

In all seriousness, there are clearly a significant number of buyers who do not notice video degradation.

And we have tested video quality with smart codecs on and off, I'll let Ethan respond.

Agree
Disagree
Informative
Unhelpful
Funny: 1

Undisclosed Manufacturer #1

In reply to John Honovich | 06/03/19 05:42pm

Ha, that's foreground degradation! And without a smart codec, correct?

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Ethan Ace

IPVM | In reply to Undisclosed Manufacturer #1 | 06/03/19 05:45pm

Has IPVM done a shootout of identical cameras, with identical scenes and compared the live and playback video quality with smart codec active and inactive?

Yes, we've tested multiple smart codecs at multiple levels. There are definitely variances from manufacturer to manufacturer, and generally those with the ability to control level of the smart codec perform better, as they can be fine tuned.

For example, Hanwha WiseStream tends to degrade the background drastically at High and above (our test):

Zipstream shows some degradation in the background using High, but not much. When you switch to "Extreme" it is quite pronounced, though (our test).

Hikvision's H.264+/H.265+ don't offer any strength controls, so there's no real option to adjust how compressed the background is, but we saw issues of smearing fine details with it on, for sure (our test). Same with Dahua Smart H.264+.

 

Agree: 1
Disagree
Informative
Unhelpful
Funny

Undisclosed Manufacturer #1

In reply to Ethan Ace | 06/03/19 06:02pm

Awesome, Thanks. Not sure how I missed that one. 

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed Manufacturer #3

In reply to Ethan Ace | 06/03/19 07:02pm

Ethan,

What about video comparisons? smart codec will smear details in a static image because that's what it's supposed to do. What about quality differences when there is motion, like how effective do the various codecs work to not compress motion? Is their compression bleeding to the object that is moving, etc.

Agree: 1
Disagree
Informative
Unhelpful
Funny
Avatar

Ethan Ace

IPVM | In reply to Undisclosed Manufacturer #3 | 06/03/19 10:30pm

In my experience, I've never seen compression bleed into moving objects. It seems that codecs tend to err more on the side of caution. Keep in mind that this is not "motion" as in valid motion like is used for VMD, but pixel change. So cameras tend toward simply compressing what does not change. Some seem to be a little bit smarter and will keep text less compressed even if it's in the background, but I haven't seen even the cheapest smart codec camera compress a valid moving object.

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed #2

IPVMU Certified | In reply to Ethan Ace | 06/03/19 10:13pm

did the sun peek out from behind the clouds right before the “H.264+ On” test?

or do you believe that brightening is also an artifact of the SC?

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Ethan Ace

IPVM | In reply to Undisclosed #2 | 06/03/19 10:32pm

That test was a couple years ago at this point, but I believe the light level was fairly stable the entire time. I'd have to go back to the video at this point to confirm.

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed #2

IPVMU Certified | In reply to Undisclosed Manufacturer #1 | 06/03/19 06:01pm

Seems to me, bandwidth is generally not an issue these days...

even on the WAN, or mobile?

also, bandwidth savings is only part of the equation, the other part is retention/storage.

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed Manufacturer #1

In reply to Undisclosed #2 | 06/03/19 06:33pm

Agreed on storage point. I was thinking strictly of camera to server bandwidth. I stand corrected on oversight of your point. 

One thing I'm not certain of and could use clarity; does smart codec come into play with WAN connections with Axis or Hanwa or other smart codecs? Does smart codec apply to secondary stream to gateway or other outlet to WAN as implied?

I am familiar with Avigilon's HDSM which is not a camera codec but rather a server to client/WAN transmission efficiency and has something to do with my oversight on that point. 

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed Integrator #4

In reply to Undisclosed Manufacturer #1 | 06/03/19 09:27pm

I am familiar with Avigilon's HDSM which is not a camera codec but rather a server to client/WAN transmission efficiency and has something to do with my oversight on that point.

Avigilon does have smart codecs on all of the H4 series of cameras at this point in time.  As far as I am aware all currently available cameras now that the H3 multi-imagers have been discontinued support smart codecs, even the H4Pro series.

One thing I'm not certain of and could use clarity; does smart codec come into play with WAN connections with Axis or Hanwa or other smart codecs?

Yes, it applies to the stream itself from the camera.  The same is true for Avigilon.

Does smart codec apply to secondary stream to gateway or other outlet to WAN as implied?

I'm not certain that smart codec applies to the secondary stream.  I would assume so but cannot answer definitively.  I may also be misunderstanding the second part of your question.  The stream itself is what is modified by smart codecs so the gateway is irrelevant.  If your definition of gateway in this instance is some form of mobile client server/transcoder the answer is highly dependent upon the VMS/NVR/transcoding device.

Agree: 1
Disagree
Informative
Unhelpful
Funny

Undisclosed Manufacturer #5

In reply to Undisclosed Integrator #4 | 06/04/19 11:31am

You can choose to enable it for the secondary or other streams, as needed in most cameras. 

This can provide additional bandwidth and storage savings, but the secondary stream is usually lower resolution so the savings are not as significant. 

Agree
Disagree
Informative: 1
Unhelpful
Funny

Undisclosed Manufacturer #1

In reply to Undisclosed Integrator #4 | 06/04/19 01:03pm

Bottom line, there are different architectures depending on the VMS and their respective utilization of smart codec can be different. 

I know Avigilon cameras have smart codec but it is strictly used for camera to server connection. ACC client and mobile pulls video from the server, not from the camera so smart codec means nothing for client connections. That's where HDSM kicks in.

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Dennis Eaton

IPVMU Certified | 07/02/19 02:11pm

Can anyone confirm that Avigilon does not support ZipStream?  I'm getting ready to put a large project out to bid and was considering ACC7 and Axis cameras.   

Agree
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