March 2024 - FFmpeg-trac - lists.ffmpeg.org

#10692(avfilter:new): Sending commands to atempo filter make it assert
by FFmpeg 13 Mar '24

13 Mar '24

#10692: Sending commands to atempo filter make it assert -------------------------------------+------------------------------------- Reporter: Cyryl Ł | Type: defect Status: new | Priority: normal Component: avfilter | Version: git- Keywords: filtering | master audio | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Minimal test case. Working commandline: {{{ % ffmpeg -v verbose -f lavfi -i "anullsrc=d=2,atempo=7" -f null - }}} Failing commandline: {{{ % ffmpeg -v verbose -f lavfi -i "anullsrc=d=2,asendcmd=c='0-1 atempo tempo 7;',atempo" -f null - ffmpeg version N-112839-gbbdedd9663 Copyright (c) 2000-2023 the FFmpeg developers built with gcc 13 (Ubuntu 13.2.0-4ubuntu3) configuration: --disable-doc --enable-debug --disable-optimizations --disable-stripping --enable-libx264 --enable-libx265 --enable-gpl --enable-libmp3lame --enable-libfdk-aac --enable-librubberband --enable- nonfree libavutil 58. 32.100 / 58. 32.100 libavcodec 60. 34.100 / 60. 34.100 libavformat 60. 17.100 / 60. 17.100 libavdevice 60. 4.100 / 60. 4.100 libavfilter 9. 13.100 / 9. 13.100 libswscale 7. 6.100 / 7. 6.100 libswresample 4. 13.100 / 4. 13.100 libpostproc 57. 4.100 / 57. 4.100 [Parsed_asendcmd_1 @ 0x55c9a6983c00] start_time:0.000000 end_time:1.000000 index:0 [Parsed_asendcmd_1 @ 0x55c9a6983c00] [enter] target:atempo command:tempo arg:7 index:0 [Parsed_asendcmd_1 @ 0x55c9a6983c00] [enter+expr] interval #0 start_ts:0.000000 end_ts:1.000000 ts:0.000000 [Parsed_asendcmd_1 @ 0x55c9a6983c00] Processing command #0 target:atempo command:tempo arg:7 [Parsed_asendcmd_1 @ 0x55c9a6983c00] Command reply for command #0: ret:Success res: [Parsed_asendcmd_1 @ 0x55c9a6983c00] [expr] interval #0 start_ts:0.000000 end_ts:1.000000 ts:0.023220 [Parsed_asendcmd_1 @ 0x55c9a6983c00] [expr] interval #0 start_ts:0.000000 end_ts:1.000000 ts:0.046440 [Parsed_asendcmd_1 @ 0x55c9a6983c00] [expr] interval #0 start_ts:0.000000 end_ts:1.000000 ts:0.069660 [Parsed_asendcmd_1 @ 0x55c9a6983c00] [expr] interval #0 start_ts:0.000000 end_ts:1.000000 ts:0.092880 [Parsed_asendcmd_1 @ 0x55c9a6983c00] [expr] interval #0 start_ts:0.000000 end_ts:1.000000 ts:0.116100 [Parsed_asendcmd_1 @ 0x55c9a6983c00] [expr] interval #0 start_ts:0.000000 end_ts:1.000000 ts:0.139320 [Parsed_asendcmd_1 @ 0x55c9a6983c00] [expr] interval #0 start_ts:0.000000 end_ts:1.000000 ts:0.162540 Assertion zeros != nsamples failed at libavfilter/af_atempo.c:539 fish: Job 1, '../FFmpeg/ffmpeg -v verbose -f …' terminated by signal SIGABRT (Abort) }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/10692> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#10900(undetermined:new): unable to build v6.1.1 without pthreads.
by FFmpeg 13 Mar '24

13 Mar '24

