December 2021 - FFmpeg-trac - lists.ffmpeg.org

#6609(ffmpeg:new): SamplingRateBox should be used if the value is greater than INT16_MAX
by FFmpeg 23 Nov '24

23 Nov '24

#6609: SamplingRateBox should be used if the value is greater than INT16_MAX -------------------------------------+------------------------------------- Reporter: fbeaufort | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: Keywords: flac, | unspecified isobmff, mp4 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: SamplingRateBox should be used if the value is greater than INT16_MAX How to reproduce: 1. Grab file from https://storage.googleapis.com/media-session/bear- 1280x720.mp4 2. Run ffmpeg command below {{{ % ffmpeg -i bear-1280x720.mp4 -map 0:0 -acodec flac -strict -2 -ar 192000 bear-flac-192kHz.mp4 }}} 3. The `bear-flac-192kHz.mp4` file should have a valid sample rate, not 0. Here are some #ffmpeg logs for some context: {{{ 12:58:08 PM <jya> you can create a bug that the SamplingRateBox (as per ISO 14496-2 12.2.3.2) is to be used if the value is greater than INT16_MAX 12:59:14 PM <jya> they have provision for that inthe SoundDescription V2, but i can't find this anywhere in the spec 12:59:20 PM <jya> must be a QT thing 1:00:14 PM <jya> and if they properly create a SamplingRateBox, need to file a bug in Firefox that our mp4 demuxer doesn't support it :) }}} And here's the ffmpeg version: {{{ % ffmpeg -version ffmpeg version 3.3.3-static http://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2017 the FFmpeg developers }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/6609> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 11

#7855(undetermined:new): Last subtitle in MP4 is displayed forever
by FFmpeg 23 Nov '24

23 Nov '24

#7855: Last subtitle in MP4 is displayed forever --------------------------------------+---------------------------------- Reporter: fumoboy007 | Type: defect Status: new | Priority: normal Component: undetermined | Version: 4.1 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+---------------------------------- Summary of the bug: Decoding the last tx3g subtitle in an MP4 produces an incorrect duration, causing the subtitle to stay on-screen until the end of the media. How to reproduce: Play the attached file in VLC. Also, run the following command and compare the outputted subtitle file with the original subtitle file (also attached). {{{ $ ffmpeg -i Permanent\ Last\ Subtitle.mp4 -map 0:s:0 FFmpeg\ Output.srt ffmpeg version 4.1 Copyright (c) 2000-2018 the FFmpeg developers built with Apple LLVM version 10.0.0 (clang-1000.11.45.5) configuration: --prefix=/usr/local/Cellar/ffmpeg/4.1_1 --enable-shared --enable-pthreads --enable-version3 --enable-hardcoded-tables --enable- avresample --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gpl --enable-libmp3lame --enable-libopus --enable-libsnappy --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-lzma --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable- libopencore-amrwb --enable-librtmp --enable-libspeex --enable-videotoolbox libavutil 56. 22.100 / 56. 22.100 libavcodec 58. 35.100 / 58. 35.100 libavformat 58. 20.100 / 58. 20.100 libavdevice 58. 5.100 / 58. 5.100 libavfilter 7. 40.101 / 7. 40.101 libavresample 4. 0. 0 / 4. 0. 0 libswscale 5. 3.100 / 5. 3.100 libswresample 3. 3.100 / 3. 3.100 libpostproc 55. 3.100 / 55. 3.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Permanent Last Subtitle.mp4': Metadata: major_brand : mp42 minor_version : 1 compatible_brands: mp41mp42isom creation_time : 2019-04-18T05:09:42.000000Z Duration: 00:01:05.04, start: 0.000000, bitrate: 431 kb/s Stream #0:0(deu): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, smpte170m), 640x360, 289 kb/s, 23.97 fps, 23.98 tbr, 24k tbn, 48k tbc (default) Metadata: creation_time : 2019-04-18T05:09:42.000000Z handler_name : Core Media Video encoder : AVC Coding Stream #0:1(deu): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 137 kb/s (default) Metadata: creation_time : 2019-04-18T05:09:42.000000Z handler_name : Core Media Audio Stream #0:2(eng): Subtitle: mov_text (tx3g / 0x67337874), 640x54, 0 kb/s (default) Metadata: rotate : 0 creation_time : 2019-04-18T05:10:26.000000Z Output #0, srt, to 'FFmpeg Output.srt': Metadata: major_brand : mp42 minor_version : 1 compatible_brands: mp41mp42isom encoder : Lavf58.20.100 Stream #0:0(eng): Subtitle: subrip (srt), 640x54 (default) Metadata: encoder : Lavc58.35.100 srt creation_time : 2019-04-18T05:10:26.000000Z Stream mapping: Stream #0:2 -> #0:0 (mov_text (native) -> subrip (srt)) Press [q] to stop, [?] for help size= 0kB time=00:00:45.25 bitrate= 0.0kbits/s speed=3.59e+04x video:0kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 79.069771% }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/7855> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 21

