Improve Capture One
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
Request a new feature, or support for a camera/lens that you would like to use in Capture One.
Hello Capture One Team,
I use Capture One on macOS with a Tangent Element panel. I am happy with the responsiveness of the existing Tangent integration, and Clarity works correctly when I turn its assigned physical knob.
However, Dehaze Amount does not appear in Capture One’s available controls in Tangent Mapper, so I cannot assign it to a knob. I would like to request native Tangent support for Dehaze Amount, allowing it to be controlled directly like other image adjustments.
When editing with the panel, I have to return to the mouse whenever I need to adjust Dehaze. This interrupts the panel-based workflow. My goal is simply to add a Dehaze knob to my existing Capture One mapping, not to replace the mapping or route all controls through another application.
I use some tools as floating panels. Consequently, Tangent Warp or other workarounds that depend on fixed screen coordinates are unsuitable for my workspace. I need native parameter control that works regardless of the Dehaze tool’s position or visibility, without requiring me to fix the tool in one location or change my workspace.
Please expose Dehaze Amount as a native Parameter that can be selected and assigned to a knob in Tangent Mapper, with:
Fine, relative increases and decreases through clockwise and counterclockwise knob rotation.
Current-value feedback on the panel display and the ability to reset Dehaze Amount to its default value from the panel.
Correct targeting of the current image variant and selected layer, wherever Dehaze is supported, independently of the tool’s screen position or visibility.
I would like to retain my existing Tangent mappings and use this control without a separate intermediary application or coordinate-based macros.
I inspected the following file included in my Capture One installation:
/Applications/Capture One.app/Contents/Resources/TangentSettings/controls.xmlClarity is registered as Parameter ID 0x00000032. However, I could not find a Parameter or Action definition for Dehaze in this file. controls.xmlXML controls.xmlXML
The AppleScript dictionary extracted from the same installation does define dehaze amount as a property of type real, with the property code CVda. I understand that this AppleScript property code and a Tangent Parameter ID belong to different interfaces. I am not assuming that the AppleScript definition proves that a native Tangent implementation already exists. CaptureOne-scripting-20260919-140508.xmlXML
Could you please confirm whether Capture One already contains a native Tangent handler for Dehaze Amount, with only the controls.xml definition missing?
If a handler already exists, please provide the correct Tangent Parameter ID, confirm whether value retrieval, adjustment and reset are supported, and advise whether there is an officially supported XML definition or update that would expose this control.
If the native Tangent handler has not yet been implemented, please treat this as a feature request for native Dehaze Amount support and forward it to the relevant development team.
I value the existing Tangent integration and would like to use Dehaze in the same direct, responsive way as the controls that already work. Please let me know the current support status and whether adding this control is under consideration.
Thank you.
Update: a working Warp workaround, and why native Tangent support is still needed
Capture One Support has confirmed that native Tangent control for Dehaze is not currently supported, and that this requires development work rather than simply adding a missing
controls.xmldefinition. This answers the technical question in my original request.Since posting, I have also found a working workaround using Tangent Warp to combine Capture One’s Speed Edit key with scroll input. This does not require fixed screen coordinates. I can now adjust Dehaze by turning a knob and reset only Dehaze by pressing it.
However, the experience of setting this up highlights an important reason why I am still requesting native support: keyboard-based panel controls can depend on the currently selected macOS keyboard input source.
I use both Korean and English input. With
Gassigned as the Dehaze Speed Edit key, the Warp control did not work while Korean input was selected and produced system alert sounds. Switching to English input made it work. Changing the assigned key to=resolved this particular problem, and Dehaze now works in both input states.That is a useful workaround, but finding a key that works is not the same as making panel operations independent of the language used for typing. Other shortcut-based assignments still need to be checked, and may require different keys or manual input-source switching. I am referring to the active keyboard input source, not Capture One’s interface language.
This matters because the benefit of the panel is not just speed. I adjust Contrast and Brightness together using a trackball, while using my other hand to adjust another parameter. Having to stop, check the input source and switch languages breaks the continuous connection between looking at the image and adjusting it.
What I would like is to separate the language I use for typing from the controls I use for adjusting images. The same panel operation should perform the same function whether Korean or English input is selected.
A related example is showing or hiding the selected layer’s mask overlay. I have not found a native Action for this in my current Tangent mapping. I mean toggling only the visible mask overlay while leaving the layer’s adjustments active—not enabling or disabling the layer. A direct Action would let me move between inspecting the mask and judging the image without relying on a keyboard shortcut.
I have asked Support whether this Action already exists and whether it should be submitted as a separate feature request. I mention it here because it illustrates the same need for direct, input-source-independent panel control.
For Dehaze specifically, my Warp configuration also does not provide current-value feedback to the panel’s OLED display. The requested native parameter control, reset and value feedback therefore remain relevant.
These observations are from my Korean/English setup, rather than a claim about every input method. I am not attributing the input-source behaviour to a particular technical cause; I am explaining why emulated keyboard input does not fully replace native integration in my workflow.
The workaround lets me continue working. Native support would remove the need to manage these extra conditions and let me keep my attention on the image.