On 14/08/2020 10:30, Linjie Fu wrote:
On Fri, Aug 14, 2020 at 5:51 AM Mark Thompson <s...@jkqxz.net> wrote:
This precalculates all of the information we will need to define slice
and tile positions at init time rather than rebuilding some of it with
every slice. The control of tiles is generalised to match slices, so that
arbitrary tile and slice layouts are possible within the constraint that
slices can't cross tile boundaries (which comes from how VAAPI handles
slices and tiles). Support for the EQUAL_MULTI_ROWS slice structure fits
easily into this, so it is added at the same time.
Some inputs for EQUAL_MULTI_ROWS slice structure, I believe there are
some discussions in libva and hw behavior team. To be honest, I don't think
the current notation/comment is suitable for what the hw could do.
I'm not sure what you mean here. If some hardware needs a different slice
structure then a new one will need to be defined and implemented?
Even if you don't have any current hardware using it, it is likely to be useful
in the not-too-distant future given that it is the VP9/AV1 uniform tiling mode.
- Mark
_______________________________________________
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".