#10900: unable to build v6.1.1 without pthreads. --------------------------------------+---------------------------------- Reporter: glennmcc | Type: defect Status: new | Priority: normal Component: undetermined | Version: 6.1 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+---------------------------------- root@glennmcc-i7:~/build/ffmpeg-6.1.1# ./configure --disable-pthreads root@glennmcc-i7:~/build/ffmpeg-6.1.1# time make Even tho I disabled pthreads.... it still got these errors and it did not build ffmpeg, ffprobe, ffplay for Linux. In file included from libavcodec/vulkan.c:19: ./libavutil/vulkan.c: In function 'ff_vk_exec_pool_free': ./libavutil/vulkan.c:267:9: error: implicit declaration of function 'pthread_mutex_destroy'; did you mean 'ff_mutex_destroy'? [-Werror =implicit-function-declaration] 267 | pthread_mutex_destroy(&e->lock); | ^~~~~~~~~~~~~~~~~~~~~ | ff_mutex_destroy ./libavutil/vulkan.c: In function 'ff_vk_exec_pool_init': ./libavutil/vulkan.c:410:15: error: implicit declaration of function 'pthread_mutex_init' [-Werror=implicit-function-declaration] 410 | err = pthread_mutex_init(&e->lock, NULL); | ^~~~~~~~~~~~~~~~~~ ./libavutil/vulkan.c: In function 'ff_vk_exec_wait': ./libavutil/vulkan.c:507:5: error: implicit declaration of function 'pthread_mutex_lock' [-Werror=implicit-function-declaration] 507 | pthread_mutex_lock(&e->lock); | ^~~~~~~~~~~~~~~~~~ ./libavutil/vulkan.c:510:5: error: implicit declaration of function 'pthread_mutex_unlock'; did you mean 'ff_mutex_unlock'? [-Werror=implicit- function-declaration] 510 | pthread_mutex_unlock(&e->lock); | ^~~~~~~~~~~~~~~~~~~~ | ff_mutex_unlock cc1: some warnings being treated as errors make: *** [ffbuild/common.mak:81: libavcodec/vulkan.o] Error 1 -- Ticket URL: <https://trac.ffmpeg.org/ticket/10900> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#6939(build system:new): make install clean regression
by FFmpeg 12 Mar '24

12 Mar '24

#6939: make install clean regression -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: important | Component: build Version: git- | system master | Keywords: regression Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- http://ffmpeg.org/pipermail/ffmpeg-user/2017-December/038318.html Running `make install clean` is broken since cbe181c8e1611aaee2a85ab522e17b1322bdd4de {{{ $ ./configure --path=~/installationtest && make install clean ... ./ffbuild/pkgconfig_generate.sh: line 21: libavfilter/libavfilter.version: No such file or directory make: *** [libavdevice/libavdevice.pc] Error 1 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/6939> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#10715(ffmpeg:new): QSV decoder fails to get configured and issues Error initializing the MFX video decoder: unsupported (-3)
by FFmpeg 11 Mar '24

11 Mar '24

#10715: QSV decoder fails to get configured and issues Error initializing the MFX video decoder: unsupported (-3) -------------------------------------+------------------------------------- Reporter: tipoman | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: Keywords: ffmpeg , | unspecified qsv, intel, hevc , hardware | Blocked By: decoding | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- I have a RTSP server streaming h265(HEVC) video. I can play the video with Intel HW acceleration like this: {{{ ffplay -loglevel info -vcodec hevc_qsv -rtsp_transport tcp -i rtsp://192.168.1.88 }}} This uses two-way data RTP+RTCP exchange via additional UDP port. I need to be able to play the video by only receiving the RTP stream. I disabled incoming traffic on the server, made the server stream the video to the client IP on UDP port 5600. By looking at the messages log I sniffed the SDP info and saved it to a file named 60.sdp Added a=rtcp-mux option and was able to successfully see the video with this pipeline: {{{ ffmpeg -loglevel trace -protocol_whitelist udp,file,hevc,rtp,crypto -i ~/Videos/60.sdp -vcodec rawvideo -f matroska - | ffplay -i - }}} **60.sdp file** {{{ v=0 o=StreamingServer 38990265062388 38990265062388 IN IP4 0.0.0.0 s=RTSP Session c=IN IP4 127.0.0.1 t=0 0 a=range:npt=0- m=video 5600 RTP/AVP 97 a=control:video a=rtpmap:97 H265/90000 a=fmtp:97 profile-level-id=016000; packetization-mode=1; a=framerate:60 a=recvonly a=rtcp-mux }}} So far everything worked as expected. Then I added the HW acceleration option like this: {{{ ffmpeg -hide_banner -loglevel trace -vcodec hevc_qsv -protocol_whitelist udp,file,hevc,rtp,crypto -i ~/Videos/60.sdp -vcodec rawvideo -f matroska - | ffplay -hide_banner -i - }}} and got this error: {{{ [AVHWDeviceContext @ 0x5555b8020ac0] VAAPI driver: Intel iHD driver for Intel(R) Gen Graphics - 23.3.2 (). [AVHWDeviceContext @ 0x5555b8020ac0] Driver not found in known nonstandard list, using standard behaviour. [hevc_qsv @ 0x5555b7fe5500] Initialized an internal MFX session using hardware accelerated implementation [hevc_qsv @ 0x5555b7fe5500] Error initializing the MFX video decoder: unsupported (-3) Error while decoding stream #0:0: Function not implemented }}} Just to confirm, I'm able to play the same video stream on the local UDP port with hardware acceleration with GStreamer like this : {{{ gst-launch-1.0 udpsrc port=5600 buffer-size=65536 caps="application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H265" ! rtph265depay ! queue max-size-buffers=1 ! vaapih265dec ! autovideosink sync=false }}} Some details on the system. {{{ i3-1215u, Ubuntu 22.04.3 vainfo Trying display: wayland Trying display: x11 libva info: VA-API version 1.19.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_19 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.19 (libva 2.19.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 23.3.2 () ffmpeg version 4.4.2-0ubuntu0.22.04.1 Copyright (c) 2000-2021 the FFmpeg developers }}} Seems there is some problem of configuring the Intel QSV decoder from the ffmpeg pipeline. I think SPS/PPS/VPS settings are not set, but I can not be sure. Am I missing something or this is an issue in libavcodec/qsvdec.c ? -- Ticket URL: <https://trac.ffmpeg.org/ticket/10715> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#9766(undetermined:new): h264_qsv decoder does not work with RTSP
by FFmpeg 11 Mar '24

