Bug 86781

Summary:	enabling glamor causes jumpy VDPAU playback with 2x framerate DI
Product:	Mesa	Reporter:	warpme
Component:	Drivers/Gallium/radeonsi	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium
Version:	10.3
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description warpme 2014-11-27 10:39:48 UTC

VDPAU playback of interlaced content starts to be jumpy when user enables glamor and DI is set to 2x.
Issue is seen under MythTV. Playback log reports:

2014-11-13 13:47:01.013753 I Player(1): Video is 3.18365 frames behind audio (too slow), dropping frame to catch up.
2014-11-13 13:47:01.013783 I AOBase: Pause 1
2014-11-13 13:47:01.014047 I Player(1): Video is 3.45023 frames behind audio (too slow), dropping frame to catch up.
2014-11-13 13:47:01.014064 I AOBase: Pause 1
2014-11-13 13:47:01.014171 I Player(1): Video is 3.40015 frames behind audio (too slow), dropping frame to catch up.
2014-11-13 13:47:01.014188 I AOBase: Pause 1
2014-11-13 13:47:01.014286 I Player(1): Video is 3.1126 frames behind audio (too slow), dropping frame to catch up. 

2x DI problem manifests only with enabled glamor. On Brazos with EXA, 2x DI works perfect while enabling glamor triggers 2x DI issue. 
On Kabini issue is always present as Kabini mandatory requires glamor. 

Tests were done with mesa 10.2.8/10.3.3 and xserver 1.16.1/1.16.2

Comment 1 Marek Olšák 2015-08-02 11:19:50 UTC

Does this still happen on current Mesa git?

Comment 2 warpme 2015-08-04 09:26:25 UTC

Marek,
I just checked with Mesa10.6.3/xorg1.17.2 and issue with too slow decode (manifested by "Video is 3.40015 frames behind audio") gone. 
Unfortunately interlaced video playback with any 2x framerate DI is not smooth as expected. Issue is seen on movements where I see v.short (50mSec like) picture freezes regularly every 0.5sec or so. 
Exactly the same software but with Nvidia HW and their closed source drivers plays perfectly. I didn't see anything in log's.
I would love to provide You more details if needed.

Comment 3 GitLab Migration User 2019-09-25 17:51:22 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/1212.

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.