Dynamic GOV / FPS and compression#741
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Co-authored-by: Sriram Bhetanabottla <sriram.bhetanabottla@axis.com>
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
| <xs:documentation>Optional - Indicates that the minimum framerate.</xs:documentation> | ||
| </xs:annotation> | ||
| </xs:element> | ||
| <xs:element name="EncodingStrategy" type="xs:string" minOccurs="0"> |
There was a problem hiding this comment.
Isn't this redundant if you can control the same with either DynamicFPS OR DynamicGov? We can add a requirement to keep it mutually exclusive unless both the strategies can be applied together and device needs to have some priority to choose one over the other?
There was a problem hiding this comment.
This extensible list allows the device to provide the names that match the best their smart encoding algorithm modes. The main usecase of EncodingStrategy is to configure the level of effort (Low, Mid, High). For instance, Axis devices have Zipstream modes (Low to Extreme), Hanwha has WiseStream modes, etc.
|
resolve the conversations if addressed/fixed. |
|
__WG meeting: agree with proposal, but replace number of i-Frames by GOP length. |
Rephrasing as discussed in the meeting of the video working group.
Add missing configuration for advanced bitrate reduction technologies
Last add EncodingEffortLevel - control how the device can reduce quality on lower interest region in order to reduce bandwidth. Dynamic GOV and FPS have more impact when effort level is high.