October 2014 - FFmpeg-trac - lists.ffmpeg.org

#3692(avcodec:new): dpx samples (possibly broken) look broken with FFmpeg, work fine with ImageMagick
by FFmpeg 07 May '21

07 May '21

#3692: dpx samples (possibly broken) look broken with FFmpeg, work fine with ImageMagick --------------------------------------+--------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: git-master | Keywords: dpx Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 --------------------------------------+--------------------------------- http://www.simplesystems.org/users/bfriesen/dpx/ contains three dpx samples, one (16 bit) looks ugly with FFmpeg, ImageMagick and GraphicsMagick, the other two (8 bit) only look broken with FFmpeg. {{{ $ ffmpeg -i DLAD_8b_1c_big.dpx ffmpeg version N-63624-g4ba8560 Copyright (c) 2000-2014 the FFmpeg developers built on May 31 2014 12:24:49 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 87.100 / 52. 87.100 libavcodec 55. 65.100 / 55. 65.100 libavformat 55. 42.100 / 55. 42.100 libavdevice 55. 13.101 / 55. 13.101 libavfilter 4. 5.100 / 4. 5.100 libswscale 2. 6.100 / 2. 6.100 libswresample 0. 19.100 / 0. 19.100 libpostproc 52. 3.100 / 52. 3.100 Input #0, image2, from 'DLAD_8b_1c_big.dpx': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0: Video: dpx, gray, 255x185 [SAR 1:1 DAR 51:37], 25 tbr, 25 tbn, 25 tbc At least one output file must be specified }}} {{{ $ ffmpeg -i DLAD_8b_3c_big.dpx ffmpeg version N-63624-g4ba8560 Copyright (c) 2000-2014 the FFmpeg developers built on May 31 2014 12:24:49 with gcc 4.7 (SUSE Linux) configuration: --enable-gpl libavutil 52. 87.100 / 52. 87.100 libavcodec 55. 65.100 / 55. 65.100 libavformat 55. 42.100 / 55. 42.100 libavdevice 55. 13.101 / 55. 13.101 libavfilter 4. 5.100 / 4. 5.100 libswscale 2. 6.100 / 2. 6.100 libswresample 0. 19.100 / 0. 19.100 libpostproc 52. 3.100 / 52. 3.100 Input #0, image2, from 'DLAD_8b_3c_big.dpx': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0: Video: dpx, rgb24, 255x185 [SAR 1:1 DAR 51:37], 25 tbr, 25 tbn, 25 tbc At least one output file must be specified }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/3692> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#3785(undetermined:new): SWSCALE: in_range, in_color_matrix, out_range, out_color_matrix incorrect
by FFmpeg 24 Apr '21

24 Apr '21