11 Mar '24

#9766: h264_qsv decoder does not work with RTSP -------------------------------------+------------------------------------- Reporter: Steve | Type: defect Sampson | Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: QSV RTSP | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: {{{ % ffmpeg.exe -init_hw_device qsv:hw,child_device_type=d3d11va -hwaccel qsv -c:v h264_qsv -hwaccel_output_format qsv -i rtsp://user:password@172.16.1.105/axis-media/media.amp -f null - ffmpeg version: ffmpeg version 5.0-full_build-www.gyan.dev downloaded on 2022-01-16, so build is around that date. Running on Windows 10 with an Intel GPU (Intel UHD Graphics 620, but I suspect this problem isn't related to the exact hardware version - it also reproduced on another machine). The RTSP stream comes from a camera. It looks like it has a pixel format of 720x576, pix_fmt: yuvj420p. If there is a way to capture this stream such that someone else can reproduce the error, please let me know. I suspect the reproduction of this problem requires a genuine RTSP server. When running, it initializes the connection to the RTSP server and then logs an error Error initializing the MFX video decoder: invalid video parameters (-15) The same command line successfully decodes using an mp4 file instead of an RTSP input (captured from the camera using ffmpeg -i rtsp://user:password@172.16.1.105/axis-media/media.amp -acodec copy -vcodec copy c:/abc.mp4) ''The RTSP stream decodes successfully without any hardware acceleration.'' That is, with a command line of "ffmpeg.exe -i rtsp://user:password@172.16.1.105/axis-media/media.amp -f null -". It also is correctly displayed in VLC. I tried many different combinations of command line parameters (for example just with -hwaccel qsv -c:v h264_qsv) and none were successful. }}} My commentary/analysis {{{ Note that I am not at all an expert on FFMPEG. I was tasked to GPU-enable our existing code and this is my first serious look at FFMPEG. The use case is to display the video from a set of cameras (all RTSP, all H264). Our code uses the FFMPEG API and doesn't use the FFMPEG program but my tests have been using FFMPEG. The actual build I wish(ed) to use is an older build of ffmpeg (branched in 2019 and slightly modified by my team - but the decoding wasn't touched). It gives a different error string but it may be a similar root cause. I tried to debug it to figure out what was going wrong. The error in that version was "non-existing PPS 0 referenced" (from parse_nal_units) and then "Decoding pixel format '(null)' is not supported" (from ff_qsv_process_data). I can't easily make my own build of FFMPEG (the process of building with Windows is too complex for me to quickly do) or I would attempt using the latest code. The SPD returned by the camera is the following SDP: v=0 o=- 1651685682795324 1651685682795324 IN IP4 172.16.1.105 s=Media Presentation e=NONE b=AS:50000 t=0 0 a=control:* a=range:npt=0.000000- m=video 0 RTP/AVP 96 c=IN IP4 0.0.0.0 b=AS:50000 a=framerate:25.0 a=transform:0.937500,0.000000,0.000000;0.000000,1.000000,0.000000;0.000000,0.000000,1.000000 a=control:trackID=1 a=rtpmap:96 H264/90000 a=fmtp:96 packetization-mode=1; profile-level-id=420029; sprop-parameter- sets=Z0IAKeKQFoJNgScFAQXh4kRU,aM48gA== }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/9766> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 19

#10895(avcodec:new): 'make clean' does not remove all object files
by FFmpeg 11 Mar '24

11 Mar '24

#10895: 'make clean' does not remove all object files -------------------------------------+------------------------------------- Reporter: Sean | Type: defect McGovern | Status: new | Priority: normal Component: avcodec | Version: git- | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- How to reproduce: {{{ % configure <whatever options> % make % make clean % find . -type f -name '*.o' }}} Results: {{{ ./libavcodec/x86/h26x/h2656dsp.o ./libavcodec/x86/h26x/h2656_inter.o }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/10895> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#10898(ffmpeg:new): gop_size (GopPicSize) defaults to 65535 in hevc_qsv encoding - regression / change of default behavior
by FFmpeg 09 Mar '24

09 Mar '24

#10898: gop_size (GopPicSize) defaults to 65535 in hevc_qsv encoding - regression / change of default behavior --------------------------------+---------------------------------- Reporter: fedy | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: 6.0 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+---------------------------------- Summary of the bug: Seems like the default behavior of the QuickSync hevc_qsv encoder (or maybe ffmpeg as a whole) regarding gop_size have changed. On ffmpeg 6.0.1, if not specified, it defaults to 65535 which results in unseekable encodes (single I frame / IDR frame). My previous test encodes (that were probably still using ffmpeg version 5) show it used to be 248 for a 25fps video which is much more reasonable. How to reproduce: {{{ % ffmpeg -hide_banner -loglevel verbose -hwaccel qsv -hwaccel_output_format qsv -c:v h264_qsv -i input.mp4 -map 0 -map -0:d:m:handler_name:TimeCodeHandler -c copy -copy_unknown -c:v hevc_qsv -global_quality 18 -preset slow -vf scale_qsv=format=p010le -write_tmcd auto output.mp4 ffmpeg version 6.0.1 built on ... (Fedora 38 / RPM Fusion) }}} Other notes: This behavior isn't completely new - found a reddit thread mentioning the behavior change about a year ago: https://www.reddit.com/r/ffmpeg/comments/zjwm4r/trouble_with_ffmpeg_using_q… Looking at the output from: {{{ ffmpeg -h encoder=hevc_qsv }}} I notice several options of type <int> where the declared range is -1 to 65535. Looks kind of weird: maybe these are 32bit signed values everywhere, just combining a 16-bit unsigned value range (0-65535) and a -1 "default/auto" and everything is fine, but if at any place they are interpreted as 16bit then -1 and 65535 overlap (they are represented as same 16bit bit pattern). Couldn't this be the reason behind the weird 65535 default? Probably unrelated: I also can't seem to make the following options work: {{{ -extbrc 1 -adaptive_i 1 -adaptive_b 1 }}} ... they show up as: {{{ [hevc_qsv @ 0x55edcbee4340] BitrateLimit: unknown; MBBRC: unknown; ExtBRC: OFF [hevc_qsv @ 0x55edcbee4340] Trellis: auto [hevc_qsv @ 0x55edcbee4340] RepeatPPS: OFF; NumMbPerSlice: 0; LookAheadDS: unknown [hevc_qsv @ 0x55edcbee4340] AdaptiveI: unknown; AdaptiveB: unknown; BRefType:pyramid }}} ... in ffmpeg output My test platform is: Intel Pentium Silver J5005 (Gemini Lake) -- Ticket URL: <https://trac.ffmpeg.org/ticket/10898> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#10395(undetermined:new): Broken MXF support
by FFmpeg 09 Mar '24

09 Mar '24

#10395: Broken MXF support -------------------------------------+------------------------------------- Reporter: slydiman | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: Here is the MXF sample recorded by Canon C300 http://slydiman.me/ffmpeg/mxf/test.mxf (60MB) I used ffmpeg nightly build version 20230507 with libavformat 60.5.100 ffmpeg_2021 is ffmpeg version 20210714 with libavformat 59.4.100 How to reproduce: {{{ ffmpeg -i test.mxf -c:v copy -y video.h264 ffmpeg_2021 -i video.h264 -c:v copy -y test1_ok.mxf ffmpeg -i video.h264 -c:v copy -y test2_fail.mxf [mxf @ 000002e37b40eac0] Unsupported frame rate 1200000/1. Set -strict option to 'unofficial' or lower in order to allow it! [out#0/mxf @ 000002e37b409900] Could not write header (incorrect codec parameters ?): Invalid argument Invalid argument ffmpeg -r 25 -i video.h264 -c:v copy -y test3_ok.mxf }}} {{{ ffmpeg -i test.mxf -c:v copy -an -y video.mp4 ffmpeg -i video.mp4 -c:v copy -y test4_fail.mxf [mxf @ 0000022e9ad499c0] Unsupported frame rate 12800/1. Set -strict option to 'unofficial' or lower in order to allow it! [out#0/mxf @ 0000022e9ad49880] Could not write header (incorrect codec parameters ?): Invalid argument Invalid argument ffmpeg -r 25 -i video.mp4 -c:v copy -y test5_fail.mxf [mxf @ 00000246dee3b180] h264 profile not supported [mxf @ 00000246dee3b180] could not get h264 profile av_interleaved_write_frame(): Operation not permitted [out#0/mxf @ 00000246dceb9400] Error muxing a packet [out#0/mxf @ 00000246dceb9400] Error writing trailer: Unknown error occurred [out#0/mxf @ 00000246dceb9400] video:1878kB audio:0kB subtitle:0kB other streams:0kB global headers:10kB muxing overhead: unknown }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/10395> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#9641(avformat:new): Matroska duplicate tags are only output once instead of repeated
by FFmpeg 08 Mar '24

08 Mar '24

