From: Jan Burgmeier <jan.burgmeier@unicon-software.com>
To: "Christian König" <deathsimple@vodafone.de>,
dri-devel@lists.freedesktop.org
Subject: Re: Heavy artifacts during hw accelerated playback of wmv files
Date: Fri, 31 Mar 2017 12:20:52 +0200 [thread overview]
Message-ID: <1490955652.21560.25.camel@unicon-software.com> (raw)
In-Reply-To: <48f3764d-bfb1-507c-7974-05debdae10c1@vodafone.de>
Hi,
the error only occurs with wmv, h264 works.
I created a bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=100510
Regards,
Jan
On Fri, 2017-03-31 at 09:13 +0200, Christian König wrote:
> Hi Jan,
>
> very interesting. Sounds like we somehow mess up the buffer placement
> so
> that it won't work any more with UVD.
>
> But this only happens with WMV files? Not with H264 or anything else?
>
> Anyway please open up a bug report on https://bugs.freedesktop.org/.
>
> Thanks,
> Christian.
>
> Am 30.03.2017 um 14:16 schrieb Jan Burgmeier:
> > Hi,
> >
> > with versions newer than libdrm-2.4.66 I have heavy artifacts
> > during hw
> > accelerated playback of wmv files vaapi/vdpau tested with
> > gstreamer-
> > 0.10 and ffmpeg based mpv.
> >
> > Bisect result:
> > db138b9ba12a0de5d6140832c0679c2418e3e7e0 is the first bad commit
> > commit db138b9ba12a0de5d6140832c0679c2418e3e7e0
> > Author: Michel Dänzer <michel.daenzer@amd.com>
> > Date: Thu Jan 21 18:08:49 2016 +0900
> >
> > radeon: Pass radeon_bo_open flags to the
> > DRM_RADEON_GEM_CREATE
> > ioctl
> >
> > Not doing so makes it impossible for radeon_bo_open callers to
> > set
> > any
> > RADEON_GEM_* flags for the newly created BO.
> >
> > Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> >
> > If I revert this commit on the current master branch the artefacts
> > are
> > gone.
> >
> > System environment:
> > -- chipset: AMD GX-217GA SOC with Radeon(tm) HD Graphics
> > -- system architecture: 32-bit
> > -- xserver: 1.19.1
> > -- mesa: 13.0.3, 13.0.6, 17.0.2
> > -- libdrm: 2.4.74
> > -- kernel: 4.4.11
> > -- Linux distribution: eLux
> > -- Machine or mobo model: HP t620 dual core thin client
> >
> > Regards,
> > Jan Burgmeier
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/dri-devel
>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-03-31 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 12:16 Heavy artifacts during hw accelerated playback of wmv files Jan Burgmeier
2017-03-31 6:54 ` Michel Dänzer
2017-03-31 7:13 ` Christian König
2017-03-31 10:20 ` Jan Burgmeier [this message]
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=1490955652.21560.25.camel@unicon-software.com \
--to=jan.burgmeier@unicon-software.com \
--cc=deathsimple@vodafone.de \
--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.