All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96860] Aliasing when using vdpau with mpv
Date: Fri, 08 Jul 2016 14:12:42 +0000	[thread overview]
Message-ID: <bug-96860-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 96860
           Summary: Aliasing when using vdpau with mpv
           Product: Mesa
           Version: 11.2
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: dolohow@outlook.com
        QA Contact: dri-devel@lists.freedesktop.org

When using hardware decoding with radeonsi along with mpv I can observe
aliasing on rough edges.

It was previously reported on mpv issue tracker

  https://github.com/mpv-player/mpv/issues/3317

but the main developer pointed out that the bug is in mesa.

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

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

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

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

             reply	other threads:[~2016-07-08 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 14:12 bugzilla-daemon [this message]
2016-07-08 14:54 ` [Bug 96860] Aliasing when using vdpau with mpv bugzilla-daemon
2016-07-09 10:22 ` bugzilla-daemon
2016-07-12 19:45 ` bugzilla-daemon
2016-07-16 12:41 ` bugzilla-daemon
2016-07-18 13:11 ` bugzilla-daemon
2019-09-25 17:54 ` 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-96860-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.