ONVIF:...ration(3pm)

👑 NAME 👑

okay so bestie, gather round 💖 this is ONVIF::PTZ::Types::EngineConfiguration — a Perl data type class, living its best life in the ONVIF::PTZ::Types family. It's the manual page for it, from the User Contributed Perl Documentation section (that's section 3pm to the librarians). Yes it's a mouthful, no we're not renaming it, the name is the name and she's iconic ✨

---

🌸 DESCRIPTION 🌸

so basically 🫶 this is a Perl data type class for the XML Schema defined complexType called EngineConfiguration, and it comes from the namespace:

http://www.onvif.org/ver10/schema

that's it, that's the whole deal. it's a Perl-side glow-up of one specific complexType from that ONVIF schema namespace, and it's here to hold your data and look cute doing it 💅

---

🎀 PROPERTIES 🎀

the way that you get at these is through get_PROPERTY / set_PROPERTY methods — that's the access pattern, no cap. Here's what's available:

• VideoAnalyticsConfiguration
• AnalyticsEngineInputInfo

two properties, both accessible, both slaying ✨

---

💜 METHODS 💜

🦋 new 🦋

Constructor! It's giving classic Perl constructor energy 🎀 and here's the thing — the following data structure may be passed to new():

{ # ONVIF::PTZ::Types::EngineConfiguration
  VideoAnalyticsConfiguration =>  { # ONVIF::PTZ::Types::VideoAnalyticsConfiguration
    AnalyticsEngineConfiguration =>  { # ONVIF::PTZ::Types::AnalyticsEngineConfiguration
      AnalyticsModule =>  { # ONVIF::PTZ::Types::Config
        Parameters =>  { # ONVIF::PTZ::Types::ItemList
          SimpleItem => ,
          ElementItem =>  {
          },
          Extension =>  { # ONVIF::PTZ::Types::ItemListExtension
          },
        },
      },
      Extension =>  { # ONVIF::PTZ::Types::AnalyticsEngineConfigurationExtension
      },
    },
    RuleEngineConfiguration =>  { # ONVIF::PTZ::Types::RuleEngineConfiguration
      Rule =>  { # ONVIF::PTZ::Types::Config
        Parameters =>  { # ONVIF::PTZ::Types::ItemList
          SimpleItem => ,
          ElementItem =>  {
          },
          Extension =>  { # ONVIF::PTZ::Types::ItemListExtension
          },
        },
      },
      Extension =>  { # ONVIF::PTZ::Types::RuleEngineConfigurationExtension
      },
    },
  },
  AnalyticsEngineInputInfo =>  { # ONVIF::PTZ::Types::AnalyticsEngineInputInfo
    InputInfo =>  { # ONVIF::PTZ::Types::Config
      Parameters =>  { # ONVIF::PTZ::Types::ItemList
        SimpleItem => ,
        ElementItem =>  {
        },
        Extension =>  { # ONVIF::PTZ::Types::ItemListExtension
        },
      },
    },
    Extension =>  { # ONVIF::PTZ::Types::AnalyticsEngineInputInfoExtension
    },
  },
},

like, look at that nesting. it's giving main character energy, fr fr 😭 every level is a whole vibe — VideoAnalyticsConfiguration spills into AnalyticsEngineConfiguration (with its AnalyticsModule and Extension) AND RuleEngineConfiguration (with its Rule and Extension), and then AnalyticsEngineInputInfo does its own thing with InputInfo and Extension. copy it exactly, don't freestyle it, the schema is watching 👀

---

🌈 AUTHOR 🌈

Generated by SOAP::WSDL — yeah, it wasn't hand-written by a human with a candle and a dream, it was generated. respect the machine's hustle 🤖✨

---

and that's the whole page bestie!! this was ONVIF::PTZ::Types::EngineConfiguration, shipped in the User Contributed Perl Documentation collection, running on perl v5.40.1, and dated 2026-02-01. go forth and build your EngineConfiguration objects, you absolute legend 👑💖 periodt.