[FFmpeg-devel] [PATCH] lavc add XVBA decoder and hardware accelerator

Feng Duan digamma2function at gmail.com
Tue Jul 2 02:50:18 CEST 2013


Hi,

Sorry again. I will rewrite them all. Thank you give me a lesson.

Best Regards.

Feng


On Tue, Jul 2, 2013 at 1:59 AM, Rainer Hochecker <fernetmenta at online.de>wrote:

> compn <tempn <at> twmi.rr.com> writes:
>
> >
> > On Mon, 1 Jul 2013 10:09:08 +0000 (UTC), Rainer Hochecker wrote:
> > >After a brief look into this code I have to say that I don't support
> it. I
> > >had good reasons not to include e.g. opening the decoder inside ffmpeg.
> You
> > >do XOpenDisplay inside ffmpeg which I consider a no-go.
> >
> > isnt it possible to have two parts in ffmpeg? the hwaccel code that
> > xbmc will use, and then the decoder wrapper that other projects (like
> > ffmpeg binary itself or mplayer project) can use without having to write
> > a special video output ?
> >
> > making sure it has all the features xbmc needs is important.
> > adding one or two things to make it work for other projects will
> > also help.
> >
> > -compn
> >
>
> Sure it is possible. As I already mentioned I was not finished with this.
> My
> xvba implementation followed vdpau style. Applications like XBMC need full
> control over the decoder context because of interoperation with GL, refresh
> rate switching, etc .
> Currently my xvba implementation makes no use of a HWAccel context. (this
> is
> on my todo list). An application could request the wrapper via this context
> if desired.
>
> I am still wondering about the fact that somebody grabed my code without
> contacting me, tailored it to his needs, and submitted it upstream. This is
> unbelievable.
>
>
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>


More information about the ffmpeg-devel mailing list