#7485(undetermined:new): HLS not accurately seeking
by FFmpeg 23 Nov '24

23 Nov '24

#7485: HLS not accurately seeking -------------------------------------+------------------------------------- Reporter: lletourn | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Seeking accurately in HLS videos doens't work, but it works fine in other containers (mp4, mkv, etc) tried with ffmpeg version 3.4.4 and master f85fa100db7d35952 {{{ % ./ffmpeg version N-92147-gf85fa100db Copyright (c) 2000-2018 the FFmpeg developers built with gcc 7 (Ubuntu 7.3.0-16ubuntu3) configuration: --enable-libfreetype --enable-gpl --enable-libx264 --enable-libx265 --enable-nonfree --enable-libfdk-aac --enable-libopus --enable-libpulse --enable-libvpx --enable-openssl --enable-static libavutil 56. 19.101 / 56. 19.101 libavcodec 58. 32.100 / 58. 32.100 libavformat 58. 18.104 / 58. 18.104 libavdevice 58. 4.105 / 58. 4.105 libavfilter 7. 33.100 / 7. 33.100 libswscale 5. 2.100 / 5. 2.100 libswresample 3. 2.100 / 3. 2.100 libpostproc 55. 2.100 / 55. 2.100 }}} How to reproduce: Create an HLS video like this {{{ % mkdir a % ./ffmpeg -y -s 640x480 -f rawvideo -pix_fmt rgb24 -r 25 -i /dev/zero -vf "drawtext=fontfile=/usr/share/fonts/truetype/freefont/FreeMono.ttf: text=%{n}: x=(w-tw)/2: y=h-(2*lh): fontcolor=white: box=1: boxcolor=0x000000FF" -an -vcodec libx264 -preset medium -tune stillimage -crf 24 -pix_fmt yuv420p -shortest -force_key_frames "expr:gte(t,n_forced*5)" -bf 0 -hls_time 5 -hls_list_size 0 -hls_wrap 0 -hls_allow_cache 1 -hls_segment_filename "a/a_%04d.ts" -t 60 a/a.m3u8 }}} And also create it's mp4 counterpart: {{{ % ./ffmpeg -i a/a.m3u8 -codec copy a.mp4 }}} And try to seek in any segment: {{{ F=130;rm -f f.png;./ffmpeg -y -ss `awk "BEGIN {print (${F})/25}"` -i a/a.m3u8 -f image2 -q:v 1 -vframes 1 f.png ./ffplay f.png }}} Got frame 250 (bad) {{{ F=126;rm -f f.png;./ffmpeg -y -ss `awk "BEGIN {print (${F})/25}"` -i a/a.m3u8 -f image2 -q:v 1 -vframes 1 f.png ; feh f.png }}} Got frame 250 (bad) {{{ F=125;rm -f f.png;./ffmpeg -y -ss `awk "BEGIN {print (${F})/25}"` -i a/a.m3u8 -f image2 -q:v 1 -vframes 1 f.png ./ffplay f.png }}} Got frame 125 (good) {{{ F=124;rm -f f.png;./ffmpeg -y -ss `awk "BEGIN {print (${F})/25}"` -i a/a.m3u8 -f image2 -q:v 1 -vframes 1 f.png ./ffplay f.png }}} Got frame 125 (bad) Now try the same with the mp4 and you'll always get the exact right frame {{{ F=130;rm -f f.png;./ffmpeg -y -ss `awk "BEGIN {print (${F})/25}"` -i a.mp4 -f image2 -q:v 1 -vframes 1 f.png ./ffplay f.png }}} Got 130 (good) {{{ F=126;rm -f f.png;./ffmpeg -y -ss `awk "BEGIN {print (${F})/25}"` -i a.mp4 -f image2 -q:v 1 -vframes 1 f.png ./ffplay f.png }}} Got 126 (good) etc it seems to only be seeking on segment boundaries. -- Ticket URL: <https://trac.ffmpeg.org/ticket/7485> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 12

#9535(undetermined:new): PNG decoder fails processing more than a certain number of frames
by FFmpeg 20 Nov '24

20 Nov '24

#9535: PNG decoder fails processing more than a certain number of frames -------------------------------------+------------------------------------- Reporter: panthalassa | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: png | Blocked By: decoding | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: trying to encode a video with more than a certain number of frames from a .png sequence results in corrupted output and an out-of-memory scenario How to reproduce: Sorry but due to the absurd bandwith requirements I likely won't be able to upload the offending files. This can likely be reproduced by converting a long, losslessly compressed video into a sufficient number of PNG's (my stats: 11 minute 1080p video at 60fps = ~39,000 frames, each frame 1.9mb making the uncompressed video around 80gb) I acquired these frames from rendering in Blender Present on all versions I've tested from 3.4.8 to 4.4.1. Any png-based input fails with too many files in the directory - symptoms include the encoded video having scrambled frame order after about 1000 frames, as well as the [png @ 0x??? chunk too big] error after about 14750 processed frames. Taking a generous swathe of images around the error points and processing them separately produces no errors implying that a corrupted PNG is not to blame. Putting a smaller (1-2000) number of frames in a directory and processing them separately produces a successful result longer than 1000 frames, past the previous point of onset for corruption. Unknown exactly how many frames are needed to cause the error. Any format encoding that receiving raw PNG input appears to be bugged - libx264rgb, libx265, ffv1 tested Latest tested version: clean install of N-104671-g2cddb2f7a8 on a live USB of Linux Mint 19.1 MATE following the instructions on the Compile FFMPEG page {{{ % ffmpeg -framerate 60 -f image2 -pattern_type glob -i $1'/*.png' -vcodec libx265 -pix_fmt yuv420p10le -vf scale=out_range=pc $2 % ffmpeg -framerate 60 -f image2 -pattern_type glob -i $1'/*.png' -vcodec ffv1 -coder 1 -level 3 -threads 4 -slices 4 -pix_fmt bgra $2 ffmpeg version: N-104671-g2cddb2f7a8 built on ... Linux Mint 19.1 MATE live USB }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9535> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 14

#7978(undetermined:new): inaccurate conversion from YCbCr Narrow range to RGB Full range
by FFmpeg 19 Nov '24

19 Nov '24

#7978: inaccurate conversion from YCbCr Narrow range to RGB Full range -------------------------------------+------------------------------------- Reporter: cepesh | Type: defect Status: new | Priority: important Component: | Version: 4.1 undetermined | Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: inaccurate conversion from YCbCr Narrow range to RGB Full range How to reproduce: {{{ Command line: "C:\\tools\\ffmpeg-4.1.3\\bin\\ffmpeg.exe" -loglevel debug -report -s 3840x2160 -vcodec v210 -i YUV_pattern-2fr.v210 -vf "scale=in_color_matrix=bt2020:in_range=tv" -vframes 1 tiff_bug_00.tiff -y ffmpeg version 4.1.3 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 8.3.1 (GCC) 20190414 configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable- fontconfig --enable-gnutls --enable-iconv --enable-libass --enable- libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore- amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable- libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable- ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth libavutil 56. 22.100 / 56. 22.100 libavcodec 58. 35.100 / 58. 35.100 libavformat 58. 20.100 / 58. 20.100 libavdevice 58. 5.100 / 58. 5.100 libavfilter 7. 40.101 / 7. 40.101 libswscale 5. 3.100 / 5. 3.100 libswresample 3. 3.100 / 3. 3.100 libpostproc 55. 3.100 / 55. 3.100 }}} 100% White Source YCbCr value = 0x03ac, 0x0200, 0x0200 (940, 512, 512) Observed RGB value = 65283, 65283, 65283 Expected RGB value = 65535, 65535, 65535 58% White Source YCbCr value = 0x023c, 0x0200, 0x0200 (572, 512, 512) Observed RGB value = 37858, 37858, 37858 Expected RGB value = 38004, 38004, 38004 100% Magenta Source YCbCr value = 0x015a, 0x343, 0x039c Observed RGB value = 65280, 0, 65289 Expected RGB value = 65533, 0, 65535 -- Ticket URL: <https://trac.ffmpeg.org/ticket/7978> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 15

#9569(avformat:new): spdif: Unusual frame timing
by FFmpeg 19 Nov '24

19 Nov '24

#9569: spdif: Unusual frame timing -----------------------------------+-------------------------------------- Reporter: Mitzsch01 | Type: defect Status: new | Priority: normal Component: avformat | Version: git-master Keywords: spdif | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+-------------------------------------- '''Summary of the bug:''' When playing back a file containing a Dolby TrueHD track with passthrough enabled and you skip forward or backward audio is lost. (I tried it with mpv) In the console, it shows the following message: {{{ [ffmpeg] spdif: Unusual frame timing: 40872 => 18920, 40 samples/frame is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature that has not been implemented. [ffmpeg] spdif: If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel(a)ffmpeg.org) }}} It also occurs when you play a file that comes from a master and needed seamless branching. Whenever it hits the sequence that was merged, audio is lost and it shows the same message above. This behavior is present after the commits for this issue https://trac.ffmpeg.org/ticket/7731 were merged. The implementation before that worked fine in this regard. '''How to reproduce:''' Play any TrueHD file with passthrough enabled and skip forward or backward in the file. In most cases, the audio will be lost and you see the message ''spdif: Unusual frame timing:''. You may recover from this by skipping further. {{{ mpv 0.34.0-116-gd92cf77be5 Copyright © 2000-2021 mpv/MPlayer/mplayer2 projects built on Sat Dec 25 17:26:05 CET 2021 FFmpeg library versions: libavutil 57.13.100 libavcodec 59.15.101 libavformat 59.10.100 libswscale 6.1.102 libavfilter 8.21.100 libswresample 4.0.100 FFmpeg version: N-105030-g0c8741f819 }}} '''Samples:''' https://kodi.wiki/view/Samples -- Ticket URL: <https://trac.ffmpeg.org/ticket/9569> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 25

#8385(avformat:new): libavformat/aviobuf: A part of conditional expression is always true: whence != 2
by FFmpeg 18 Nov '24

18 Nov '24

#8385: libavformat/aviobuf: A part of conditional expression is always true: whence != 2 ----------------------------------+-------------------------------------- Reporter: Balling | Type: defect Status: new | Priority: normal Component: avformat | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- If you look here https://github.com/FFmpeg/FFmpeg/blob/b741a84a15aed8afa01800dbc4b8b0e344e5d… you will see that on line 265 we would have already returned if whence were SEEK_END (2). It is not changed in between. This change was done in commit: https://github.com/FFmpeg/FFmpeg/commit/7a6fe01f99cb95797ba59134f44b6666b1a… whence != SEEK_END is always true, so short circuiting and force will not be checked. Also see #8156 https://trac.ffmpeg.org/attachment/ticket/8156/project2019.tasks Dunno how to fix it. The code is like this (): {{{ if (whence != SEEK_CUR && whence != SEEK_SET) return AVERROR(EINVAL); if (whence == SEEK_CUR) { offset1 = pos + (s->buf_ptr - s->buffer); if (offset == 0) return offset1; if (offset > INT64_MAX - offset1) return AVERROR(EINVAL); offset += offset1; } if (offset < 0) return AVERROR(EINVAL); if (s->short_seek_get) { short_seek = s->short_seek_get(s->opaque); /* fallback to default short seek */ if (short_seek <= 0) short_seek = s->short_seek_threshold; } else short_seek = s->short_seek_threshold; offset1 = offset - pos; // "offset1" is the relative offset from the beginning of s->buffer s->buf_ptr_max = FFMAX(s->buf_ptr_max, s->buf_ptr); if ((!s->direct || !s->seek) && offset1 >= 0 && offset1 <= (s->write_flag ? s->buf_ptr_max - s->buffer : buffer_size)) { /* can do the seek inside the buffer */ s->buf_ptr = s->buffer + offset1; } else if ((!(s->seekable & AVIO_SEEKABLE_NORMAL) || offset1 <= buffer_size + short_seek) && !s->write_flag && offset1 >= 0 && (!s->direct || !s->seek) && (whence != SEEK_END || force)) { }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/8385> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 8

#5548(avcodec:new): FFV1 encoder creates invalid stream if width or height is 1 or 2
by FFmpeg 16 Nov '24

16 Nov '24