#3785: SWSCALE: in_range, in_color_matrix, out_range, out_color_matrix incorrect -------------------------------------+------------------------------------- Reporter: troy_s | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: | Blocked By: colormanagement colorspace 709 | Reproduced by developer: 0 601 | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- '''Summary of the bug''': Seems that swscale is still sadly mangling RGB to YCbCr and vice versa transforms. Disabled all ASM speedups to avoid code path issues, as were previously hard coded to 601 coefficents etc. '''How to reproduce''': Encode a test chart and check values. Test chart available from http://www .belle-nuit.com/test-chart. '''Expected versus Results''': BT.709 and sRGB share identical luminance coefficients. An sRGB image, encoded at full range using BT.709 primaries should decode to a perfect 1:1 regarding RGB values, compression notwithstanding. Sampling the upper row of colors using the provided test chart, we can see some issues with the encoding / decoding step, when using FFPLAY with the corresponding scale commands. For example, an encode using {{{ ./ffmpeg -loop 1 -i ~/Downloads/testchart.tif -t 3 -c:v h264 -vf "scale=in_range=full:in_color_matrix=bt709:out_range=full:out_color_matrix=bt709" out709-full.mp4 }}} Should produce a perfect 1:1 when played back with {{{ ./ffplay -vf "scale=in_range=full:in_color_matrix=bt709:out_range=full:out_color_matrix=bt709" out709-full.mp4 }}} When we sample the sRGB / 709 values using an image editor, the top row should result in RGB values as follows: {{{ Name R G B Yellow: 180 180 16 Cyan: 16 180 180 Magenta: 180 16 180 Green: 16 180 16 Red: 180 16 16 Blue: 16 16 180 }}} Given that 709 and sRGB share identical primaries, and broadcast scaling is set to full range, there should be a perfect 1:1 result with the values. However, what we find with playback via the ffmpeg command set with proper values is: {{{ Name R G B Yellow: 179 190 22 Cyan: 31 197 180 Magenta: 167 0 176 Green: 30 209 21 Red: 166 0 19 Blue: 17 5 173 }}} There appears to be breakage with regard to the application of the coefficients, as well as possibly misinterpretation of the full range settings. The are some transforms that yield vaguely close values. However, these suffer from quantization issues where no such should occur. It would seem that all transformations are likely being performed at the relative bit depth for performance. Sadly, this corrupts the values quite significantly. {{{ ./ffmpeg -loop 1 -i ~/Downloads/testchart.tif -t 3 -c:v h264 -vf "scale=in_range=full:in_color_matrix=bt601:out_range=full:out_color_matrix=bt601" out601-full.mp4 }}} The following, despite being 601 coefficients, should yield perfect 1:1 with RGB values (RGB being a relative color space) but quantization issues again result. {{{ ./ffplay -vf "scale=in_range=full:in_color_matrix=bt601:out_range=full:out_color_matrix=bt601" out601-full.mp4 }}} Further testing of the in_range and out_range specifics will be conducted when the basic color coefficients issue is corrected. '''Conclusion''': Some mangling is still present in the color handling in FFMPEG. Quantization issues can likely be expected until a float (likely non- realtime) option is introduced for higher quality frame by frame encoding / decoding. However, even with quantization issues, the encoding / decoding coefficients are not responding / respected in correct fashion for 709 to 709 (1:1 with sRGB content). -- Ticket URL: <https://trac.ffmpeg.org/ticket/3785> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 30

#3794(swscale:new): SWSCALE: Quantization Errors in Y Studio Range
by FFmpeg 19 Apr '21

19 Apr '21

#3794: SWSCALE: Quantization Errors in Y Studio Range ------------------------------------+-------------------------------------- Reporter: troy_s | Type: defect Status: new | Priority: normal Component: swscale | Version: git-master Keywords: 709 Y luma | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+-------------------------------------- Summary of the bug: It appears FFMPEG has some +/- single unit quantization errors in the YCbCr transform. How to reproduce: Generate a raw YCbCr image and diff against theoretically correct values. {{{ ./ffmpeg -i ~/Documents/FFMPEG\ Color\ Research/ARIB_STD-B28.png -pix_fmt yuv444p -vcodec rawvideo -f rawvideo -vf scale="in_range=full:in_color_matrix=bt709:out_range=full:out_color_matrix=bt709" test.yuv ffmpeg version N-64815-gb53bdae Copyright (c) 2000-2014 the FFmpeg developers built on Jul 19 2014 16:33:49 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1) configuration: --enable-gpl --enable-libx264 --disable-asm libavutil 52. 92.101 / 52. 92.101 libavcodec 55. 69.100 / 55. 69.100 libavformat 55. 48.101 / 55. 48.101 libavdevice 55. 13.102 / 55. 13.102 libavfilter 4. 11.102 / 4. 11.102 libswscale 2. 6.100 / 2. 6.100 libswresample 0. 19.100 / 0. 19.100 libpostproc 52. 3.100 / 52. 3.100 Input #0, image2, from '/home/aphorism/Documents/FFMPEG Color Research/ARIB_STD-B28.png': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0: Video: png, rgb24, 1920x1080 [SAR 2835:2835 DAR 16:9], 25 tbr, 25 tbn, 25 tbc Output #0, rawvideo, to 'test.yuv': Metadata: encoder : Lavf55.48.101 Stream #0:0: Video: rawvideo (444P / 0x50343434), yuv444p, 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 25 fps, 25 tbn, 25 tbc Metadata: encoder : Lavc55.69.100 rawvideo Stream mapping: Stream #0:0 -> #0:0 (png (native) -> rawvideo (native)) Press [q] to stop, [?] for help frame= 1 fps=0.0 q=0.0 Lsize= 6075kB time=00:00:00.04 bitrate=1244160.0kbits/s video:6075kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000% }}} Diff'd versions of the theoretically ideal values versus FFMPEG's output. Lowest red stripe is due to theoretical version preserving the -2% patch, and not relevant. -- Ticket URL: <https://trac.ffmpeg.org/ticket/3794> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 16

