Specifications

• “command”: An action occurs when the value is set to something greater than “0” (e.g.
degauss). If you don't define any value element in a command control, the default value
“0x01” will be used.
• “list”: The control accepts a list of values (e.g. OSD language).
• refresh (only for list and command controls): Set whether other controls must be refreshed
after changing list value or running the command associated with the control (optional). Possible
values:
• “none”: Do not refresh anything. (default)
• “all”: Refresh all controls.
value attributes:
• id: abbreviated value name.
• name: full English value name (it is not needed if there is only one value for command con-
trols).
• value: DDC/CI control value (optional).
File format:
<?xml version="1.0"?>
<options date="%date%" dbversion="3">
<group name="%groupname%">
<subgroup name="%subgroupname%" pattern="%patternname%">
<control id="%control_id%" type="value" name="%control_name%"
address="%hex_address%"/>
<!-- Command using the default 0x01 address -->
<control id="%control_id%" type="command" name="%control_name%"
address="%hex_address%"/>
<control id="%control_id%" type="command" name="%control_name%"
address="%hex_address%">
<value id="%value_id%" value="%hex_value%"/>
</control>
<control id="%control_id%" type="list" name="%control_name%"
address="%hex_address%">
<value id="%value_id%" name="%value_name%" value="%hex_value%"/>
<value...>
</control>
<control ...>
</subgroup>
</group>
<group ...>
</options>
Monitor Profiles
XML files: monitor/%monitor_id%.xml
caps element
The caps attribute is optional. Its format is defined in ACCESS.bus specifications.
To add controls to caps, use the add attribute. To remove controls from caps, use the remove at-
tribute.
Note remove is handled before add, so if you remove and add a same control, it will finally be in
caps.
controls element
Documents for developers
15