ONVIF:...Options(3pm)

🌸 NAME 🌸

ONVIF::Analytics::Types::VideoDecoderConfigurationOptions — bestie, that's a whole mouthful, i know, but it's from the ONVIF:...Options(3pm) page in the User Contributed Perl Documentation, so you know it's the real deal 💅

---

✨ DESCRIPTION ✨

Okay so real talk: this is a Perl data type class ✨ It exists to represent one specific XML Schema defined complexType, and that complexType is literally named VideoDecoderConfigurationOptions, living in the namespace http://www.onvif.org/ver10/schema. That's it. That's the whole job. It's giving "i have one purpose and i slay at it" 👑

---

🎀 PROPERTIES 🎀

These are the properties you can reach, and the way you reach them is with get_PROPERTY / set_PROPERTY methods. No cap, that's the access pattern 🫶

• JpegDecOptions
• H264DecOptions
• Mpeg4DecOptions
• Extension

---

💅 METHODS 💅

✨ new ✨

Constructor energy 💖 It makes you a fresh object. And here's the data structure you're allowed to pass to new() — read it carefully, i'm not summarising a single line of it because every field matters:

{ # ONVIF::Analytics::Types::VideoDecoderConfigurationOptions
  JpegDecOptions =>  { # ONVIF::Analytics::Types::JpegDecOptions
    ResolutionsAvailable =>  { # ONVIF::Analytics::Types::VideoResolution
      Width =>  $some_value, # int
      Height =>  $some_value, # int
    },
    SupportedInputBitrate =>  { # ONVIF::Analytics::Types::IntRange
      Min =>  $some_value, # int
      Max =>  $some_value, # int
    },
    SupportedFrameRate =>  { # ONVIF::Analytics::Types::IntRange
      Min =>  $some_value, # int
      Max =>  $some_value, # int
    },
  },
  H264DecOptions =>  { # ONVIF::Analytics::Types::H264DecOptions
    ResolutionsAvailable =>  { # ONVIF::Analytics::Types::VideoResolution
      Width =>  $some_value, # int
      Height =>  $some_value, # int
    },
    SupportedH264Profiles => $some_value, # H264Profile
    SupportedInputBitrate =>  { # ONVIF::Analytics::Types::IntRange
      Min =>  $some_value, # int
      Max =>  $some_value, # int
    },
    SupportedFrameRate =>  { # ONVIF::Analytics::Types::IntRange
      Min =>  $some_value, # int
      Max =>  $some_value, # int
    },
  },
  Mpeg4DecOptions =>  { # ONVIF::Analytics::Types::Mpeg4DecOptions
    ResolutionsAvailable =>  { # ONVIF::Analytics::Types::VideoResolution
      Width =>  $some_value, # int
      Height =>  $some_value, # int
    },
    SupportedMpeg4Profiles => $some_value, # Mpeg4Profile
    SupportedInputBitrate =>  { # ONVIF::Analytics::Types::IntRange
      Min =>  $some_value, # int
      Max =>  $some_value, # int
    },
    SupportedFrameRate =>  { # ONVIF::Analytics::Types::IntRange
      Min =>  $some_value, # int
      Max =>  $some_value, # int
    },
  },
  Extension =>  { # ONVIF::Analytics::Types::VideoDecoderConfigurationOptionsExtension
  },
},

See how it nests? JpegDecOptions, H264DecOptions and Mpeg4DecOptions all carry their own ResolutionsAvailable (which is a ONVIF::Analytics::Types::VideoResolution with Width and Height, both int), their own SupportedInputBitrate and SupportedFrameRate (both ONVIF::Analytics::Types::IntRange with Min and Max, both int) 💖

The two that differ: H264DecOptions also has SupportedH264Profiles (an H264Profile) and Mpeg4DecOptions also has SupportedMpeg4Profiles (an Mpeg4Profile). And Extension is a ONVIF::Analytics::Types::VideoDecoderConfigurationOptionsExtension — empty in the example, but that's where the future-proofing lives 🌈

---

🫶 AUTHOR 🫶

Generated by SOAP::WSDL. Like, a machine wrote this one, and honestly? It ate 🔥

---

And that's the whole page, bestie — no notes, no filler, main character documentation energy only. This was perl v5.40.1, dated 2026-02-01, filed under ONVIF:...Options(3pm) in the User Contributed Perl Documentation. Go forth and configure your video decoder options 💖✨🎀🦋