#9641: Matroska duplicate tags are only output once instead of repeated -------------------------------------+------------------------------------- Reporter: Gary Moore | Type: defect Status: new | Priority: normal Component: avformat | Version: Keywords: matroska | unspecified metadata | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- When using ffprobe from the commandline, or calling into ffmpeg using {{{#!div style="font-size: 80%" {{{#!c++ while ((tag=av_dict_get(m_fctx->chapters[i]->metadata, "", tag, AV_DICT_IGNORE_SUFFIX))) }}} }}} if there are duplicate tags, only the last tag and value is returned. The Matroska tag spec (https://www.matroska.org/technical/tagging.html) states that if a tag has multiple values, the tag should be repeated with one value per tag. However, ffmpeg only returns the last tag and value. This prevents extending mka tag support in Kodi (which uses ffmpeg for tag reading) as there can be multiple composers/lyricists etc for individual tracks. This bug is present in v4.4 (current version used by Kodi) and v5.0 using a static build of github master branch from https://johnvansickle.com/ffmpeg/ dated 20220108 {{{#!div style="font-size: 80%" ffprobe output (commandline ffprobe -v 9 -loglevel 99 -i ../music/5.1SurroundSoundTestFilesVariousFormatsAACAC3MP4DTSWAV/mka/Pink\ Floyd\ Live\ at\ Knebworth\ 1990.mka) {{{#!bash ./ffprobe -v 9 -loglevel 99 -i ../music/5.1SurroundSoundTestFilesVariousFormatsAACAC3MP4DTSWAV/mka/Pink\ Floyd\ Live\ at\ Knebworth\ 1990.mka ffprobe version N-60236-gffb000fff8-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2007-2022 the FFmpeg developers built with gcc 8 (Debian 8.3.0-6) configuration: --enable-gpl --enable-version3 --enable-static --disable- debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gmp --enable-libgme --enable-gray --enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libdav1d --enable-libxvid --enable-libzvbi --enable-libzimg libavutil 57. 18.100 / 57. 18.100 libavcodec 59. 20.100 / 59. 20.100 libavformat 59. 17.100 / 59. 17.100 libavdevice 59. 5.100 / 59. 5.100 libavfilter 8. 25.100 / 8. 25.100 libswscale 6. 5.100 / 6. 5.100 libswresample 4. 4.100 / 4. 4.100 libpostproc 56. 4.100 / 56. 4.100 [NULL @ 0x5a771c0] Opening '../music/5.1SurroundSoundTestFilesVariousFormatsAACAC3MP4DTSWAV/mka/Pink Floyd Live at Knebworth 1990.mka' for reading [file @ 0x5a77a80] Setting default whitelist 'file,crypto,data' Probing matroska,webm score:100 size:2048 [matroska,webm @ 0x5a771c0] Format matroska,webm probed with size=2048 and score=100 [matroska,webm @ 0x5a771c0] Unknown entry 0x447B at pos. 2013792645 [matroska,webm @ 0x5a771c0] Unknown entry 0x447B at pos. 2013792741 [matroska,webm @ 0x5a771c0] Unknown entry 0x447B at pos. 2013793267 [matroska,webm @ 0x5a771c0] Unknown entry 0x447B at pos. 2013793369 [matroska,webm @ 0x5a771c0] Unknown entry 0x447B at pos. 2013793535 [matroska,webm @ 0x5a771c0] Unknown entry 0x447B at pos. 2013794075 [matroska,webm @ 0x5a771c0] Unknown entry 0x447B at pos. 2013794240 [matroska,webm @ 0x5a771c0] Unknown entry 0x447B at pos. 2013794483 [matroska,webm @ 0x5a771c0] Unknown entry 0x447B at pos. 2013794666 [matroska,webm @ 0x5a771c0] Unknown entry 0x447B at pos. 2013794841 [matroska,webm @ 0x5a771c0] Unknown entry 0x447B at pos. 2013794962 st:0 removing common factor 32 from timebase [matroska,webm @ 0x5a771c0] Before avformat_find_stream_info() pos: 5977 bytes read:35491 seeks:2 nb_streams:1 [matroska,webm @ 0x5a771c0] All info found [matroska,webm @ 0x5a771c0] stream 0: start_time: 0 duration: NOPTS [matroska,webm @ 0x5a771c0] format: start_time: 0 duration: 3426.7 (estimate from stream) bitrate=4701 kb/s [matroska,webm @ 0x5a771c0] After avformat_find_stream_info() pos: 32664 bytes read:68259 seeks:2 frames:1 Input #0, matroska,webm, from '../music/5.1SurroundSoundTestFilesVariousFormatsAACAC3MP4DTSWAV/mka/Pink Floyd Live at Knebworth 1990.mka': Metadata: creation_time : 2022-02-09T11:24:44.000000Z encoder : libebml v1.3.10 + libmatroska v1.5.2 TITLE : Live at Knebworth 1990 ALBUMARTISTSORT : Pink Floyd ARTIST : Pink Floyd ARTISTSORT : Pink Floyd MUSICBRAINZ_ALBUMARTIST: Pink Floyd MUSICBRAINZ_ALBUMARTISTID: 83d91898-7763-47d7-b03b-b92132375c47 MUSICBRAINZ_ALBUMID: 4f6f7e13-1d87-430e-b2c7-86acf58fe15f MUSICBRAINZ_ARTISTID: 83d91898-7763-47d7-b03b-b92132375c47 MUSICBRAINZ_RELEASEGROUPID: 9c4299b6-7e4a-4879-9fcf-5b15ca10a233 PUBLISHER : Parlophone DATE_RECORDED : 2021 Duration: 00:57:06.70, start: 0.000000, bitrate: 4701 kb/s Chapters: Chapter #0:0: start 0.000000, end 663.663000 Metadata: MUSICBRAINZ_TRACKID: 84e3cf9a-f1f2-49ff-8d8a-8596d57a0a7a COMPOSER : David Gilmour;Roger Waters;Richard Wright INSTRUMENTS : David Gilmour,Guitar,Nick Mason,Drums,Guy Pratt,Bass Guitar,Clare Torry,Backing Vocals,Sam Brown,BackingVocals,Candy Dulfer,Saxaphone,Tim Renwick,Guitar,Richard Wright,Backing vocals,Richard Wright,keyboards LYRICIST : Roger Waters TITLE : Shine On You Crazy Diamond, Parts 1–5 track : 1/7 Chapter #0:1: start 663.663000, end 967.633333 Metadata: MUSICBRAINZ_TRACKID: 3cbc4c9c-bac2-47c3-a4fb-4515efe726c2 COMPOSER : Richard Wright TITLE : The Great Gig in the Sky track : 2/7 Chapter #0:2: start 967.633333, end 1270.060458 Metadata: MUSICBRAINZ_TRACKID: c2e10557-3208-4965-88c6-40c534cc0cfb TITLE : Wish You Were Here track : 3/7 Chapter #0:3: start 1270.060458, end 1840.839000 Metadata: MUSICBRAINZ_TRACKID: b5b91cd2-b0f1-4569-99b5-8ddce4e7c441 TITLE : Sorrow track : 4/7 Chapter #0:4: start 1840.839000, end 2453.159042 Metadata: MUSICBRAINZ_TRACKID: 46725dce-1e11-4f29-a3c1-ce62168204c4 TITLE : Money track : 5/7 Chapter #0:5: start 2453.159042, end 2947.569625 Metadata: MUSICBRAINZ_TRACKID: 366f18f0-c8fb-4a05-89ff-0ce83f1e289f TITLE : Comfortably Numb track : 6/7 Chapter #0:6: start 2947.569625, end 3426.690000 Metadata: MUSICBRAINZ_TRACKID: 28636bbd-b8ec-4cb0-9c3c-4444a4df7eb1 TITLE : Run Like Hell track : 7/7 Stream #0:0(eng), 1, 651/31250000: Audio: dts (DTS-HD MA), 48000 Hz, 5.1(side), s32p (24 bit) Metadata: title : Surround 5.1 BPS-eng : 4699476 DURATION-eng : 00:57:06.699323040 NUMBER_OF_BYTES-eng: 2012961516 NUMBER_OF_FRAMES-eng: 321253 _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES _STATISTICS_WRITING_APP-eng: mkvmerge v45.0.0 ('Heaven in Pennies') 64-bit _STATISTICS_WRITING_DATE_UTC-eng: 2022-02-09 11:24:44 [AVIOContext @ 0x5a7ff00] Statistics: 68259 bytes read, 2 seeks }}} }}} Note that Chapter #0:1 has only one composer tag ``Chapter #0:1: start 663.663000, end 967.633333 Metadata: MUSICBRAINZ_TRACKID: 3cbc4c9c-bac2-47c3-a4fb-4515efe726c2 COMPOSER : Richard Wright TITLE : The Great Gig in the Sky track : 2/7`` Output from `mkvextract tags Pink\ Floyd\ Live\ at\ Knebworth\ 1990.mka > pftags.xml` {{{#!div style="font-size: 80%" {{{#!xml <?xml version="1.0"?>  <Tags> <Tag> <Targets> <TargetTypeValue>50</TargetTypeValue> </Targets> <Simple> <Name>TITLE</Name> <String>Live at Knebworth 1990</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> <TagLanguageIETF>und</TagLanguageIETF> </Simple> <Simple> <Name>ARTIST</Name> <String>Pink Floyd</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> </Tag> <Tag> <Targets> <TargetTypeValue>30</TargetTypeValue> </Targets> <Simple> <Name>ALBUMARTISTSORT</Name> <String>Pink Floyd</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> <TagLanguageIETF>und</TagLanguageIETF> </Simple> <Simple> <Name>ARTIST</Name> <String>Pink Floyd</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>ARTISTSORT</Name> <String>Pink Floyd</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>MUSICBRAINZ_ALBUMARTIST</Name> <String>Pink Floyd</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>MUSICBRAINZ_ALBUMARTISTID</Name> <String>83d91898-7763-47d7-b03b-b92132375c47</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>MUSICBRAINZ_ALBUMID</Name> <String>4f6f7e13-1d87-430e-b2c7-86acf58fe15f</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>MUSICBRAINZ_ARTISTID</Name> <String>83d91898-7763-47d7-b03b-b92132375c47</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>MUSICBRAINZ_RELEASEGROUPID</Name> <String>9c4299b6-7e4a-4879-9fcf-5b15ca10a233</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>PUBLISHER</Name> <String>Parlophone</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> </Tag> <Tag> <Targets> <TargetTypeValue>50</TargetTypeValue> </Targets> <Simple> <Name>DATE_RECORDED</Name> <String>2021</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> <TagLanguageIETF>und</TagLanguageIETF> </Simple> </Tag> <Tag> <Targets> <ChapterUID>1518495949379077925</ChapterUID> <TargetTypeValue>30</TargetTypeValue> </Targets> <Simple> <Name>MUSICBRAINZ_TRACKID</Name> <String>28636bbd-b8ec-4cb0-9c3c-4444a4df7eb1</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> <TagLanguageIETF>und</TagLanguageIETF> </Simple> <Simple> <Name>TITLE</Name> <String>Run Like Hell</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>PART_NUMBER</Name> <String>7/7</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> </Tag> <Tag> <Targets> <ChapterUID>3613098625400000886</ChapterUID> <TargetTypeValue>30</TargetTypeValue> </Targets> <Simple> <Name>COMPOSER</Name> <String>David Gilmour;Roger Waters;Richard Wright</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> <TagLanguageIETF>und</TagLanguageIETF> </Simple> <Simple> <Name>INSTRUMENTS</Name> <String>David Gilmour,Guitar,Nick Mason,Drums,Guy Pratt,Bass Guitar,Clare Torry,Backing Vocals,Sam Brown,BackingVocals,Candy Dulfer,Saxaphone,Tim Renwick,Guitar,Richard Wright,Backing vocals,Richard Wright,keyboards</String> </Simple> <Simple> <Name>LYRICIST</Name> <String>Roger Waters</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>MUSICBRAINZ_TRACKID</Name> <String>84e3cf9a-f1f2-49ff-8d8a-8596d57a0a7a</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>TITLE</Name> <String>Shine On You Crazy Diamond, Parts 1–5</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>PART_NUMBER</Name> <String>1/7</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> </Tag> <Tag> <Targets> <ChapterUID>11822505076461640796</ChapterUID> <TargetTypeValue>30</TargetTypeValue> </Targets> <Simple> <Name>MUSICBRAINZ_TRACKID</Name> <String>b5b91cd2-b0f1-4569-99b5-8ddce4e7c441</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> <TagLanguageIETF>und</TagLanguageIETF> </Simple> <Simple> <Name>TITLE</Name> <String>Sorrow</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>PART_NUMBER</Name> <String>4/7</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> </Tag> <Tag> <Targets> <ChapterUID>12948420648829714117</ChapterUID> <TargetTypeValue>30</TargetTypeValue> </Targets> <Simple> <Name>MUSICBRAINZ_TRACKID</Name> <String>46725dce-1e11-4f29-a3c1-ce62168204c4</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> <TagLanguageIETF>und</TagLanguageIETF> </Simple> <Simple> <Name>TITLE</Name> <String>Money</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>PART_NUMBER</Name> <String>5/7</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> </Tag> <Tag> <Targets> <ChapterUID>14931913620754867571</ChapterUID> <TargetTypeValue>30</TargetTypeValue> </Targets> <Simple> <Name>COMPOSER</Name> <String>Clare Torry</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>COMPOSER</Name> <String>Richard Wright</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>MUSICBRAINZ_TRACKID</Name> <String>3cbc4c9c-bac2-47c3-a4fb-4515efe726c2</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> <TagLanguageIETF>und</TagLanguageIETF> </Simple> <Simple> <Name>TITLE</Name> <String>The Great Gig in the Sky</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>PART_NUMBER</Name> <String>2/7</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> </Tag> <Tag> <Targets> <ChapterUID>16908591664885573413</ChapterUID> <TargetTypeValue>30</TargetTypeValue> </Targets> <Simple> <Name>MUSICBRAINZ_TRACKID</Name> <String>366f18f0-c8fb-4a05-89ff-0ce83f1e289f</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> <TagLanguageIETF>und</TagLanguageIETF> </Simple> <Simple> <Name>TITLE</Name> <String>Comfortably Numb</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>PART_NUMBER</Name> <String>6/7</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> </Tag> <Tag> <Targets> <ChapterUID>17396753124889256807</ChapterUID> <TargetTypeValue>30</TargetTypeValue> </Targets> <Simple> <Name>MUSICBRAINZ_TRACKID</Name> <String>c2e10557-3208-4965-88c6-40c534cc0cfb</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> <TagLanguageIETF>und</TagLanguageIETF> </Simple> <Simple> <Name>TITLE</Name> <String>Wish You Were Here</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> <Simple> <Name>PART_NUMBER</Name> <String>3/7</String> <TagLanguage>und</TagLanguage> <DefaultLanguage>1</DefaultLanguage> </Simple> </Tag> <Tag> <Targets> <TrackUID>3</TrackUID> <TargetTypeValue>50</TargetTypeValue> </Targets> <Simple> <Name>BPS</Name> <String>4699476</String> <TagLanguage>eng</TagLanguage> <TagLanguageIETF>en</TagLanguageIETF> </Simple> <Simple> <Name>DURATION</Name> <String>00:57:06.699323040</String> <TagLanguage>eng</TagLanguage> </Simple> <Simple> <Name>NUMBER_OF_BYTES</Name> <String>2012961516</String> <TagLanguage>eng</TagLanguage> </Simple> <Simple> <Name>NUMBER_OF_FRAMES</Name> <String>321253</String> <TagLanguage>eng</TagLanguage> </Simple> <Simple> <Name>_STATISTICS_TAGS</Name> <String>BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES</String> <TagLanguage>eng</TagLanguage> </Simple> <Simple> <Name>_STATISTICS_WRITING_APP</Name> <String>mkvmerge v45.0.0 ('Heaven in Pennies') 64-bit</String> <TagLanguage>eng</TagLanguage> </Simple> <Simple> <Name>_STATISTICS_WRITING_DATE_UTC</Name> <String>2022-02-09 11:24:44</String> <TagLanguage>eng</TagLanguage> </Simple> </Tag> </Tags> }}} }}} The above shows two composer tags with different values, whereas ffprobe/avformat only shows/returns the last tag and value. If necessary I can supply the original file or I can tag a dummy mka/mkv file with the same tags for testing purposes. -- Ticket URL: <https://trac.ffmpeg.org/ticket/9641> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#10857(avcodec:new): Stream-level side data propagated to frames is indistinguishable from frame-level side data
by FFmpeg 08 Mar '24