#5548: FFV1 encoder creates invalid stream if width or height is 1 or 2 ----------------------------------+--------------------------------------- Reporter: Zenitram | Type: defect Status: new | Priority: normal Component: avcodec | Version: unspecified Keywords: FFV1 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- Summary of the bug: FFV1 encoder creates an invalid stream if width or height is 1 or 2. technical description: is such scenario, num_v_slices has a value of 2 so slice_y should be maximum 1, but slices have slice_y = 2 everywhere (instead of = 0 or 1). How to reproduce: {{{ >ffmpeg -y -f lavfi -i testsrc -t 1 -filter:v scale="353:1" -vcodec ffv1 -level 3 353x1.mkv ffmpeg version N-79630-g9ac154d Copyright (c) 2000-2016 the FFmpeg developers built with gcc 5.3.0 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmfx --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable- libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo- amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable- libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable- libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib libavutil 55. 22.101 / 55. 22.101 libavcodec 57. 38.100 / 57. 38.100 libavformat 57. 34.103 / 57. 34.103 libavdevice 57. 0.101 / 57. 0.101 libavfilter 6. 44.100 / 6. 44.100 libswscale 4. 1.100 / 4. 1.100 libswresample 2. 0.101 / 2. 0.101 libpostproc 54. 0.100 / 54. 0.100 Input #0, lavfi, from 'testsrc': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (RGB[24] / 0x18424752), rgb24, 320x240 [SAR 1:1 DAR 4:3], 25 fps, 25 tbr, 25 tbn [matroska @ 0000000000f8e8e0] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. Output #0, matroska, to '353x1.mkv': Metadata: encoder : Lavf57.34.103 Stream #0:0: Video: ffv1 (FFV1 / 0x31564646), bgr0, 353x1 [SAR 4:1059 DAR 4:3], q=2-31, 200 kb/s, 25 fps, 1k tbn Metadata: encoder : Lavc57.38.100 ffv1 Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> ffv1 (native)) Press [q] to stop, [?] for help frame= 25 fps=0.0 q=-0.0 Lsize= 15kB time=00:00:00.96 bitrate= 130.4kbits/s speed=44.7x video:14kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 7.009154% >ffmpeg -i 353x1.mkv fake.mp4 ffmpeg version N-79630-g9ac154d Copyright (c) 2000-2016 the FFmpeg developers built with gcc 5.3.0 (GCC) configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmfx --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable- libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo- amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable- libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable- libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib libavutil 55. 22.101 / 55. 22.101 libavcodec 57. 38.100 / 57. 38.100 libavformat 57. 34.103 / 57. 34.103 libavdevice 57. 0.101 / 57. 0.101 libavfilter 6. 44.100 / 6. 44.100 libswscale 4. 1.100 / 4. 1.100 libswresample 2. 0.101 / 2. 0.101 libpostproc 54. 0.100 / 54. 0.100 [ffv1 @ 00000000025245e0] slice count invalid [matroska,webm @ 00000000001d6e60] Failed to open codec in av_find_stream_info [ffv1 @ 00000000025245e0] slice count invalid Input #0, matroska,webm, from '353x1.mkv': Metadata: ENCODER : Lavf57.34.103 Duration: 00:00:01.00, start: 0.000000, bitrate: 125 kb/s Stream #0:0: Video: ffv1 (FFV1 / 0x31564646), none, 353x1, SAR 1:255 DAR 353:255, 25 fps, 25 tbr, 1k tbn (default) Metadata: ENCODER : Lavc57.38.100 ffv1 DURATION : 00:00:01.000000000 [buffer @ 00000000025179e0] Unable to parse option value "-1" as pixel format Last message repeated 1 times [buffer @ 00000000025179e0] Error setting option pix_fmt to value -1. [graph 0 input from stream 0:0 @ 0000000002517500] Error applying options to the filter. Error opening filters! }}} Same if you invert width and height. -- Ticket URL: <https://trac.ffmpeg.org/ticket/5548> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#6521(avformat:new): HEIF support
by FFmpeg 15 Nov '24

15 Nov '24

#6521: HEIF support -------------------------------------+------------------------------------- Reporter: mateo | Owner: mateo Type: | Status: new enhancement | Component: avformat Priority: normal | Keywords: mov isom Version: | heif unspecified | Blocking: Blocked By: | Analyzed by developer: 0 Reproduced by developer: 0 | -------------------------------------+------------------------------------- With the upcoming iOS 11 release, Apple will use the HEIF format instead of the JPEG one as its default photo format. I've started working on adding this support to lavf/mov. I open this ticket to track my progress (and will update it accordingly). -- Ticket URL: <https://trac.ffmpeg.org/ticket/6521> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 24

#9357(avformat:new): HLS live seek support
by FFmpeg 11 Nov '24

11 Nov '24

#9357: HLS live seek support -----------------------------------+--------------------------------------- Reporter: SuRGeoNix | Type: enhancement Status: new | Priority: normal Component: avformat | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+--------------------------------------- The current API (hls demuxer) doesn't seem to provide/expose required information to implement HLS live seek as the playlists/segments are not known (HLSContext). Even if you just re-opening the format context to accomplish this with the 'live_start_index' avdict option you don't have the information of the segments/durations. Additionally, it seems that the hls demuxer sets AVFMTCTX_UNSEEKABLE flag always. Can't see the reason why it applies it for example in this HLS live stream (https://cph-p2p- msl.akamaized.net/hls/live/2000341/test/level_3.m3u8) It has been also seen even after seeking on HLS live stream that the timestamps are not related to the previous ones (before seeking) or to the first_timestamp or ic->start_time. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9357> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1