August 2023 - FFmpeg-trac - lists.ffmpeg.org

#10509(undetermined:new): `select` filter doesn't support `ih` and `iw` constants
by FFmpeg 07 Aug '23

07 Aug '23

#10509: `select` filter doesn't support `ih` and `iw` constants -------------------------------------+------------------------------------- Reporter: | Type: defect alexey.rodionov | Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: filter | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Running e.g. the following command: {{{ ffmpeg -i input.mp4 -vf select='gt(ih\,1080)',scale=-2:1080 output.mp4 }}} causes the following error: {{{ [Parsed_select_0 @ 00000196cee7f500] [Eval @ 00000087f25fe3d0] Undefined constant or missing '(' in 'ih,1080)' [Parsed_select_0 @ 00000196cee7f500] Error while parsing expression 'gt(ih,1080)' [AVFilterGraph @ 00000196cee7f440] Error initializing filters Invalid argument }}} Support for `ih` and `iw` constants in the `select` filter would allow interesting complex one-line filters. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10509> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#10505(undetermined:new): Closed Captions decode but stop on DeckLink SDI
by FFmpeg 05 Aug '23

05 Aug '23

#10505: Closed Captions decode but stop on DeckLink SDI -------------------------------------+------------------------------------- Reporter: Brian | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: closed | Blocked By: caption decklink | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Closed Captions decode properly on Decklink SDI until the http/HLS stream provider drops captions during commercial breaks, after that happens, the captions never return back to working, unless you restart FFMPEG. The same issue does not happen directly streaming in VLC or if I use FFMPEG to stream the HLS to a UDP player or directly to a file (like the one I am providing). I believe this issue is only related to the Decklink output. The Decklink output continues to display the idle caption bars on line 21/O even though the captions have returned in the stream. I have a recording sample that triggers this action on Google Drive: https://drive.google.com/file/d/1d8ts13PqRDp2mNR9E7W_cR9ztkBNzLUk/view?usp=… How to reproduce: {{{ ./ffmpeg -i AMGCCtoNoCCb.ts -filter:v fps=30000/1001 -f decklink -top 1 -s 1920x1080 -r 30000/1001 -ar 48k -ac 2 -vcodec v210 "DeckLink SDI" ffmpeg version N-111626-g0ba719f726 built with gcc 9 (Ubuntu 9.4.0-1ubuntu1~20.04.1) }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/10505> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#10503(undetermined:new): the AC-3 core in the TrueHD audio track were not read correctly by the function av_format_find_stream_info in libavformat
by FFmpeg 04 Aug '23

04 Aug '23

#10503: the AC-3 core in the TrueHD audio track were not read correctly by the function av_format_find_stream_info in libavformat -------------------------------------+------------------------------------- Reporter: FionaLee | Type: defect Status: new | Priority: important Component: | Version: 4.0.6 undetermined | Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: The situation is that I am currently developing applications based on VLC source code and playing blue-ray videos. The number of tracks obtained is different from the number obtained by other players, and I am unable to list and play the AC-3 cores in TrueHD tracks. After analysis, it was found that the FFmpeg referenced by VLC has bugs. The AC-3 core in the TrueHD audio track were not read correctly by the function av_format_find_stream_info in libavformat,and the number of tracks is incorrect, making it impossible to play the AC-3 tracks. https://code.videolan.org/videolan/vlc/-/issues/28321 https://code.videolan.org/videolan/vlc/uploads/3a5adcbb333ec96c94c75ba921a6… How to reproduce: {{{ Use the FFmpeg library in the VLC sourcecode ,demux https://yw97-my.sharepoint.com/:u:/g/personal/8_yw97_onmicrosoft_com /EXqDZKwrMlVAsVj74B9iy5gBJ5KUzOUf5f6Gpv2i_-j1ug?e=mLYqEa you can see the AC-3 core is not correctly listed }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10503> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#10502(undetermined:new): var_stream_map doesn't support optional entries
by FFmpeg 02 Aug '23

02 Aug '23

