ONVIF:...Options(3pm)
β¨ ONVIF::PTZ::Types::VideoDecoderConfigurationOptions β¨
okay bestie, so this is a Perl data type class π it lives in the ONVIF:...Options corner of your manual pages (yes that's the 3pm one, we stan a third-section queen π), and it's literally just here to be a Perl data type class for the XML Schema defined complexType VideoDecoderConfigurationOptions, which comes from the namespace http://www.onvif.org/ver10/schema. that's the whole vibe. it's giving "glorified struct with a glow-up." π
πΈ DESCRIPTION πΈ
it's a Perl data type class for the XML Schema defined complexType VideoDecoderConfigurationOptions from the namespace http://www.onvif.org/ver10/schema.
no cap, that's it. it's a shape-shifter for XML, and its only job is to hold the decoder config tea π«
π PROPERTIES π
these are the properties you can get at with get_PROPERTY / set_PROPERTY methods, and yes you should use those, don't go poking at the hash directly like a gremlin π
JpegDecOptionsβ the JPEG decoder options, slayH264DecOptionsβ the H264 decoder options, iconicMpeg4DecOptionsβ the MPEG-4 decoder options, periodtExtensionβ the extension slot, for the extra stuff, iykyk
π¦ METHODS π¦
β new
Constructor bestie!! π this is where you hand it a data structure and it just gets it. here's exactly what you can pass to new():
{ # ONVIF::PTZ::Types::VideoDecoderConfigurationOptions
JpegDecOptions => { # ONVIF::PTZ::Types::JpegDecOptions
ResolutionsAvailable => { # ONVIF::PTZ::Types::VideoResolution
Width => $some_value, # int
Height => $some_value, # int
},
SupportedInputBitrate => { # ONVIF::PTZ::Types::IntRange
Min => $some_value, # int
Max => $some_value, # int
},
SupportedFrameRate => { # ONVIF::PTZ::Types::IntRange
Min => $some_value, # int
Max => $some_value, # int
},
},
H264DecOptions => { # ONVIF::PTZ::Types::H264DecOptions
ResolutionsAvailable => { # ONVIF::PTZ::Types::VideoResolution
Width => $some_value, # int
Height => $some_value, # int
},
SupportedH264Profiles => $some_value, # H264Profile
SupportedInputBitrate => { # ONVIF::PTZ::Types::IntRange
Min => $some_value, # int
Max => $some_value, # int
},
SupportedFrameRate => { # ONVIF::PTZ::Types::IntRange
Min => $some_value, # int
Max => $some_value, # int
},
},
Mpeg4DecOptions => { # ONVIF::PTZ::Types::Mpeg4DecOptions
ResolutionsAvailable => { # ONVIF::PTZ::Types::VideoResolution
Width => $some_value, # int
Height => $some_value, # int
},
SupportedMpeg4Profiles => $some_value, # Mpeg4Profile
SupportedInputBitrate => { # ONVIF::PTZ::Types::IntRange
Min => $some_value, # int
Max => $some_value, # int
},
SupportedFrameRate => { # ONVIF::PTZ::Types::IntRange
Min => $some_value, # int
Max => $some_value, # int
},
},
Extension => { # ONVIF::PTZ::Types::VideoDecoderConfigurationOptionsExtension
},
},
like. look at it. nested hashes all the way down, it's giving infinite nesting doll energy πͺ and the comments tell you the type of each thing so you literally cannot mess it up. Width is an int, Height is an int, Min and Max are ints, SupportedH264Profiles is an H264Profile, SupportedMpeg4Profiles is an Mpeg4Profile. everything else is its own lil complexType. you got this fr fr π
heads up bestie: don't go inventing keys that aren't in that structure, the schema is the schema and it will not be vibing with your freestyle π
π AUTHOR π
Generated by SOAP::WSDL β not a human, a whole machine did this, and honestly? it ate. π₯
and that's the whole page, my love π this beauty came to you from perl v5.40.1, dated 2026-02-01, and yes it's still rockin' that ONVIF:...Options(3pm) title card at the bottom like a signature perfume π go forth and decode, bestie, you're the main character now π
π¦ where this page comes from
- ubuntu resolute: zoneminder 1.36.37+dfsg1-1 Β· GPL-2.0-or-later
- ubuntu stonking: zoneminder 1.36.37+dfsg1-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms