xpra icon
Bug tracker and wiki

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#956 closed enhancement (fixed)

Looking for a way to determine FPS being rendered

Reported by: alas Owned by: alas
Priority: minor Milestone: 0.16
Component: client Version: 0.15.x
Keywords: Cc:

Description

I'm not particularly picky about where/how, but would it be possible to export/display/output FPS being rendered (or subregions being thusly rendered) by h264 (and presumably other video encodings)?

Xpra info might be an awkward means, but that would work. A parameter flag (maybe --display-fps=on?) would work. A flag that could be turned on with the server control channel would double-plus work. An extra line on one of the graphs (or a small extra graph) on the Session Info graphs tab would not only work, but it would be osx-shiny as well (maybe a purple line?).

Whatever would be easiest/least painful to implement, assuming its not entirely painful/unfeasible, would be hugely appreciated.

Attachments (1)

session-info-video-encoder-info.png (984.0 KB) - added by Antoine Martin 5 years ago.
the video encoder info shown as a per-window tooltip on session info

Download all attachments as: .zip

Change History (3)

Changed 5 years ago by Antoine Martin

the video encoder info shown as a per-window tooltip on session info

comment:1 Changed 5 years ago by Antoine Martin

Owner: changed from Antoine Martin to alas

The fps can already be found via xpra info (you will need r10387 or later to see the fps for vp8 / vp9):

$ xpra info | grep fps=
window[4].encoder.fps=20

To also see which encoder is used and the window title:

$ xpra info | egrep "encoder=|fps=|\.title=" | egrep -v "pipeline|connection"
window[4].encoder=vpx
window[4].encoder.fps=23
window[4].title=GLX Spheres

You can also see it client side on the session info dialog: attachment/ticket/956/session-info-video-encoder-info.png
You will need to hover over the each window id to see the details, which will refresh every second.

See also (vsync / opengl sync related): #981, #792, #386

If that is enough, please close.

Last edited 5 years ago by Antoine Martin (previous) (diff)

comment:2 Changed 5 years ago by alas

Resolution: fixed
Status: newclosed

Tested and working... all along.

Looks like enough for my purposes. Closing.

Note: See TracTickets for help on using tickets.