This repository has been archived by the owner on Nov 1, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 342
Presentation feedback API doesn't identify the frame submission #1917
Comments
emersion
added a commit
to emersion/wlroots
that referenced
this issue
Nov 16, 2019
This is set to the value of wlr_output.commit_seq when the frame has been submitted. This allows tracking presentation with more then 1 full frame of latency. References: swaywm#1917
emersion
added a commit
that referenced
this issue
Nov 16, 2019
This is set to the value of wlr_output.commit_seq when the frame has been submitted. This allows tracking presentation with more then 1 full frame of latency. References: #1917
aiqs4
pushed a commit
to aiqs4/wlroots
that referenced
this issue
Dec 19, 2019
This is set to the value of wlr_output.commit_seq when the frame has been submitted. This allows tracking presentation with more then 1 full frame of latency. References: swaywm#1917
aiqs4
pushed a commit
to aiqs4/wlroots
that referenced
this issue
Dec 19, 2019
This is set to the value of wlr_output.commit_seq when the frame has been submitted. This allows tracking presentation with more then 1 full frame of latency. References: swaywm#1917
aiqs4
pushed a commit
to aiqs4/wlroots
that referenced
this issue
Dec 19, 2019
This is set to the value of wlr_output.commit_seq when the frame has been submitted. This allows tracking presentation with more then 1 full frame of latency. References: swaywm#1917
aiqs4
pushed a commit
to aiqs4/wlroots
that referenced
this issue
Dec 19, 2019
This is set to the value of wlr_output.commit_seq when the frame has been submitted. This allows tracking presentation with more then 1 full frame of latency. References: swaywm#1917
aiqs4
pushed a commit
to aiqs4/wlroots
that referenced
this issue
Dec 19, 2019
This is set to the value of wlr_output.commit_seq when the frame has been submitted. This allows tracking presentation with more then 1 full frame of latency. References: swaywm#1917
filips
pushed a commit
to filips/wlroots
that referenced
this issue
Mar 15, 2020
This is set to the value of wlr_output.commit_seq when the frame has been submitted. This allows tracking presentation with more then 1 full frame of latency. References: swaywm#1917
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The presentation feedback API in
wlr_output
doesn't let backends specify for which frame submission the event is. So presentation feedback doesn't work properly if the delay is greater than one frame.In practice, the DRM backend guarantees that the delay will be < 1 frame. However that's not the case for other backends.
We should add a way to track frame submissions (with a sequence number? with an object?). We already have
output->commit_seq
, we can probably re-use this for presentation feedback.The text was updated successfully, but these errors were encountered: