[MPlayer-dev-eng] [PATCH]VO_VDPAU, round 2

Uoti Urpala uoti.urpala at pp1.inet.fi
Tue Jan 6 23:19:23 CET 2009

On Tue, 2009-01-06 at 20:09 +0100, Reimar Döffinger wrote:
> On Tue, Jan 06, 2009 at 07:52:53PM +0200, Jan Knutar wrote:
> > On the nvidia linux forums it seems they recommend setting additional 
> > env variables to get debug/trace printf's out of vdpau, which are yet 
> > more (and longer) error numbers, which the users post. Then nvidia 
> > folks reply and tell you the problem... :-)
> I know, quite a few companies like that approach to debugging, and I
> have heard the most ridiculous arguments for it, like "if we use a
> meaningful message, we need to get manager approval because it has to
> be translated, so we try use only meaningless messages".
> That does not make it better (ok, the approach of not checking errors
> at all is not really better, and I would not have minded much if a
> couple of -v messages just would have printed numbers, but having _all_
> in that style is not okay).

Also some specific number combinations apparently mean "hardware bug
prevents this set of parameters from working on this card". Fun
debugging your software if you can't know when your code is correct but
the drivers reject it because of a hardware problem...

More information about the MPlayer-dev-eng mailing list