From 20.1 and later some settings that were previously set from the client workstation's local config or via the user profile are moved to the System-wide settings. The purpose of the System-wide settings is to make sure that settings are always the same between all client workstations and the server.
You can find the System-wide settings in the System management module: System → System-wide settings
The settings that were moved
- Visual Density Method
- Density Dud Threshold
Result of the changes
From MeasureColor versions 20.1 and later any settings for Visual density method and Density dud threshold that were previously set in either a local config on the client workstation or on the server in a user profile are ignored. Server and all clients will follow the System-wide settings, regardless of any other settings.
After updating the MeasureColor server to 20.1, please review the System-wide settings before using the software. Defaults have remained the same, so in most cases, nothing will happen.
Visual density method background
Densitometers switch density channels based on the ratio of measured values between the C, M, Y and V channel. Unfortunately, not all device follow the same method to do that. In order to let MeasureColor switch channels in the same fashion as the attached device, we made the density method used in MeasureColor configurable.
- Highest component (will always select the channel with the highest density)
Density Dud Threshold background
This setting defines which patches might be tagged as 'duds' when exporting a measurement SVF. In cases where MeasureColor is used as a frontend for a closed-loop system, you might not want to the system to act on an obviously faulty measurement even when an operator would let it slip through.
When the density threshold is exceeded, the patch will be tagged as 'dud' and skipped for correction by the closed-loop system.