[PR #1913] docs: add Troubleshooting section for dim screen captures and slider brightness jump #1331

New issue

Open

opened 2026-10-02 22:09:50 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-10-02 22:09:50 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/MonitorControl/MonitorControl/pull/1913
Author: @ankitdhandharia
Created: 9/23/2026
Status: 🔄 Open

Base: main ← Head: docs/troubleshooting-dim-captures

📝 Commits (1)

831645f docs: add Troubleshooting section for dim captures and slider jump

📊 Changes

1 file changed (+15 additions, -0 deletions)

View changed files

📝 README.md (+15 -0)

📄 Description

What

Adds a Troubleshooting section to the README covering the two most frequently repeated support questions for displays without hardware (DDC) control:

Screenshots / screen recordings / screen sharing look dim — explains that shade-overlay dimming is captured while gamma-table dimming is not, and how to fix it by turning off Avoid gamma table manipulation.
Brightness jumps suddenly at a point on the slider — explains the software/hardware dimming handover on non-DDC displays and the same fix.

Why

The README has no Troubleshooting/FAQ section, yet these two questions recur often in Issues and Discussions and are answered the same way each time by the maintainer, e.g. #1446, #1252, #1388, and discussions #1453 / #1189. Documenting the cause and the one-setting fix in the README should reduce repeat questions and help users self-serve.

This is docs only (README.md); no code changes. It is complementary to the open code fix in #1877 (which excludes the overlay from capture for real displays) — the docs also cover the gamma default and the slider-jump case, which that PR does not.

Testing

Documentation change only. Rendered Markdown reviewed for correct formatting and links.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/MonitorControl/MonitorControl/pull/1913 **Author:** [@ankitdhandharia](https://github.com/ankitdhandharia) **Created:** 9/23/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs/troubleshooting-dim-captures` --- ### 📝 Commits (1) - [`831645f`](https://github.com/MonitorControl/MonitorControl/commit/831645f98dfb4a67afa278d80e9f9ff85defb494) docs: add Troubleshooting section for dim captures and slider jump ### 📊 Changes **1 file changed** (+15 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+15 -0) </details> ### 📄 Description ## What Adds a **Troubleshooting** section to the README covering the two most frequently repeated support questions for displays without hardware (DDC) control: 1. **Screenshots / screen recordings / screen sharing look dim** — explains that shade-overlay dimming is captured while gamma-table dimming is not, and how to fix it by turning **off** *Avoid gamma table manipulation*. 2. **Brightness jumps suddenly at a point on the slider** — explains the software/hardware dimming handover on non-DDC displays and the same fix. ## Why The README has no Troubleshooting/FAQ section, yet these two questions recur often in Issues and Discussions and are answered the same way each time by the maintainer, e.g. #1446, #1252, #1388, and discussions #1453 / #1189. Documenting the cause and the one-setting fix in the README should reduce repeat questions and help users self-serve. This is **docs only** (`README.md`); no code changes. It is complementary to the open code fix in #1877 (which excludes the overlay from capture for real displays) — the docs also cover the gamma default and the slider-jump case, which that PR does not. ## Testing Documentation change only. Rendered Markdown reviewed for correct formatting and links. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

gitea-mirror added the

pull-request

label

2026-10-02 22:09:50 -06:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

github-starred/MonitorControl#1331

No description provided.

Rows
Columns