#3623(undetermined:new): Mixed results writing M4A metadata
by FFmpeg 15 Apr '21

15 Apr '21

#3623: Mixed results writing M4A metadata -------------------------------------+------------------------------------- Reporter: svnpenn | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Given this file http://bitbucket.org/svnpenn/a/downloads/superuser.mp4 I am having mixed results writing metadata. For example these commands {{{ ffmpeg -i superuser.mp4 -c copy good.aac ffmpeg -i good.aac -c copy -bsf aac_adtstoasc -metadata title=Confetti \ -movflags faststart good.m4a }}} Will generate an M4A file that plays correctly with metadata that is recognized. However this command {{{ ffmpeg -i superuser.mp4 -c copy -vn -movflags faststart \ -metadata title=Confetti bad.m4a }}} Generates a file that plays correctly, but my player does not recognize the metadata. Note I also tried adding `-bsf aac_adtstoasc` to the bad command to no avail. How can I tweak the second command to get it working? Command-line output http://gist.github.com/svnpenn/82e7f7685084759c7483 Source question http://superuser.com/q/750627 -- Ticket URL: <https://trac.ffmpeg.org/ticket/3623> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 17

#3586(avcodec:new): [discrepancy with libav] avcodec_encode_video2 merges packet side data with the packet body
by FFmpeg 10 Apr '21

10 Apr '21

#3586: [discrepancy with libav] avcodec_encode_video2 merges packet side data with the packet body -------------------------------------+------------------------------------- Reporter: Lastique | Type: defect Status: new | Priority: normal Component: avcodec | Version: 2.2.1 Keywords: libav | Blocked By: avcodec_encode_video2 avpacket | Reproduced by developer: 0 av_packet_merge_side_data | Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- We have an application which uses ffmpeg to encode video in h263. The application requests h263_mb_info side data by setting the "mb_info" option on the encoder context: {{{ av_opt_set_int(av_ctx, "mb_info", 1400, AV_OPT_SEARCH_CHILDREN) }}} Later we call avcodec_encode_video2() to encode frames. The problem is that ffmpeg avcodec_encode_video2() returns AVPackets with the encoded frame and some amount of junk at the end. From the source code I can see that the junk is actually the encoded side data (mb_info) appended to the h263 packet by av_packet_merge_side_data() which is called by avcodec_encode_video2(). This appended side data prevents the packets from being decoded by ffmpeg 2.2.1 (I tried both decoding through the API and ffplay). Decoding results in many messages such as: {{{ slice end not reached but screenspace end (399 left 019CE3, score= -7) concealing 88 DC, 88 AC, 88 MV errors in P frame }}} and corrupted image. This is also different from libav behavior. At least 9.x and 10.x versions don't merge side data into the packet body, and when using libav we don't have the decoding problem. Looking at the libavcodec code I don't really understand why the call to av_packet_merge_side_data() is needed. Side data, at least mb_info in case of h263, is not the part of the encoded media and thus should not be part of the packet body. Since the packet size (AVPacket::size) includes the appended side data, there is no way to obtain the size of the actual media. I suspect, av_packet_split_side_data() can be used to restore the original un-merged packet, but (a) it is not documented and (b) doing av_packet_merge_side_data() and av_packet_split_side_data() is a waste of memory and CPU (note: we pre-allocate packet data buffer to optimize performance). Therefore my preferred solution would be to remove the call to av_packet_merge_side_data() from avcodec_encode_video2(). If that call cannot be removed then what is the correct way to obtain the actual media from the merged packet? -- Ticket URL: <https://trac.ffmpeg.org/ticket/3586> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 11

#3516(undetermined:new): mjpeg: wrong colors (CMYK with subsampling)
by FFmpeg 22 Mar '21

22 Mar '21

