gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-commit] /srv/bzr/gnash/trunk r12349: Silence some debugging m


From: Rob Savoye
Subject: Re: [Gnash-commit] /srv/bzr/gnash/trunk r12349: Silence some debugging messages.
Date: Wed, 04 Aug 2010 08:22:13 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.7) Gecko/20100720 Fedora/3.1.1-1.fc13 Lightning/1.0b2 Thunderbird/3.1.1

On 08/04/10 04:39, Benjamin Wolsey wrote:

> I think this should always apply to hwaccel: if I select vaapi and it
> fails to initialize (as it always does here), I certainly don't want to
> get Xv acceleration. Falling back to no acceleration would be slightly
> more sensible, but generally if I request something that doesn't work,
> it's most useful if gnash fails to start and tells me why instead of
> silently doing something else.

 I'm not so sure about that, I'll have to think about it after coffee...
Vaapi has been working for me fine, you just need libva, and a new
enough ffmpeg. I'll obviously have to make sure it still works after
this checkin.

> The only thing that really bothers me is the fallback to Xv, so feel
> free to revert this change and implement it a different way.

  As our Xv support doesn't work very well, and actually raises the cpu
load instead of lowering it, we probably don't want to use it anymore
anyway. The poroblems with Xv have been widely discussed before.

        - rob -




reply via email to

[Prev in Thread] Current Thread [Next in Thread]