Bug 55913 - Vdpau driver lag
Summary: Vdpau driver lag
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-12 11:56 UTC by francesco
Modified: 2019-09-18 19:01 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
vdpau output (21.98 KB, text/plain)
2012-10-12 11:56 UTC, francesco
Details

Note You need to log in before you can comment on or make changes to this bug.
Description francesco 2012-10-12 11:56:49 UTC
Created attachment 68485 [details]
vdpau output

You said was now ready vdpau but when I try to watch a movie with this output on my radeon 4650 , the video run with some lag :(
Comment 1 Andy Furniss 2012-10-12 20:43:01 UTC
(In reply to comment #0)
> Created attachment 68485 [details]
> vdpau output
> 
> You said was now ready vdpau but when I try to watch a movie with this
> output on my radeon 4650 , the video run with some lag :(

R600 vdpau decode isn't perfect, depending on content you may notice some inaccuracy.

With x86, it probably won't beat CPU decode unless you have something old/slow and single core.

The lag you see I can recreate - it seems to be a mplayer2 issue, "real" mplayer works OK for me.
Comment 2 francesco 2012-10-12 23:53:03 UTC
Yes, really, is a issue of mplayer2, with mplayer I don't have any problem, you can close this bug. Xv is more efficient on my pc.
Comment 3 Andy Furniss 2012-10-13 15:37:52 UTC
Xv is a bit faster for me, but software decode + -vo vdpau can give a better vsync than Xv in some circumstances.
Comment 4 Grigori Goronzy 2012-10-22 22:04:07 UTC
mplayer2 uses advanced VDPAU functionality that mplayer does not use - the presentation queue. This works fine with Nvidia's implementation. Likely the bug is in Mesa's implementation of the presentation queue.
Comment 5 Andy Furniss 2012-10-23 11:42:57 UTC
(In reply to comment #4)
> mplayer2 uses advanced VDPAU functionality that mplayer does not use - the
> presentation queue. This works fine with Nvidia's implementation. Likely the
> bug is in Mesa's implementation of the presentation queue.

Maybe, but maybe it's something as simple as the fact (or way) that mesa vdpau is vsynced.

Some further testing results -

Use VDPAU_TRACE=1 and grep/awk/bash to get the diffs from the timestamps mplayer2 uses on vdp_presentation_queue_display.

Playing 25 fps on a 60Hz screen looks OK ish for a while -

50030334
33349000
50022000
33350000
50022000
33348000
50023000
33349000
50022000
33349000
33356334
33333332
50029334

but then when it starts lagging mplayer2 is asking for longer intervals -

100052334
16682334
100046000
16673000
100046000
16674000
83333330
66728336
83371000
66697000
83372000
66697000
83370000
66699000
83370000

First thought it's trying to framedrop - maybe my GPU is too slow (it's powerful but set to low).

Turn it up and no lag - me thinks that's it then, but then mplayer works so another test.

GPU on low again but screen @120Hz also = no lag, so it's not just perf.

If you know mplayer2 code well perhaps that will tell yoou something.

Another separate observation SD or HD just -vo seems to work but the %cpu shown for vo rises. It seems it's rate of rise decreased as it gets higher so I don't know if it will ever get to 100 and start lagging.
Comment 6 GitLab Migration User 2019-09-18 19:01:13 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/424.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.