#3516: mjpeg: wrong colors (CMYK with subsampling) -------------------------------------+------------------------------------- Reporter: ami_stuff | Owner: Type: defect | Status: new Priority: normal | Component: Version: | undetermined unspecified | Keywords: Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 -------------------------------------+------------------------------------- attached file decodes with wrong colors {{{ C:\>ffmpeg3 -i YCbCrK.jpg out.bmp ffmpeg version 2.2.git-0f714ab Copyright (c) 2000-2014 the FFmpeg developers built on Mar 31 2014 22:26:54 with gcc 4.6.2 (GCC) configuration: --disable-ffprobe --disable-pthreads --enable-gpl libavutil 52. 70.100 / 52. 70.100 libavcodec 55. 55.106 / 55. 55.106 libavformat 55. 36.100 / 55. 36.100 libavdevice 55. 11.100 / 55. 11.100 libavfilter 4. 3.100 / 4. 3.100 libswscale 2. 5.102 / 2. 5.102 libswresample 0. 18.100 / 0. 18.100 libpostproc 52. 3.100 / 52. 3.100 [mjpeg @ 01d76580] Warning: not compiled with thread support, using thread emula tion Input #0, image2, from 'YCbCrK.jpg': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0: Video: mjpeg, yuva420p(pc), 1024x768, 25 tbr, 25 tbn, 25 tbc [bmp @ 01d78c00] Warning: not compiled with thread support, using thread emulati on [mjpeg @ 01d76580] Warning: not compiled with thread support, using thread emula tion Output #0, image2, to 'out.bmp': Metadata: encoder : Lavf55.36.100 Stream #0:0: Video: bmp, bgra, 1024x768, q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (mjpeg -> bmp) Press [q] to stop, [?] for help frame= 1 fps=0.0 q=0.0 Lsize=N/A time=00:00:00.04 bitrate=N/A video:3072kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 586396112781312.000000% }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/3516> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#3424(avcodec:new): JPEG Decoder fails to decode valid jpeg file (all other major implementations work)
by FFmpeg 22 Mar '21

22 Mar '21

#3424: JPEG Decoder fails to decode valid jpeg file (all other major implementations work) --------------------------------------+--------------------------------- Reporter: dbuitenh | Owner: Type: defect | Status: new Priority: normal | Component: avcodec Version: git-master | Keywords: jpeg Blocked By: | Blocking: Reproduced by developer: 0 | Analyzed by developer: 0 --------------------------------------+--------------------------------- How to reproduce: $ ffmpeg -loglevel debug -i bug.jpg decoded.png git HEAD has the same issue and output. Output: {{{ ffmpeg version N-60776-gd089e9a Copyright (c) 2000-2014 the FFmpeg developers built on Feb 20 2014 11:17:04 with gcc 4.4.7 (GCC) 20120313 (Red Hat 4.4.7-3) configuration: --enable-gpl --enable-version3 --enable-nonfree --disable-decoder=dirac --enable-libopencore-amrnb --enable-libopencore- amrwb --disable-decoder=amrnb --disable-decoder=amrwb --enable-libopus --enable-libx264 --enable-libschroedinger --disable-static --enable-shared --disable-ffplay --disable-ffserver --enable-libfdk-aac --enable-libspeex --enable-avresample --enable-openssl --enable-pic libavutil 52. 65.100 / 52. 65.100 libavcodec 55. 52.102 / 55. 52.102 libavformat 55. 33.100 / 55. 33.100 libavdevice 55. 10.100 / 55. 10.100 libavfilter 4. 1.103 / 4. 1.103 libavresample 1. 1. 0 / 1. 1. 0 libswscale 2. 5.101 / 2. 5.101 libswresample 0. 17.104 / 0. 17.104 libpostproc 52. 3.100 / 52. 3.100 Splitting the commandline. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'. Reading option '-i' ... matched as input file with argument 'bug.jpg'. Reading option 'decoded.png' ... matched as output file. Finished splitting the commandline. Parsing a group of options: global . Applying option loglevel (set logging level) with argument debug. Successfully parsed a group of options. Parsing a group of options: input file bug.jpg. Successfully parsed a group of options. Opening an input file: bug.jpg. [AVIOContext @ 0x23bcdc0] Statistics: 1129716 bytes read, 0 seeks [mjpeg @ 0x23bb060] marker=d8 avail_size_in_buf=1129714 [mjpeg @ 0x23bb060] marker parser used 0 bytes (0 bits) [mjpeg @ 0x23bb060] marker=e0 avail_size_in_buf=1129712 [mjpeg @ 0x23bb060] marker parser used 16 bytes (128 bits) [mjpeg @ 0x23bb060] marker=ee avail_size_in_buf=1129694 [mjpeg @ 0x23bb060] marker parser used 14 bytes (112 bits) [mjpeg @ 0x23bb060] marker=e1 avail_size_in_buf=1129678 [mjpeg @ 0x23bb060] marker parser used 6005 bytes (48040 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=1123670 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=1058133 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=992596 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=927059 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=861522 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=795985 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=730448 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=664911 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=599374 [mjpeg @ 0x23bb060] marker parser used 33031 bytes (264248 bits) [mjpeg @ 0x23bb060] marker=ed avail_size_in_buf=566340 [mjpeg @ 0x23bb060] marker parser used 43 bytes (344 bits) [mjpeg @ 0x23bb060] marker=e1 avail_size_in_buf=566294 [mjpeg @ 0x23bb060] marker parser used 3898 bytes (31184 bits) [mjpeg @ 0x23bb060] marker=db avail_size_in_buf=562393 [mjpeg @ 0x23bb060] index=0 [mjpeg @ 0x23bb060] qscale[0]: 2 [mjpeg @ 0x23bb060] marker parser used 67 bytes (536 bits) [mjpeg @ 0x23bb060] marker=c0 avail_size_in_buf=562324 [mjpeg @ 0x23bb060] sof0: picture: 1280x720 [mjpeg @ 0x23bb060] component 0 1:1 id: 66 quant:0 [mjpeg @ 0x23bb060] component 1 1:1 id: 76 quant:0 [mjpeg @ 0x23bb060] component 2 1:1 id: 88 quant:0 [mjpeg @ 0x23bb060] component 3 1:1 id: 74 quant:0 [mjpeg @ 0x23bb060] pix fmt id 11111111 [mjpeg @ 0x23bb060] marker parser used 20 bytes (160 bits) [mjpeg @ 0x23bb060] marker=c4 avail_size_in_buf=562302 [mjpeg @ 0x23bb060] class=0 index=0 nb_codes=10 [mjpeg @ 0x23bb060] marker parser used 29 bytes (232 bits) [mjpeg @ 0x23bb060] marker=c4 avail_size_in_buf=562271 [mjpeg @ 0x23bb060] class=1 index=0 nb_codes=242 [mjpeg @ 0x23bb060] marker parser used 78 bytes (624 bits) [mjpeg @ 0x23bb060] escaping removed 1699 bytes [mjpeg @ 0x23bb060] marker=da avail_size_in_buf=562191 [mjpeg @ 0x23bb060] component: 66 [mjpeg @ 0x23bb060] component: 76 [mjpeg @ 0x23bb060] component: 88 [mjpeg @ 0x23bb060] component: 74 [mjpeg @ 0x23bb060] marker parser used 560491 bytes (4483924 bits) [mjpeg @ 0x23bb060] marker=d9 avail_size_in_buf=0 [mjpeg @ 0x23bb060] decode frame unused 0 bytes Input #0, image2, from 'bug.jpg': Duration: 00:00:00.04, start: 0.000000, bitrate: N/A Stream #0:0, 1, 1/25: Video: mjpeg, yuva444p(pc), 1280x720 [SAR 300:300 DAR 16:9], 1/25, 25 tbr, 25 tbn, 25 tbc Successfully opened the file. Parsing a group of options: output file decoded.png. Successfully parsed a group of options. Opening an output file: decoded.png. Successfully opened the file. detected 24 logical cores [graph 0 input from stream 0:0 @ 0x23a4760] Setting 'video_size' to value '1280x720' [graph 0 input from stream 0:0 @ 0x23a4760] Setting 'pix_fmt' to value '299' [graph 0 input from stream 0:0 @ 0x23a4760] Setting 'time_base' to value '1/25' [graph 0 input from stream 0:0 @ 0x23a4760] Setting 'pixel_aspect' to value '300/300' [graph 0 input from stream 0:0 @ 0x23a4760] Setting 'sws_param' to value 'flags=2' [graph 0 input from stream 0:0 @ 0x23a4760] Setting 'frame_rate' to value '25/1' [graph 0 input from stream 0:0 @ 0x23a4760] w:1280 h:720 pixfmt:yuva444p tb:1/25 fr:25/1 sar:300/300 sws_param:flags=2 [format @ 0x23a49c0] compat: called with args=[rgb24|rgba|rgb48be|rgba64be|pal8|gray|gray8a|gray16be|monob] [format @ 0x23a49c0] Setting 'pix_fmts' to value 'rgb24|rgba|rgb48be|rgba64be|pal8|gray|gray8a|gray16be|monob' [auto-inserted scaler 0 @ 0x23a5c80] Setting 'flags' to value '0x4' [auto-inserted scaler 0 @ 0x23a5c80] w:iw h:ih flags:'0x4' interl:0 [format @ 0x23a49c0] auto-inserting filter 'auto-inserted scaler 0' between the filter 'Parsed_null_0' and the filter 'format' [AVFilterGraph @ 0x23be4a0] query_formats: 4 queried, 2 merged, 1 already done, 0 delayed [auto-inserted scaler 0 @ 0x23a5c80] picking rgba out of 8 ref:yuva444p alpha:1 [swscaler @ 0x23ab020] Forcing full internal H chroma due to input having non subsampled chroma [auto-inserted scaler 0 @ 0x23a5c80] w:1280 h:720 fmt:yuva444p sar:300/300 -> w:1280 h:720 fmt:rgba sar:1/1 flags:0x4 Output #0, image2, to 'decoded.png': Metadata: encoder : Lavf55.33.100 Stream #0:0, 0, 1/90000: Video: png, rgba, 1280x720 [SAR 1:1 DAR 16:9], 1/25, q=2-31, 200 kb/s, 90k tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (mjpeg -> png) Press [q] to stop, [?] for help [mjpeg @ 0x23bb060] marker=d8 avail_size_in_buf=1129714 [mjpeg @ 0x23bb060] marker parser used 0 bytes (0 bits) [mjpeg @ 0x23bb060] marker=e0 avail_size_in_buf=1129712 [mjpeg @ 0x23bb060] marker parser used 16 bytes (128 bits) [mjpeg @ 0x23bb060] marker=ee avail_size_in_buf=1129694 [mjpeg @ 0x23bb060] marker parser used 14 bytes (112 bits) [mjpeg @ 0x23bb060] marker=e1 avail_size_in_buf=1129678 [mjpeg @ 0x23bb060] marker parser used 6005 bytes (48040 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=1123670 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=1058133 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=992596 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=927059 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=861522 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=795985 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=730448 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=664911 [mjpeg @ 0x23bb060] marker parser used 65534 bytes (524272 bits) [mjpeg @ 0x23bb060] marker=e2 avail_size_in_buf=599374 [mjpeg @ 0x23bb060] marker parser used 33031 bytes (264248 bits) [mjpeg @ 0x23bb060] marker=ed avail_size_in_buf=566340 [mjpeg @ 0x23bb060] marker parser used 43 bytes (344 bits) [mjpeg @ 0x23bb060] marker=e1 avail_size_in_buf=566294 [mjpeg @ 0x23bb060] marker parser used 3898 bytes (31184 bits) [mjpeg @ 0x23bb060] marker=db avail_size_in_buf=562393 [mjpeg @ 0x23bb060] index=0 [mjpeg @ 0x23bb060] qscale[0]: 2 [mjpeg @ 0x23bb060] marker parser used 67 bytes (536 bits) [mjpeg @ 0x23bb060] marker=c0 avail_size_in_buf=562324 [mjpeg @ 0x23bb060] sof0: picture: 1280x720 [mjpeg @ 0x23bb060] component 0 1:1 id: 66 quant:0 [mjpeg @ 0x23bb060] component 1 1:1 id: 76 quant:0 [mjpeg @ 0x23bb060] component 2 1:1 id: 88 quant:0 [mjpeg @ 0x23bb060] component 3 1:1 id: 74 quant:0 [mjpeg @ 0x23bb060] pix fmt id 11111111 [mjpeg @ 0x23bb060] marker parser used 20 bytes (160 bits) [mjpeg @ 0x23bb060] marker=c4 avail_size_in_buf=562302 [mjpeg @ 0x23bb060] class=0 index=0 nb_codes=10 [mjpeg @ 0x23bb060] marker parser used 29 bytes (232 bits) [mjpeg @ 0x23bb060] marker=c4 avail_size_in_buf=562271 [mjpeg @ 0x23bb060] class=1 index=0 nb_codes=242 [mjpeg @ 0x23bb060] marker parser used 78 bytes (624 bits) [mjpeg @ 0x23bb060] escaping removed 1699 bytes [mjpeg @ 0x23bb060] marker=da avail_size_in_buf=562191 [mjpeg @ 0x23bb060] component: 66 [mjpeg @ 0x23bb060] component: 76 [mjpeg @ 0x23bb060] component: 88 [mjpeg @ 0x23bb060] component: 74 [mjpeg @ 0x23bb060] marker parser used 560491 bytes (4483924 bits) [mjpeg @ 0x23bb060] marker=d9 avail_size_in_buf=0 [mjpeg @ 0x23bb060] decode frame unused 0 bytes [output stream 0:0 @ 0x23a4e60] EOF on sink link output stream 0:0:default. No more output streams to write to, finishing. [AVIOContext @ 0x240ec20] Statistics: 0 seeks, 50 writeouts frame= 1 fps=0.0 q=0.0 Lsize=N/A time=00:00:00.04 bitrate=N/A video:1569kB audio:0kB subtitle:0 data:0 global headers:0kB muxing overhead -100.001370% 1 frames successfully decoded, 0 decoding errors }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/3424> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 24