#10502: var_stream_map doesn't support optional entries -------------------------------------+------------------------------------- Reporter: | Type: defect alexey.rodionov | Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: hls | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- I'm working on a service that takes a video file as input and generates HLS streams in various resolutions as output (like YouTube does). If the input file has no audio, running the following command: {{{ ffmpeg -i input.mp4 -map 0:v:0 -map 0:v:0 -map 0:v:0 -map 0:v:0 -map 0:a:0 -filter:v:0 scale=-2:360 -filter:v:1 scale=-2:480 -filter:v:2 scale=-2:720 -filter:v:3 scale=-2:1080 -f hls -hls_playlist_type vod -hls_flags independent_segments -master_pl_name master.m3u8 -hls_segment_filename stream_%v/chunk_%08d.ts -strftime_mkdir 1 -var_stream_map "v:0,name:360p,agroup:audio v:1,name:480p,agroup:audio v:2,name:720p,agroup:audio v:3,name:1080p,agroup:audio a:0,name:audio,agroup:audio" stream_%v.m3u8 }}} causes the following error: {{{ Stream map '0:a:0' matches no streams. To ignore this, add a trailing '?' to the map. }}} This error can be fixed by changing `-map 0:a:0` to `-map 0:a:0?`, but then another error occurs: {{{ [hls @ 000002928260f640] Unable to map stream at a:0 [hls @ 000002928260f640] Variant stream info update failed with status ffffffea [out#0/hls @ 000002928260f440] Could not write header (incorrect codec parameters ?): Invalid argument }}} Changing `a:0,name:audio,agroup:audio` to `a:0,name:audio,agroup:audio?` inside `-var_stream_map` doesn't help. The problem is that I don't know if the input file the user can upload has audio or not. I've found other mentions of this problem, e.g.: https://stackoverflow.com/q/54008205/#comment94853363_54008205 https://stackoverflow.com/a/59220868/#comment104669510_59220868 https://stackoverflow.com/a/69623106 Notes: The interesting thing is that there is another way to create an HLS streams using `dash` muxer with `-hls_playlist true` option instead of `hls` muxer: {{{ ffmpeg -i input.mp4 -map 0:v:0 -map 0:v:0 -map 0:v:0 -map 0:v:0 -map 0:a:0 -filter:v:0 scale=-2:360 -filter:v:1 scale=-2:480 -filter:v:2 scale=-2:720 -filter:v:3 scale=-2:1080 -use_template 1 -use_timeline 1 -adaptation_sets "id=0,streams=v id=1,streams=a" -hls_playlist true -f dash manifest.mpd }}} In this case changing `-map 0:a:0` to `-map 0:a:0?` is enough. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10502> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#10500(undetermined:new): Constant memory usage increase when doing 24/7 transcoding
by FFmpeg 02 Aug '23

02 Aug '23

#10500: Constant memory usage increase when doing 24/7 transcoding ---------------------------------------+---------------------------------- Reporter: Igor Serganov | Type: defect Status: new | Priority: normal Component: undetermined | Version: 6.0 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------------+---------------------------------- I am doing 24/7 live transcoding of various live sources (aac/mp3/hls) to different output formats (mostly mp3 and aac/adts). In all cases (regardless of input/output format) memory consumed by application slowly grows up (with approximate speed of 1Mb/hour). That is quite ok if there is a finite input as resources are freed when LibAV is done. But when doing 24/7 transcoding at some point (depending on the memory limit) the app container runs into OOM error and shuts down not gracefully. I am doing `av_packet_free` and `av_frame_free` of allocated packet/frames during main transcoding loop (see attached file). I cannot call it a 'memory leak' as all the resources are being freed in case if application processes finite input, exits transcoding loop and deallocates all the resources. Though if I do everything correctly in my code, I still consider this as a serious issue since with every read of decoded packet I can see increase of memory usage which is not reduced in the following iteration. Attaching the file with minimal code that reproduces the issue. After compiling the app can be run with command `./live -i <your-input>`. For the sake of simplicity, the application writes decoded stream to a file, however the same issue can be observed if output stream is written to http response instead of a file. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10500> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#7403(avformat:new): HLS Master Playlist fails being generated correctly
by FFmpeg 02 Aug '23

02 Aug '23

#7403: HLS Master Playlist fails being generated correctly -------------------------------------+------------------------------------- Reporter: barhom | Type: defect Status: new | Priority: normal Component: avformat | Version: Keywords: | unspecified hlsplaylist.c | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: {{{ ffmpeg -i input.ts -c copy -f hls -master_pl_name master.m3u8 -var_stream_map "v:0,a:0" "vs_%v/playlist.m3u8" }}} input.ts is attached. This has been tested on ffmpeg compiled on 2018-09-05. What is wrong: FFmpeg fails to read the bitrate of the input.ts and thus fails to write the master.m3u8 The code below is what controls this error. {{{ if (!bandwidth) { av_log(NULL, AV_LOG_WARNING, "Bandwidth info not available, set audio and video bitrates\n"); return; } }}} My thoughts is that the proper way would not to return if bandwidth is not available but simply write the playlist without the bandwidth information since it was not available. -- Ticket URL: <https://trac.ffmpeg.org/ticket/7403> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 13

#7313(avformat:new): hls_fmp4_init_filename not properly formated
by FFmpeg 02 Aug '23

02 Aug '23

#7313: hls_fmp4_init_filename not properly formated ----------------------------------+-------------------------------------- Reporter: dennisss | Type: defect Status: new | Priority: normal Component: avformat | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 1 Analyzed by developer: 1 | ----------------------------------+-------------------------------------- The documentation for the `hls_fmp4_init_filename` argument requires that if it is given, that it contains a "%v" string that will be replaced with the variation number. Likewise this is validated by the code here: [https://github.com/FFmpeg/FFmpeg/blob/c5329d64b1264ef1431732aad6f5b08d0c4b5…] But if a provide a value for it which is not the default ("init.mp4"), the "%v" does not get replaced and instead the variant number seems to have the fixed behavior of always appending it to the filename. So given a pattern of `something_init_%v.mp4`, it currently outputs a file named `something_init_%v_1.mp4`, while I would expect it to output `something_init_1.mp4`. If it helps, I think that the appending of the variant to the end occurs here: [https://github.com/FFmpeg/FFmpeg/blob/c5329d64b1264ef1431732aad6f5b08d0c4b5…] but there does not appear to be any consideration of "%v" in the string. If I comment out the entire validation block referenced in the first link and use the input pattern `something_init.mp4`, then it works fine for my needs, but is still inconsistent with the documentation. How to reproduce: {{{ % ffmpeg ..... -hls_fmp4_init_filename "something_init_%v.mp4" .... }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/7313> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2