Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pr rext support #41

Closed
wants to merge 16 commits into from
Closed

Conversation

fulinjie
Copy link
Collaborator

patch set for 422/422_10/444/444_10:

  • still needs to parse slice flags in lavc/hevcdec: set slice flags to make this really work;
  • still needs to think about lavu/pixdesc: modify to cope with competition of yuyv422/y210le.

@fulinjie
Copy link
Collaborator Author

fulinjie commented May 5, 2019

Seperate the behaviour of ff_vaapi_decode_make_slice_buffer for base and
rext.Otherwise will cause regression for:

ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -v verbose
-i ./Allegro_HEVC_Main10_HT51_PROCESSING_12-CTB32_192x200@60Hz_1.0.bin
-pix_fmt p010le -f rawvideo -vsync passthrough -vframes 5 -y
Allegro_HEVC_Main10_HT51_PROCESSING_12-CTB32_192x200_60Hz_1_0_192x200_P010.yuv

err message:
realloc(): invalid next size
I guess it should be fixed in driver.

@fulinjie fulinjie force-pushed the pr-rext_support branch 2 times, most recently from ec10210 to 3d2394c Compare May 5, 2019 08:59
@fulinjie
Copy link
Collaborator Author

fulinjie commented May 5, 2019

patch set for 422/422_10/444/444_10:

  • still needs to parse slice flags in lavc/hevcdec: set slice flags to make this really work;
    fix slice flags issue by 3d2394c, these flags are for HEVC SCC, and the use_integer_mv_flag is not used by driver, so simply removed.
  • still needs to think about lavu/pixdesc: modify to cope with competition of yuyv422/y210le.
    TBD.

@fulinjie
Copy link
Collaborator Author

fulinjie commented May 5, 2019

cope with the compatibility issue for early version of libva like FOURCC and HEVC Rext buffer support check.

@fulinjie
Copy link
Collaborator Author

rebased.

@uartie
Copy link
Collaborator

uartie commented Aug 21, 2019

please rebase to fix fate failure.

Parse all the constraint flags according to ITU-T Rec. H.265 (02/2018).

It can be passed to hw decoders to detemine the exact profile for Range
Extension HEVC.

Signed-off-by: Linjie Fu <linjie.fu@intel.com>
Add vaapi_parse_rext_profile and use profile constraint flags to
determine the exact va_profile for HEVC_REXT.

Add build object in Makefile for h265_profile_level dependency.

Signed-off-by: Linjie Fu <linjie.fu@intel.com>
Add function pointer field in vaapi_profile_map[], set profile_parser
for HEVC_REXT to find the exact va_profile.

Signed-off-by: Linjie Fu <linjie.fu@intel.com>
Signed-off-by: Fu Linjie <linjie.fu@intel.com>
yuyv422 and y210le has the same score when calling av_find_best_pix_fmt_of_2.

Current way is still a work around.

Signed-off-by: Fu Linjie <linjie.fu@intel.com>
Signed-off-by: Fu Linjie <linjie.fu@intel.com>
Signed-off-by: Fu Linjie <linjie.fu@intel.com>
Signed-off-by: Fu Linjie <linjie.fu@intel.com>
Signed-off-by: Fu Linjie <linjie.fu@intel.com>
Signed-off-by: Fu Linjie <linjie.fu@intel.com>
…0/444_10

Signed-off-by: Fu Linjie <linjie.fu@intel.com>
Seperate the behaviour of ff_vaapi_decode_make_slice_buffer for base and
rext.Otherwise will cause regression for:

ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -v verbose
-i ./Allegro_HEVC_Main10_HT51_PROCESSING_12-CTB32_192x200@60Hz_1.0.bin
-pix_fmt p010le -f rawvideo -vsync passthrough -vframes 5 -y
Allegro_HEVC_Main10_HT51_PROCESSING_12-CTB32_192x200_60Hz_1_0_192x200_P010.yuv

err message:
    realloc(): invalid next size
I guess it should be fixed in driver.

Signed-off-by: Fu Linjie <linjie.fu@intel.com>
Signed-off-by: Fu Linjie <linjie.fu@intel.com>
Signed-off-by: Fu Linjie <linjie.fu@intel.com>
Signed-off-by: Fu Linjie <linjie.fu@intel.com>
Signed-off-by: Fu Linjie <linjie.fu@intel.com>
@fulinjie
Copy link
Collaborator Author

closed temporary, will support ayuv/yuv210/yuv410 in fate and swscale separately.

@fulinjie fulinjie closed this Aug 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants