> > +AVCodec ff_vp9_qsv_decoder = {
> > + .name = "vp9_qsv",
> > + .long_name = NULL_IF_CONFIG_SMALL("VP9 video (Intel
> Quick
> > Sync Video acceleration)"),
> > + .priv_data_size = sizeof(QSVOtherContext),
> > + .type = AVMEDIA_TYPE_VIDEO,
> > + .id = AV_CODEC_ID_VP9,
> > + .init = qsv_decode_init,
> > + .decode = qsv_decode_frame,
> > + .flush = qsv_decode_flush,
> > + .close = qsv_decode_close,
> > + .capabilities = AV_CODEC_CAP_DELAY | AV_CODEC_CAP_DR1 |
> > AV_CODEC_CAP_AVOID_PROBING | AV_CODEC_CAP_HYBRID,
> > + .priv_class = &vp9_qsv_class,
> > + .pix_fmts = (const enum
> AVPixelFormat[]){ AV_PIX_FMT_NV12,
> >
> +
> AV_PIX_FMT_P010,
>
> Order of formats in pix_fmts declarations start to frighten me even more...
> To the concern I raised in patches #3,4 of this series...
This array here is just to declare the pix_fmt capability list，
But in qsvdec.c, the pix_fmts array is to init qsv HW and SW format for frame
allocation. It can't be a list for a specified clip, it should be NV12 OR (not
and ) P010 format .
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
