
darktable’s histogram, waveform and RGB parade can directly change the Exposure module. Dragging inside them is not always a harmless way to inspect or reposition a graph. If the photograph changes immediately after a scope gesture, inspect exposure and black level before adding another adjustment to compensate.
Recognize the active control regions
The official scopes manual describes interactive adjustment regions. In the histogram, the right-hand region controls exposure and the left-hand region controls black level. Drag direction changes the corresponding value. Scrolling in those regions can also adjust it.
Waveform and RGB parade use different spatial arrangements. The horizontal forms use upper and lower regions for exposure and black level; the vertical forms use right and left regions. Identify the current scope mode before interpreting a gesture. A familiar graph does not imply a passive display.
The saved-state and undo guide explains why the present module state and a historical command sequence are different evidence. Inspect the actual current parameters rather than relying on a memory that no processing slider was touched.
Diagnose one unexpected change
Suppose a hypothetical product editor tries to inspect a dark label in the histogram and drags over its left side. The black level changes, making the label harder to read. A second curve adjustment could conceal the symptom while leaving the unintended change in the processing chain.
On a disposable version, propose this diagnostic:
- Record the Exposure module’s current exposure and black-level values.
- Identify which scope is displayed and which interactive region was used.
- Make one small, deliberate test gesture in that region.
- Inspect the actual module values and visible result.
- Restore the specifically recorded state in the test copy before continuing real work.
This exercise has not been executed for this guide. It is intended to confirm a control relationship in the installed version, not to establish a universally correct exposure.
Recover the intended state precisely
For an accidental gesture, use a supported undo route while the change is identifiable, or restore the previously recorded intended value. Do not double-click an unfamiliar scope area as a general recovery tactic: the manual describes double-clicking the relevant area as resetting to its original value, which may differ from the custom value you wanted to preserve.
Keep an identified approved reference when judging the recovered image. A plausible brighter preview is not evidence that the original adjustment was restored.
Separate graph arrangement from image processing
The scopes module has its own display-mode buttons and layout controls. Use the documented module-resizing interaction when the goal is to change panel height, rather than dragging in an exposure-sensitive plotting region. Explain this distinction when teaching another editor a review workflow.
The shared-setting guide becomes relevant if the unintended value was later copied to a set: first identify the affected parameter and destinations before extending or reversing changes in bulk.
Accept the diagnosis when the gesture, altered parameter and observed appearance agree. If exposure and black level did not change, investigate another action instead of attributing every preview difference to scope interaction. Keep the graph’s measurement role and its editing role explicit in the next review.
Related tasks
- Why Can I Edit My Saved Layers but Not Undo Yesterday’s Steps?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Which Photo Edits Should I Copy to a Whole Set, and Which Should Stay Individual?
Sources and scope
- darktable user manual: scopes: Scopes allow direct exposure and black-level adjustment through region-specific drag or scroll; regions differ by mode and orientation.
Based on the current online darktable manual reviewed October 31, 2026. Match controls to the installed release. Examples and acceptance checks are proposed, not measured application or print tests.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.