[FFmpeg-trac] #8006(undetermined:closed): VAAPI: fails to transcode HEVC 10bit on AMD RAVEN APU

FFmpeg trac at avcodec.org
Tue Jul 9 14:27:44 EEST 2019


#8006: VAAPI: fails to transcode HEVC 10bit on AMD RAVEN APU
-------------------------------------+-------------------------------------
             Reporter:  tvsht        |                    Owner:
                 Type:  defect       |                   Status:  closed
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  git-master   |               Resolution:  invalid
             Keywords:  vaapi        |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by tvsht):

 Replying to [comment:1 jkqxz]:
 > This is the separated fields of surfaces in the Mesa driver biting you -
 you can't apply any postprocessing to the output of the H.265 decoder
 because you'll always fail a test like
 <https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/state_trackers/va/postproc.c#n131>.
 >
 > It works fine if you build Mesa with separated fields disabled, e.g. by:
 > {{{
 > diff --git a/src/gallium/state_trackers/va/surface.c
 b/src/gallium/state_trackers/va/surface.c
 > index 86daf0f7988..be72561df30 100644
 > --- a/src/gallium/state_trackers/va/surface.c
 > +++ b/src/gallium/state_trackers/va/surface.c
 > @@ -768,6 +768,7 @@ vlVaCreateSurfaces2(VADriverContextP ctx, unsigned
 int format,
 >        PIPE_VIDEO_ENTRYPOINT_BITSTREAM,
 >        PIPE_VIDEO_CAP_PREFERS_INTERLACED
 >     );
 > +   templat.interlaced = false;
 >
 >     if (expected_fourcc) {
 >        enum pipe_format expected_format =
 VaFourccToPipeFormat(expected_fourcc);
 > }}}


 Thank you, with this patch hw transcoding "works" above-mentioned bug is
 gone, but the resulting files are half green, I'm assuming I should report
 it to mesa's bugtracker? Could you link me to where this patch came from?

--
Ticket URL: <https://trac.ffmpeg.org/ticket/8006#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list