Skip to content

Remove the 1..100 contrast limitation to avoid flicker #15

@dumblob

Description

@dumblob

I am a long time user of xcalib and for years I have been using the hack to first run xcalib -c and then xcalib -a -v | ... and then xcalib -a -co ... to simulate behavior of "percent points independent of the current state" instead of the current "percentage relative to the current state".

Now though I became too old to withstand the flickering due to xcalib -c.

Either of these solutions would do IMHO:

  1. Treat percentage as "percent points" instead of the current percentage of the current ICC/LUT state. Percent points would thus be an absolute scale all the time (not relative as they are now).
  2. Remove the 1..100 interval limitation and allow negative numbers on input (i.e. change the interval to -100..100).
  3. Allow deferred application of the resulting computation (i.e. "transactionally" without flickering) from a chain of operations in one xcalib invocation like e.g. gstreamer does. Imagine writing xcalib -a -c ! -a -co 50 would dry-run consecutively xcalib -a -c and then xcalib -a -co 50 internally but thanks to the "deferred" behavior it would apply to the screen only the resulting numbers effectively avoiding the flicker.

WDYT?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions