> -----Original Message-----
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Michael Niedermayer
> Sent: Friday, March 29, 2019 01:48
> To: FFmpeg development discussions and patches <ffmpeg-
> de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] lavc/vaapi_decode: add va_profile
> format map support for HEVC_REXT
> 
> On Thu, Mar 28, 2019 at 12:03:53PM +0800, Linjie Fu wrote:
> > HEVC_REXT will be map to {VAProfileHEVCMain422_10,
> VAProfileHEVCMain444,
> > VAProfileHEVCMain444_10} in vaapi_profile_map[], since need to be
> distinguished
> > to select the exact va_profile.
> >
> > Add va_profile -> AV_PIX_FMT map for FF_PROFILE_HEVC_REXT to match
> the
> > exact va_profile.
> >
> > Signed-off-by: Linjie Fu <linjie...@intel.com>
> > ---
> >  libavcodec/vaapi_decode.c | 29 +++++++++++++++++++++++++----
> >  1 file changed, 25 insertions(+), 4 deletions(-)
> 
> breaks build
> 
> libavcodec/vaapi_decode.c:409:7: error: ‘VAProfileHEVCMain422_10’
> undeclared here (not in a function)
>      MAP(422_10,  YUYV422),
>        ^
> libavcodec/vaapi_decode.c:411:7: error: ‘VAProfileHEVCMain444’ undeclared
> here (not in a function)
>      MAP(444,     YUV444P),
>        ^
> libavcodec/vaapi_decode.c:412:7: error: ‘VAProfileHEVCMain444_10’
> undeclared here (not in a function)
>      MAP(444_10,  YUV444P10LE),
>        ^
> make: *** [libavcodec/vaapi_decode.o] Error 1

I'm not quite sure why it happens.
In va/va.h,  VAProfile for Main422_10, Main444, Main444_10 is declared:
    VAProfileHEVCMain422_10             = 24,
    VAProfileHEVCMain422_12             = 25,
    VAProfileHEVCMain444                     = 26,
    VAProfileHEVCMain444_10              = 27,
https://github.com/intel/libva/blob/c98b06d2b8c00dc4df628488b672711b3f0eb118/va/va.h#L380

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to