[MPlayer-users] Issues with -vc ff*vdpau and -vc ff*vdpauold
nfxjfg at googlemail.com
Sat Nov 1 15:52:31 CET 2014
On Sat, 1 Nov 2014 15:34:57 +0100
Reimar Döffinger <Reimar.Doeffinger at gmx.de> wrote:
> On Sat, Nov 01, 2014 at 03:28:41PM +0100, wm4 wrote:
> > > I could blame people for not writing tests, but on the other
> > > hand I never finished my attempts either.
> > > So I'll only blame people for not actually showing interest in
> > > proper testing, but that seems to be standard operating mode
> > > for both MPlayer and VLC, unfortunately.
> > Well, ffmpeg.c now has hardware decoding support, but from what I hear
> > hw decoding is still hard to test. It's hard to run FATE in a way it
> > can actually access the GPU. And also, most codecs don't even require
> > bitexact output, I guess.
> For regression testing it is however sufficient to hash the critical
> structs passed to the VDPAU API.
> I think I've posted patches for that already, but it was a bit of a
> However what I'd really like but absolutely have no time for is a
> software reference implementation of the VDPAU API.
> This would allow testing on all FATE machines, regardless of what
> hardware they have.
> (as a first step such a reference implementation could also just
> serialize out the API calls up to that frame, which would be
> pure regression testing then).
There's already a "tracing" pseudo-driver  provided by nvidia. Would
that be helpful?
More information about the MPlayer-users