H.265 ****** ******* *********
******* * ******** *****'* H.265 ******* ** ********* the ***** * *******, which ******** * ******** framework *** ********** ****** other **** *.***, *****, and ****-*, *** **** codecs ******* ** *** earlier ***** ***** **** by ******* *. ******* must ******* * "*****-**-***" H.264 ** *.*** ******* under ******* *, **** VMSes **** ** ************* understand ***** ** ** use. *********, ***** *** support ***** *******' *.*** stream, *** ********** ****** H.265 *******.
***** ******* */***** *, H.265 *** ***** ****** are ********** ********* ***** *****, ********* ***** ******* surveillance ******* **** ** H.264, *.***, *** *****, as **** ** **** common ****** **** ** JPEG2000, ***, *** ****. This ***** **** ********* future ****** *** ** added ** ******* ** long ** **** *** standardized ** * ***** type.
Camera **** ****** *** *********
****** ********* ** * mandatory ******* ** ******* T, ******* **** ******* and ***** **** ****/******* motion ****** ***** * standard ******. **********, ** event ********* *** *******, while **** ** **** manufacturers, ******* *** ********. The ********* ***** **** ONVIF's ******* * ************* shows ** *** ***** mandatory:

** ******** ** *******/********* motion ******, ******* * also ******** ************* ** motion *****/******* **** *** VMS ("****** ****** ******** Configuration").
*** **** ** ***** motion ********* ** * mandatory ******* *** **** one ** *****' ******* complaints ***** ******* ***** profiles, ** **** ******** this ************* * *********** for ***** *********.
Analytics ********
******* * **** ******** support *** **** ******* video *********, ********* **** detailed ***** ****, ****** position, *** ******** ***** using ******** *********. *******, Avigilon ********* ******* * as ***** ***** ** integrating *********** *********** ***** ******* (*********** ***** ** ********* And *******).
**********, ********* **** ****** limited ** ******** ******, with ******** ***** *** more ******** **** ********* custom ***********. *******, ****** video ****** *********, ********* integration ** ********, *** required. ****** ************* *** choose *** ** ********* the ********* ******* (***** than ***** ****** *********).
More ******* ******* - ***** ********, ******, *************
** ******** ** *** and *********:
- ****** ********* *** ******* inputs *** *** ********* as ****
- ***** ******* ** ******** imaging ************* **** ** focus, ********, ** *** filter, *** **** *** also *** ******** ** Profile *, ******* **** more ** ***** ************* in *** *** ****** than ** **** ****** integrations.
- *** ******* *** ******* in ******* * ** support ******** ***********. ******** specs ******** **** ******* of ******* *** *****.
****** ***** *** ******* less ********* **** ***** motion *********, **** ******* configuration ************, ********* **** support ****** *** *****'* usefulness/completeness, ** ***** ******** historically **** ******** *********** VMS ***********.
Camera ******* ******* ****
** *** *** ****** since *** *******, **** 400 ******* **** **** listed ** ******* * conformant, **** ******** *************, including ****, *****, *********, Sony, *** *******.*** *****'* *********** ********.
No *** ******* ***
*******, ** ** ***********, no *** ** *** is ****** ** ******* T **********. ** ****** VMS ********** ** *** when ******* *** ********, and *** ******** ******* Q1/Q2 ** **** ** the ********, **** **** having ** ******** ******** yet.
**** ******** *** *********** greater ********** ** *** integration ** ***** ********, as **** ***** **** not *** ********** *** performing **** ***** ** displaying ******** ********* ** Profile *, **** ** motion ****** ********, ******** rule *****, *** ******** boxes, ***** *** ******* entirely *** ** *******. By ********, **** ************** on *** ****** **** is *** ******* ** users.
Potential ******
**** ************* *** *********** have **** **** ***** did *** ** *** enough ** *********** ******* and ***** ** ***** replace ****** ****** ***********. The ******** ** ********* H.265 *******, ****** **** VMD, *********/***** ***********, *** imaging ******** ***** **** advanced ******** ***** **** pointed ** ** ***** of * "****" ***********.
************, ******* *'* **** complex ******** ********* ************ make **** ******** ***** analytics ************ ******** *** ONVIF, ***** ************ **** required *********** *** ***********, with **** ****** ************' analytics *** ********* ** many ***** (********* ** our** ****** ********* ********). ************* **** *** region ******** *** ***** format *** ****** ** increase ********* ******* *** potentially ****** ******** ************, as ***** *** ** able ** ********* ******** analytics **** *** **, instead ** ******** ******** camera *************' **********.
Poll / ****

Comments (16)
Undisclosed Manufacturer #1
Great article! The more information out about ONVIF the better! Now give us Point of Sales and this will be a happy holidays!
They also put together this document that is also great!
ONVIF Profile Feature Overview v2.2
Create New Topic
Igor Falomkin
In AxxonSoft we have implemented Profile T and tested it during ONVIF Plug Fests, but till this time were unable to apply for the conformance. Because to apply we have to test our integration with at least 3 certified cameras from different vendors, but the majority of cameras on the ONVIF site were certified only in this month (December). I think other VMS vendors had the same problem.
Create New Topic
Marc Pichaud
Profile T brings advanced features but the next revolution will also come when the "Q" is released, given as a real multiple brand remote setting monitoring.
It will simplify installations and maintenance processes. It's in the onvif road map pipe, but when is that really coming ... no lo sé ( as you know I'm training also technicians and it's a true mess with these hundreds of utilities, some with backdoors )
The old Onvif Device Manager should also be soon upgraded to support mister T profile, I presume, mmhh ? do you know more about that ?
Create New Topic
Marc Pichaud
I do agree Ethan.
It will come from the large users when they will mention "Q" devices or Q Vms for example in large public market tenders. At the time being, the level is so poor that the power users didn't even realize the benefits for the IT chain and costs (bandwidth, Cpu, Gpu, storage) of super compression options (smart compression, Dgop, H265) . So many great things coming and so few people able to understand or to use it ! Anyway, it's good for our training business but it does also explain why most large installations are not working properly.
Create New Topic
Luca Fogliati
Actually UNV claims their NVR support ONVIF T.I Havn't tested it yet but if you look at the specs of their products
Create New Topic
Igor Falomkin
The test procedure consists of the next steps:
- Save all the network traffic between our product and a camera using Wireshark network sniffer.
- Provide the saved traffic to the ONVIF test utility
- The utility analyses the traffic and infer what features are supported by the product
To confirm that the product supports a feature the utility must confirm the feature for at least three ONVIF Profile T cameras from different brands. If one of these cameras does not support a feature than the feature will be marked "No" even if the product supports it.
To get suitable cameras we contacted with 8 brands: Axis, Bosch, Sony, Hanwha, Hikvision, Uniview, Dynacolor, Honeywell. The brands those we used in the test were the brands those implement all Profile T mandotary features, were able to provide us a device and were most operative in communications.
Create New Topic
John Honovich
Update: Avigilon ACC 7 supports ONVIF Profile T now, joining Axxon:
Create New Topic
Horace Lasell
It's a day or so later, and I notice that ONVIF cites 7442 compliant products. I wonder if this actually means anything? Is it time for an update, asking, users and integrators, "Do you use this? Was the promise (eliminating multiple incompatible software, interfaces, and backdoors) realized?"
Create New Topic