dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84944] tearing on radeonsi vdpau deinterlacer
Date: Sun, 26 Oct 2014 20:44:05 +0000	[thread overview]
Message-ID: <bug-84944-502-wqho2wsMfg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-84944-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1735 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=84944

--- Comment #25 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to Christian König from comment #24)
> (In reply to Andy Furniss from comment #23)
> > My normal use case, however, is to have 2 screens - TV below monitor +
> > different refresh rates. Like this I don't get flips, but I also don't have
> > any tearing issues with deint. I always set cpus to perf - so I guess that
> > my system is fast enough to handle copy.
> 
> For your case it for some reason don't page flip because of the two screens
> setup. And it then indeed most likely tears because the deint shader needs
> to much time.

I don't tear.

> 
> But that's a completely different issue than what warpme has here. In this
> case here it don't page flip because MythTV is doing something odd.

Yea, I was just speculating that even if myth always messes up so there is no
flip that it only shows with deinterlacing due to the extra load and or the X2
framerate. It was really in response to -

"The question is why the heck do we fallback to a copy operation with glamor
when deinterlacing is enabled? Deinterlacing is independent of displaying
the video so this makes no sense." 

But what you since wrote below may be it and myth only "messes up" interlaced
content.

> My best guess is that MythTV is trying to crop the first and last line of
> the video to avoid flickering with BOB deinterlacing. But instead of
> providing a proper video_source_rect while calling VdpVideoMixerRender they
> resize their X window to be two lines less in height which is a really
> really bad idea.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2746 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-10-26 20:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 17:35 [Bug 84944] New: tearing on radeonsi vdpau deinterlacer bugzilla-daemon
2014-10-12 17:35 ` [Bug 84944] " bugzilla-daemon
2014-10-15  6:58 ` bugzilla-daemon
2014-10-19 19:41 ` bugzilla-daemon
2014-10-20  7:38 ` bugzilla-daemon
2014-10-20  8:09 ` bugzilla-daemon
2014-10-20 16:54 ` bugzilla-daemon
2014-10-20 17:23 ` bugzilla-daemon
2014-10-20 19:19 ` bugzilla-daemon
2014-10-20 20:53 ` bugzilla-daemon
2014-10-21  2:07 ` bugzilla-daemon
2014-10-21  8:35 ` bugzilla-daemon
2014-10-21  8:44 ` bugzilla-daemon
2014-10-21  8:48 ` bugzilla-daemon
2014-10-21 10:06 ` bugzilla-daemon
2014-10-22  9:43 ` bugzilla-daemon
2014-10-22 16:41 ` bugzilla-daemon
2014-10-23  1:39 ` bugzilla-daemon
2014-10-23  8:10 ` bugzilla-daemon
2014-10-23  8:35 ` bugzilla-daemon
2014-10-23 14:48 ` bugzilla-daemon
2014-10-24  1:54 ` bugzilla-daemon
2014-10-24 15:28 ` bugzilla-daemon
2014-10-26 12:16 ` bugzilla-daemon
2014-10-26 16:16 ` bugzilla-daemon
2014-10-26 20:44 ` bugzilla-daemon [this message]
2014-10-28 10:12 ` bugzilla-daemon
2014-11-11  9:53 ` bugzilla-daemon
2014-11-13  7:26 ` bugzilla-daemon
2014-11-13 13:50 ` 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-84944-502-wqho2wsMfg@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