08 Mar '24

#10857: Stream-level side data propagated to frames is indistinguishable from frame-level side data -------------------------------------+------------------------------------- Reporter: dbuitenh | Type: defect Status: new | Priority: important Component: avcodec | Version: git- Keywords: avcodec | master sidedata | Blocked By: Blocking: 7.0 | Reproduced by developer: 1 Analyzed by developer: 1 | -------------------------------------+------------------------------------- Summary of the bug: Since ae22271620df90567ba276832b33607d64e9ba9c, stream level side data gets propagated to frames. This causes issues, for example, when both the container and bitstream have the the same type of side data, such as, example, content light level metadata. The issues arises because once the stream/container level side data is propagated to the frame, which already had side data of that type, the frame now has two side data of that type attached to it, with no way of figuring out which came from where. This is made even worse due to the old av_frame_get_side_data API (which is still supported), only being able to return the first of any given side data attached to the frame. After discussing with Anton and James, it was agreed that the solution is to only attach one of each type of side data to a frame, and to prefer frame-level/bitstream-level side data by default, if both exist, so that the user can choose which they prefer to use (if the stream-level was preferred by default, that would mean the default would be to not expose frame-level at all, which would be Bad(TM). There shall be an API to allow the user to prefer one or the other, which requires adding an AVList type to the API, according to Anton's preferences. This blocks 7.0 since it is a regression with no work around. Bug opened per Michael's request. How to reproduce: Call av_frame_get_side_data() on frame(s) from the attached hdr10tags- both.mkv. You can also see it easy like this: {{{ % ffprobe -show_frames -of json hdr10tags-both.mkv [... snip ...] "side_data_list": [ { "side_data_type": "Mastering display metadata", "red_x": "11408507/16777216", "red_y": "5368709/16777216", "green_x": "2222981/8388608", "green_y": "11576279/16777216", "blue_x": "5033165/33554432", "blue_y": "16106127/268435456", "white_point_x": "10492471/33554432", "white_point_y": "689963/2097152", "min_luminance": "5368709/536870912", "max_luminance": "1000/1" }, { "side_data_type": "Content light level metadata", "max_content": 1000, "max_average": 300 }, { "side_data_type": "H.26[45] User Data Unregistered SEI message" }, { "side_data_type": "Mastering display metadata", "red_x": "35400/50000", "red_y": "14599/50000", "green_x": "8500/50000", "green_y": "39850/50000", "blue_x": "6550/50000", "blue_y": "2300/50000", "white_point_x": "15634/50000", "white_point_y": "16450/50000", "min_luminance": "10/10000", "max_luminance": "10000000/10000" } ] }}} Note the multiple indistinguishable side data on the first frame. -- Ticket URL: <https://trac.ffmpeg.org/ticket/10857> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2