From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108917] gamma adjustments cause stuttering with amdgpu.dc=1, especially problematic with RedShift etc.
Date: Thu, 27 Jun 2019 11:02:26 +0000 [thread overview]
Message-ID: <bug-108917-502-THgmWyW1za@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108917-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 866 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108917
--- Comment #12 from tempel.julian@gmail.com ---
It seems some recent (kernel?) updates have mitigated the issue a lot when
running "redshift -t 4500:4500 -l 1:1", the transition phase is now free of
stutter. After that, there is still regular stutter though for subsequent gamma
adjustments by RedShift when Compton with vsync is active.
What is really interesting: There is kwin-lowlatency as a kwin fork with vsync
adjustments:
https://github.com/tildearrow/kwin-lowlatency
With its compositing, the performance issues of atomic modesetting seem to be
entirely missing. There is zero stutter when opening windows etc., and also
continuous RedShift adjustments don't stutter. At the same time, there is zero
tearing.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1798 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-06-27 11:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 23:43 [Bug 108917] gamma adjustments cause stuttering with amdgpu.dc=1, especially problematic with RedShift etc bugzilla-daemon
2018-12-01 23:44 ` bugzilla-daemon
2018-12-03 2:59 ` bugzilla-daemon
2018-12-03 8:42 ` bugzilla-daemon
2018-12-03 9:47 ` bugzilla-daemon
2018-12-03 9:47 ` bugzilla-daemon
2018-12-03 15:33 ` bugzilla-daemon
2018-12-03 20:49 ` bugzilla-daemon
2018-12-17 14:30 ` bugzilla-daemon
2019-01-16 20:57 ` bugzilla-daemon
2019-03-19 16:44 ` bugzilla-daemon
2019-03-19 16:47 ` bugzilla-daemon
2019-03-19 18:16 ` bugzilla-daemon
2019-04-19 14:18 ` bugzilla-daemon
2019-06-27 11:02 ` bugzilla-daemon [this message]
2019-06-27 14:01 ` bugzilla-daemon
2019-06-27 19:22 ` bugzilla-daemon
2019-09-11 13:36 ` bugzilla-daemon
2019-11-19 9:06 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-108917-502-THgmWyW1za@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox