[FFmpeg-devel] [PATCH] HWAccel infrastructure (take 7.1)
Tue Feb 24 22:19:33 CET 2009
On Tue, Feb 24, 2009 at 09:42:22PM +0100, Gwenole Beauchesne wrote:
> > Well, IMO while it needs little changes that patch takes the
> > "move the mess one step higher" approach.
> > One particular disadvantage of that approach is that e.g. you can't
> > see
> > if it would still be possible to "misuse" libswscale to convert
> > between
> > VDPAU- and YV12-format without API changes.
> I don't see how it was possible in "current" (in SVN) code either.
Hm? Of course it was not implemented, but what necessary _information_
would be missing for swscale to do such a conversion?
> > There are also other questions like if it can cause any issues that
> > AVFrame + PIX_FMT is no longer sufficient to interpret the data
> > (obviously this can be solved e.g. by added a codec identifier to
> > vdpau_render_state).
> This would be an interesting addition at the API level too. I also
> have VDP_CODEC_MPEG2 et al. identifiers in my code and the fact you
> need something similar is also a sign this could be a good addition to
> the API. But back to your question, do you have an example please? I
> don't quite understand your case. Thanks.
I don't have anything specific in mind, but what does e.g. libavfilter
use? Does it have access to codec_id/AVCodecContext? Not that I know
what libavfilter would do with compressed data...
More information about the ffmpeg-devel