It was addressed in a5679933c1b8b6bef5c5c3eb7c70d06c695066cf, 0c162854c1fa2a1e43ce5588b67842675f45e3c7 and 5a366f9770dd7b02b0721b2857d6baa96acdb0af.
Unified · Split
| @@ -97,7 +97,6 @@ Stuff that didn't reach the codebase: · 96 unmodified lines | |||
| 97 | - 7993ec19a hevc: Add hevc_get_pixel_4/8/12/16/24/32/48/64 | 97 | - 7993ec19a hevc: Add hevc_get_pixel_4/8/12/16/24/32/48/64 |
| 98 | - Removal of the custom atomic API (5cc0057f49, see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-March/209003.html) | 98 | - Removal of the custom atomic API (5cc0057f49, see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-March/209003.html) |
| 99 | - new bitstream reader (see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/209609.html) | 99 | - new bitstream reader (see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/209609.html) |
| 100 | - use of the bsf instead of our parser for vp9 superframes (see fa1749dd34) | ||
| 101 | - use av_cpu_max_align() instead of hardcoding alignment requirements (see https://ffmpeg.org/pipermail/ffmpeg-devel/2017-September/215834.html) | 100 | - use av_cpu_max_align() instead of hardcoding alignment requirements (see https://ffmpeg.org/pipermail/ffmpeg-devel/2017-September/215834.html) |
| 102 | - f44ec22e0 lavc: use av_cpu_max_align() instead of hardcoding alignment requirements | 101 | - f44ec22e0 lavc: use av_cpu_max_align() instead of hardcoding alignment requirements |
| 103 | - 4de220d2e frame: allow align=0 (meaning automatic) for av_frame_get_buffer() | 102 | - 4de220d2e frame: allow align=0 (meaning automatic) for av_frame_get_buffer() |