#3566(undetermined:new): trouble reading primative mpeg-ps stream in an mp4 container
by FFmpeg 14 Feb '21

14 Feb '21

#3566: trouble reading primative mpeg-ps stream in an mp4 container -------------------------------------+------------------------------------- Reporter: jon.lee | Type: Status: new | enhancement Component: | Priority: normal undetermined | Version: Keywords: | unspecified Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Summary of the bug: I have some security camera video content that ffmpeg can't read the header data in properly. I also have the propriety player but dont have a way to get any further stream info out. I can upload a small sample and the player if that's any help? How to reproduce: {{{ % ffmpeg -i input ... output ffmpeg version built on ... }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/3566> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 8

#3729(undetermined:new): FFMPEG should show warnings when FLAC encoder produce non-subset stream
by FFmpeg 14 Feb '21

14 Feb '21

#3729: FFMPEG should show warnings when FLAC encoder produce non-subset stream -------------------------------------+------------------------------------- Reporter: Vika | Type: defect Apelsinova | Priority: normal Status: new | Version: git- Component: | master undetermined | Blocked By: Keywords: flac subset | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- FFMPEG should show warning message "The encoding parameters specified do not conform to the FLAC Subset and may not be streamable or playable in hardware devices." when one of the following statements is true: 1. sample size in bits = not (8 or 12 or 16 or 20 or 24) or 2. min_partition_order > 8 or 3. max_partition_order > 8 or 4. min_prediction_order > 12 and samplerate <= 48000 or 5. max_prediction_order > 12 and samplerate <= 48000 or 6. frame_size > 4608 and samplerate <= 48000 or 7. frame_size > 16384 -- Ticket URL: <https://trac.ffmpeg.org/ticket/3729> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 8

#3657(swscale:new): 32 Bit per Channel sws conversion
by FFmpeg 11 Feb '21

11 Feb '21

#3657: 32 Bit per Channel sws conversion ---------------------------------+--------------------------------------- Reporter: sun | Type: enhancement Status: new | Priority: wish Component: swscale | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+--------------------------------------- Hello, As there are more and more Cameras able to record with more than 8 bit per pixel and there already are programs like Shotcut and Blender which support high-precision internal processing, e.g. blender is unable to handle 10-bit videos properly, because converting a 16 bit buffer from the sws yuv to rgb conversion to its internal 32bit buffer would be too slow and therefore it has to use an 8 bit buffer. If ffmpeg could convert to 32bit directly, there wouldn't be the need to do two conversion steps, 10 ->16->32 and native high precision video support would be much easier to implement! -- Ticket URL: <https://trac.ffmpeg.org/ticket/3657> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 17