SettingsProcessingGroupColorGroupExperimentalGroup Class |
Namespace: Zivid.NET
The SettingsProcessingGroupColorGroupExperimentalGroup type exposes the following members.
Name | Description | |
---|---|---|
SettingsProcessingGroupColorGroupExperimentalGroup | Constructor |
Name | Description | |
---|---|---|
Mode | This setting controls how the color image is computed.
`automatic` is the default option. `automatic` is identical to `useFirstAcquisition` for
single-acquisition captures and multi-acquisition captures when all the acquisitions have
identical (duplicated) acquisition settings. `automatic` is identical to `toneMapping` for
multi-acquisition HDR captures with differing acquisition settings.
`useFirstAcquisition` uses the color data acquired from the first acquisition provided. If
the capture consists of more than one acquisition, then the remaining acquisitions are not used
for the color image. No tone mapping is performed. This option provides the most control of
the color image, and the color values will be consistent over repeated captures with the same
settings.
`toneMapping` uses all the acquisitions to create one merged and normalized color image. For
HDR captures the dynamic range of the captured images is usually higher than the 8-bit color
image range. `toneMapping` will map the HDR color data to the 8-bit color output range by
applying a scaling factor. `toneMapping` can also be used for single-acquisition captures to
normalize the captured color image to the full 8-bit output. Note that when using `toneMapping`
mode the color values can be inconsistent over repeated captures if you move, add or remove
objects in the scene. For the most control over the colors, select the `useFirstAcquisition`
mode.
This setting is deprecated as of SDK 2.14. This setting will be removed in the next SDK major
version (SDK 3.0). The recommended way to do a 2D+3D capture is to set a `Settings2D` object
in the `Settings/Color` node. Tip: If you want to convert an existing settings.yml file to use
the `Settings/Color` node, you can import the .yml file into Zivid Studio and then re-export it
to .yml.
|
Name | Description | |
---|---|---|
Clone | Create a clone (deep copy) of the current instance | |
CopyWith | Create a clone (deep copy) of the current instance and invoke delegate on the clone | |
ToString | Get string representation of the object (Overrides ObjectToString.) |