H.265 Problems - Does Any Camera Manufacture Consider Adopting AV1?

With H.265 there is still an ongoing issue of royalties and there is no native browser support for H.265 decoding which makes the move to the cloud problematic (consider you want to avoid transcoding).

AV1 seems to be progressing quickly and is royalty-free.

Login to read this IPVM discussion.
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.

** *** ** * can ****, ** ***** manufacturer *** **** *** leap **** *.*** ** AV1/VP8/9.

**** *** ****** ** do **** *****. ** you **** ***** ******* (most ********* **) *** need ** ******* *.***. ONVIF *****'* ******* ***/***/***.

*** *** **** *** leap **** **** **** retailer ** ***** ******'* product ** ********* ** our *** (******** **'** still ** ****** *****). We *** *** ** our ****-******* *******.

*** ******* * ******-**** user ********** ** **** browsers.

***** *****'* ******* ***/***/***.

*** ***** ******** ** future ********? **** ************* supported *.*** **** ****** ONVIF ******* **.

* *** ** **** chipsets *** *** ******** encoding *** *.*** **** VP8/9.

*** **** ** *** encoding ******* ** ***** surveillance ******* *** ******* to ** **** *****, it ** ******** *** way ****** - ***** would ** ** ***** support (**** ****** ******* a *** *******) ** there *** ** ******* with **** **********. **** is ******* **** *** happened **** *.*** *** ONVIF ******* * *******.

*** **** ***** ** the **** ** **************************** ** ****** (******) side, ***** ** ******** based ** *** **** of *************** *** ******** of ***** *******. ** long ** **** ******** formats *** *** ** common ****-**** **** ** video ******* (**** *********, etc.), ****** * ******** decoding ******* ** *** client-side ********** (*** ***, phones, *******, ***.) **** you ** ***** *** now.

** *** ****** **** the ********** ******* ********* services, **** *** ******** chips ****** ** *** TVs ********** ******* ***, then ***** ** ******* as **** *****, **** adoption **** ***** ************ will *****. * ** 10 ***** ** ** informed *****, *** ***, it **** ******.

*** ** ***** * relatively *** ******* *** represents * **** **** for *************. ***** ****** browsers ******* **, **** NVR's *** ***'* ** not (***). * ******* it **** ** **** difficult *** *** ** make **'* *** **** the ******** ******** ******** than ** *** *** H.265. ******* ** *** name *** **********, *.*** support *** **** ** a ******** ********** ***** H.264, *** ** ***** took ******* ** *** broad *******.

** ******** ************ ********* for *** ***? ***** hardware *********** ******** *** VMS ******* ******* *********, there's ******* ********** *** manufacturers ** ******* ******* with *** *******. *** royalty **** ****** ** it ** ****, *** manufacturers *** ***** ** pass ** *** ***** and *** ****** ** willing ** **** **, so * ***'* ***** that's ****** ********** ** it's ***.

** *** ******** ********* to **** ****** *****-***** or *****-******* ********, ** will ****** **** ********* to *** ***-******** ****** and ********* **** ******** browser ******* *** ******** server ********. * ****** if **** **** ********** be **** ****** *** industry ****** ****** **** AV1/VP9?

*** - ************** ***** ***** ******** acceleration ** ***

*******, ** *** *** see, **** ** ***** chips ** *** ******* an ******** *** **** (or ***?) ** ***** with ** ******** ******* are *** ** *** in ***** *******.

* ******* * *** replying ** *********** #*, but * ***** * wasn't. *** ***** * was ****** ** **** was **** ***** ****'* much ********* ***. * guess * ****'* **** that *****.

***** *** **** *** products **** ** - DW - **** **** can **-****** ****/**,* .

** *** ***** ****** side, ****** *** ***** be ******** **** ** an ***** ****** ** some ********.

* ***** **** ** see *** ********** ******* into ***** ** ******* as ** ******** ****** but *** ***** ** hold ** ******.

* ******** *** ***** grip ***'* *** ** ActiveX ******** **** ***** other ********** *** ***** on.

** ******* *** ******, the ********** *** ********* other ***** ***** ********* has ****** ** ** with ********, *** ********** to ** **** ********.

*********, *** ********* *** the *** ******** ***** processing / ******** ***** used ** *** ** Video *****. **** **** robust ******* *** *.*** and *.***, *** **** (likely) ***** ******* ******** other **** ***** *** codecs. *'** ********** ***** both ** **** **** exact ********. **** **** given * **********, "**."

*** ********* **** ********* support ******** ***** ** available. ****** **** **** extensions ** *********** ****** any ******* ***** ***** on *** ******. ******** a ********* ***** ** significantly ****** **** ** used ** **.

******** ** * ****** manufacturer, ** ***** ** very ***** ** **** the ********** ****** ** choose ****. *** ******* streams, ** **** ** times ******** ** ***** FFMPEG (* ******** *******/*******) to ****** ******* ****** mobile, *** ******* ***** playback.

*** ********* *** **** forced ** ** ********** sneaky *********** ** ***** to *********** ******* ******** on ****** *******. ******* and ***** **** **** different **********, *** ******* for ***** ******** *********** decoding *********.

***** *** *** ******** to ****** *** *** other ***** ***** **** JPEG, *.*** *** *.***, we're ***** **** **** we **** *** * very **** ****.

** ****** ******* ******** to *****. **... *** is *** *******-**********, * take **? **** ** _need_ ******** ******* *** encoding? ** ***** ****** in *** **** *** has (*******) *** *** (spec?) * ***'* ***** the ****** ******* *** a ******** ****** ** the **** *** ************ given ***** ****** ********** hardware *******.

*** ******** ***** ****** absolutely ******** ******** ******* for ******** *****+ ***** streams.