aboutsummaryrefslogtreecommitdiffstats
path: root/tests/checkasm/h264pred.c
diff options
context:
space:
mode:
authorAndreas Rheinhardt <andreas.rheinhardt@outlook.com>2024-06-04 12:14:10 +0200
committerAndreas Rheinhardt <andreas.rheinhardt@outlook.com>2024-06-20 18:58:38 +0200
commitc28e553cbfa70ba0ca635271f5154301889fb706 (patch)
tree96e95c42f0e0bde8bd968c371c392d8756d18603 /tests/checkasm/h264pred.c
parentf8b8f161634c5917b7cddbb3dd37440afd9105f9 (diff)
downloadffmpeg-c28e553cbfa70ba0ca635271f5154301889fb706.tar.gz
avcodec/mpegutils: Fix ff_draw_horiz_band()
Broken in 5ecf5b93dda9d0c69875b80d28929f0d97dd7d06. More precisely, 3994623df2efd2749631c3492184dd8d4ffa9d1b changed the precursor of ff_mpv_reconstruct_mb() to always decode to the first row of macroblocks for B pictures when a draw_horiz_band callback is set and to (they are exported to the caller via said callback and each row overwrites the previously decoded row; this was probably intended as a cache-optimization). This first macroblock row was used as source for the draw_horiz_band callback. This of course means that the ordinary output B-frame was not decoded correctly at all. Therefore the first aforementioned commit removed this special handling of draw_horiz_band; yet it did not remove the special handling for B-frames in ff_draw_horiz_band(), which broke draw_horiz_band for B-frames. This commit fixes this. (Actually, draw_horiz_band was already broken before 5ecf5b93dda9d0c69875b80d28929f0d97dd7d06 when using slice-threading: All slice-threads would write to the first row of macroblocks for B-frames, leading to data races. It seems no one has ever complained about this, just as no one has ever complained about the breakage caused by 5ecf5b93dda9d0c69875b80d28929f0d97dd7d06. Probably no one uses draw_horiz_band.) Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
Diffstat (limited to 'tests/checkasm/h264pred.c')
0 files changed, 0 insertions, 0 deletions