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

#6860(avformat:new): hvc1 instead of hev1 in FourCC
by FFmpeg 12 Aug '19

12 Aug '19

#6860: hvc1 instead of hev1 in FourCC -------------------------------------+------------------------------------- Reporter: AlexisMay | Type: Status: new | enhancement Component: avformat | Priority: wish Keywords: HEVC, Mac, | Version: git- macOS 10.13, | master Blocking: | Blocked By: Analyzed by developer: 0 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: {{{ % ffmpeg -i input -c:v hevc_videotoolbox output.mp4 produces file with Codec ID(FourCC) hev1 which is unplayable in default Quicktime player on macOS 10.13. Changing Codec ID to hvc1 in hex editor fixes the issue. Can you please output by default hevc files with Codec ID hvc1? -- Ticket URL: <https://trac.ffmpeg.org/ticket/6860> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#8075(undetermined:new): ability to play video successfully depends on encoding fps
by FFmpeg 12 Aug '19

12 Aug '19

#8075: ability to play video successfully depends on encoding fps -------------------------------------+------------------------------------- Reporter: andromodon | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: fps | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Hello. I am using the latest master branch ffmpeg (faa9cd312f02cec5f74658319d1119fcaa7f9088) and this vlc on an ubuntu 18.04 machine: VLC media player 3.0.7.1 Vetinari (revision 3.0.7.1-0-gf3940db4af) VLC version 3.0.7.1 Vetinari (3.0.7.1-0-gf3940db4af) I configured ffmpeg with the --enable-gpl --enable-libx264 options before running "make". The issue is that sometimes when I'm viewing a video with vlc that was encoded by ffmpeg, I only see the first frame and get these playback errors: [andromodon@yogie bin]$ vlc fcounter_6fps.avi VLC media player 3.0.7.1 Vetinari (revision 3.0.7.1-0-gf3940db4af) [000055e6c6702570] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 [00007f3c60c04be0] avcodec decoder: Using Intel i965 driver for Intel(R) Haswell Mobile - 2.1.0 for hardware decoding [00007f3c60c04be0] main decoder error: buffer deadlock prevented [00007f3c60c04be0] avcodec decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) [00007f3c60c04be0] avcodec decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) [00007f3c60c04be0] avcodec decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) [00007f3c60c04be0] avcodec decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) [00007f3c60c04be0] avcodec decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) [00007f3c60c04be0] avcodec decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) [00007f3c60c04be0] avcodec decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) [00007f3c60c04be0] avcodec decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) [00007f3c60c04be0] avcodec decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) [00007f3c60c04be0] avcodec decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) [00007f3c60c04be0] avcodec decoder error: more than 5 seconds of late video -> dropping frame (computer too slow ?) How to reproduce the issue: Download this example video file: https://drive.google.com/open?id=1YQ85A_m1HJTvTqITkg0rKRkselCwiHCu cd to that directory. Run this command: for fps in {5..6}; do echo "$fps"; time './ffmpeg' -y -r "$fps" -i FCounter.mp4 -c:v libx264 -crf 40 fcounter_"$fps"fps.avi; done Then, view fcounter_5fps.avi and fcoutner_6fps.avi with that vlc version, and you'll see that while 5 plays just fine, 6 doesn't. Just the first frame is shown for fcoutner_6fps.avi, and then the errors start scrolling. I've tried this experiment with fps as integers between 1 and 30, and it seems that 1-5fps and 9-30fps works fine, but 6-8fps does not. I'm also attaching the two logs, one from -r 5 and the later one from -r 6. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8075> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#7464(undetermined:new): Videotollbox hardware acceleration method double displayed on macOS
by FFmpeg 11 Aug '19

11 Aug '19

#7464: Videotollbox hardware acceleration method double displayed on macOS -------------------------------------+------------------------------------- Reporter: Sami32 | Type: Status: new | enhancement Component: | Priority: minor undetermined | Version: git- Keywords: hwaccels | master videotollbox macOS | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: I was able to reproduce it on macOS 64-bit using the latest Zeranoe build the `-hwaccels` display 2 times "videotoolbox" hardware acceleration method. How to reproduce: {{{ % ffmpeg -hwaccels ... libavutil 56. 18.100 / 56. 18.100 libavcodec 58. 19.101 / 58. 19.101 libavformat 58. 13.101 / 58. 13.101 libavdevice 58. 4.100 / 58. 4.100 libavfilter 7. 21.100 / 7. 21.100 libswscale 5. 2.100 / 5. 2.100 libswresample 3. 2.100 / 3. 2.100 libpostproc 55. 2.100 / 55. 2.100 Hardware acceleration methods: videotoolbox videotoolbox }}} See the user report: https://github.com/UniversalMediaServer/UniversalMediaServer/issues/1592 -- Ticket URL: <https://trac.ffmpeg.org/ticket/7464> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#7985(undetermined:new): undefined-behavior at libavcodec/vc2enc_dwt.c:69
by FFmpeg 10 Aug '19

10 Aug '19

#7985: undefined-behavior at libavcodec/vc2enc_dwt.c:69 -------------------------------------+------------------------------------- Reporter: Suhwan | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: vc2enc_dwt | Blocked By: ubsan | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: There's an undefined-behavior at libavcodec/vc2enc_dwt.c:69:34 How to reproduce: {{{ % ffmpeg_g -y -r 74 -i tmp.tiff -map 0 -c:a mpeg1video -c:v vc2 -disposition:a pgm -disposition:a flv -vframes 46 -r 3 -ab 731 -ar 22050 -b:v 716k tmp_.adx ffmpeg version N-94149-g50e194e6e1 Copyright (c) 2000-2019 the FFmpeg developers built with clang version 9.0.0 (https://github.com/llvm/llvm-project.git 442a120567a4bc6c59bc754f9edabfb770086f36) }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/7985> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#8071(avcodec:new): Integer overflow in bitrate / libx264 encoding
by FFmpeg 10 Aug '19

10 Aug '19

#8071: Integer overflow in bitrate / libx264 encoding ---------------------------------+---------------------------------- Reporter: jonfryd | Type: defect Status: new | Priority: normal Component: avcodec | Version: 4.1.4 Keywords: libx264 | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+---------------------------------- Summary of the bug: There seems to be a 32 bit integer overflow / conversion issue in how the video bitrate parameter is being handled by libx264 (I have tested a few other encoders and they seem to be fine). Notice how a bitrate of 3 gb/s gets interpreted as "-1294967 kb/s" in the example below. FFmpeg also displays a warning "The bitrate parameter is set too low" which is nice and how I initially detected the problem. Bonus info: the same example works fine in version 4.1. How to reproduce: {{{ % ffmpeg -f lavfi -i life -c:v libx264 -vb 3G test.mov ffmpeg version 4.1.4-0york3~18.04 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1) configuration: --prefix=/usr --extra-version='0york3~18.04' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable- libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable- libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable- libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable- libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-nonfree --enable-libfdk-aac --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared 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, lavfi, from 'life': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo (B0W1 / 0x31573042), monob, 320x240 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (libx264)) Press [q] to stop, [?] for help [swscaler @ 0x556dfb947740] deprecated pixel format used, make sure you did set range correctly [libx264 @ 0x556dfb936e00] using SAR=1/1 [libx264 @ 0x556dfb936e00] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2 [libx264 @ 0x556dfb936e00] profile High 4:4:4 Predictive, level 6.2, 4:4:4 8-bit [libx264 @ 0x556dfb936e00] 264 - core 155 r2917 0a84d98 - H.264/MPEG-4 AVC codec - Copyleft 2003-2018 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x1:0x111 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=4 threads=7 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=2000000 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00 The bitrate parameter is set too low. It takes bits/s as argument, not kbits/s Output #0, mov, to 'test.mov': Metadata: encoder : Lavf58.20.100 Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuvj444p(pc), 320x240 [SAR 1:1 DAR 4:3], q=-1--1, -1294967 kb/s, 25 fps, 12800 tbn, 25 tbc Metadata: encoder : Lavc58.35.100 libx264 Side data: cpb: bitrate max/min/avg: 0/0/-1294967296 buffer size: 0 vbv_delay: -1 frame= 841 fps=575 q=-1.0 Lsize= 16868kB time=00:00:33.52 bitrate=4122.5kbits/s speed=22.9x }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/8071> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#6673(avformat:new): fmp4/hls not working with remote paths
by FFmpeg 10 Aug '19

10 Aug '19

#6673: fmp4/hls not working with remote paths -------------------------------------+------------------------------------- Reporter: | Type: defect thecodeassassin | Priority: normal Status: new | Version: git- Component: avformat | master Keywords: fmp4 hls | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: When sending the chunks via the HTTP PUT method the init.mp4 file is not created on the remote path. When supplying a init.mp4 manually in the playlist the manifest does not play anywhere. This could be due to the init.mp4 being incorrect or because of something else. Is the init.mp4 stream specific or is it possible to generate a generic one? How to reproduce: {{{ % ffmpeg -i bbb.avi -loglevel warning \ -hls_fmp4_init_filename init.mp4 -c:a aac -b:a 128k -ar 44100 -c:v libx264 -max_muxing_queue_size 400 -x264opts no-scenecut -force_key_frames "expr:gte(t,n_forced*2)" -crf 23 -start_number 0 -hls_time 4 -hls_list_size 3 -use_localtime 1 -hls_segment_type fmp4 -hls_segment_filename "${REMOTE_PATH}/segment_%s.m4s" -preset ultrafast -profile:v main -level 3.1 -r 30 -threads 0 -vf "scale=-2:720" -bufsize 2000k -maxrate 2000k -b:v 2000k -f hls -method PUT "${REMOTE_PATH}/playlist.m3u8" ffmpeg version 3.3.3 }}} Error: [hls @ 0x7fa09a00ca00] Failed to open segment 'init.mp4' Could not write header for output file #0 (incorrect codec parameters ?): No such file or directory Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/6673> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 11

#6541(avformat:new): HLS fMP4 Bug
by FFmpeg 09 Aug '19

09 Aug '19

#6541: HLS fMP4 Bug ----------------------------------+-------------------------------------- Reporter: JohnPi | Type: defect Status: new | Priority: normal Component: avformat | Version: git-master Keywords: Fmp4 HLS | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Hi, When i try to use "-hls_segment_type fmp4" , ffmpeg detect the option but continue to encode in .ts file,the headers are good but the segments aren't in .m4s. Did i did something wrong ? Thank you by advance :) There is the command : {{{ " ./ffmpeg -y -loglevel debug -re -i "udp://239.192.0.1:1234?fifo_size=5000000&overrun_nonfatal=1" -c:v mpeg4 -hls_segment_type fmp4 -hls_fmp4_init_filename test.mp4 /var/www/HLS/A.m3u8 " }}} and there is the m3u8 playlist : {{{ "#EXTM3U #EXT-X-VERSION:7 #EXT-X-TARGETDURATION:3 #EXT-X-MEDIA-SEQUENCE:12 #EXT-X-MAP:URI="test.mp4" #EXTINF:1.920000, A12.ts #EXTINF:1.920000, A13.ts #EXTINF:2.240000, A14.ts #EXTINF:1.920000, A15.ts #EXTINF:1.920000, A16.ts " }}} and there is the ffmpeg -version : {{{ ffmpeg version N-86789-g4c1aac8 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 6.4.0 (Debian 6.4.0-1) 20170704 configuration: --prefix=/root/ffmpeg_build --pkg-config-flags=--static --extra-cflags=-I/root/ffmpeg_build/include --extra- ldflags=-L/root/ffmpeg_build/lib --bindir=/root/bin --enable-gpl --enable- libass --enable-libfdk-aac --enable-libfreetype --enable-vaapi --enable- vdpau --enable-libx264 --enable-nvenc --enable-cuvid --enable-nonfree libavutil 55. 67.100 / 55. 67.100 libavcodec 57.100.104 / 57.100.104 libavformat 57. 75.100 / 57. 75.100 libavdevice 57. 7.100 / 57. 7.100 libavfilter 6. 95.100 / 6. 95.100 libswscale 4. 7.101 / 4. 7.101 libswresample 2. 8.100 / 2. 8.100 libpostproc 54. 6.100 / 54. 6.100 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/6541> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 16

#8067(avfilter:new): vf_scale_vaapi fails when stream contains resolution changes
by FFmpeg 08 Aug '19

08 Aug '19

#8067: vf_scale_vaapi fails when stream contains resolution changes ----------------------------------+-------------------------------------- Reporter: tmm1 | Type: defect Status: new | Priority: normal Component: avfilter | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+-------------------------------------- Summary of the bug: Given an mpegts stream which contains resolution changes, using vaapi decoding along with the scale_vaapi filter causes failures when the resolution change is encountered. ffmpeg appears to be attempting to insert an sws scaler. How to reproduce: {{{ % ffmpeg -loglevel verbose -hwaccel vaapi -hwaccel_output_format vaapi -i input.ts -map 0:v -an -sn -c:v h264_vaapi -init_hw_device vaapi=intel:/dev/dri/renderD128 -profile:v 100 -level 42 -filter_hw_device intel -filter:v scale_vaapi=1280:720 -b:v 3000k -minrate 2700k -maxrate 3300k -bufsize 6000k -f null -y /dev/null ffmpeg version 8183713 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.4) libavutil 56. 31.100 / 56. 31.100 libavcodec 58. 54.100 / 58. 54.100 libavformat 58. 29.100 / 58. 29.100 libavdevice 58. 8.100 / 58. 8.100 libavfilter 7. 57.100 / 7. 57.100 libswscale 5. 5.100 / 5. 5.100 libswresample 3. 5.100 / 3. 5.100 libpostproc 55. 5.100 / 55. 5.100 [AVHWDeviceContext @ 0x255a000] libva: VA-API version 1.5.0 [AVHWDeviceContext @ 0x255a000] libva: va_getDriverName() returns 0 [AVHWDeviceContext @ 0x255a000] libva: va_openDriver() returns 0 [AVHWDeviceContext @ 0x255a000] Initialised VAAPI connection: version 1.5 [AVHWDeviceContext @ 0x255a000] VAAPI driver: Intel i965 driver for Intel(R) Bay Trail - 2.4.0.pre1 (2.4.0.pre1). [AVHWDeviceContext @ 0x255a000] Driver not found in known nonstandard list, using standard behaviour. [mpegts @ 0x2569940] parser not found for codec timed_id3, packets or times may be invalid. Last message repeated 1 times [h264 @ 0x256f740] Reinit context to 1280x720, pix_fmt: yuv420p [mpegts @ 0x2569940] max_analyze_duration 5000000 reached at 5034667 microseconds st:0 Input #0, mpegts, from 'input.ts': Duration: 00:19:18.48, start: 0.033356, bitrate: 3445 kb/s Program 1 Stream #0:0[0x101]: Audio: aac (HE-AAC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 124 kb/s Stream #0:1[0x102]: Video: h264 (High), 1 reference frame ([27][0][0][0] / 0x001B), yuv420p(tv, bt709, progressive, center), 1280x720, 29.97 fps, 29.97 tbr, 90k tbn, 96k tbc Stream #0:2[0x103]: Data: timed_id3 (ID3 / 0x20334449) Stream mapping: Stream #0:1 -> #0:0 (h264 (native) -> h264 (h264_vaapi)) Press [q] to stop, [?] for help [mpegts @ 0x2569940] Correcting start time by 2577 [h264 @ 0x25a9100] Reinit context to 1280x720, pix_fmt: vaapi_vld [graph 0 input from stream 0:1 @ 0x282a340] w:1280 h:720 pixfmt:vaapi_vld tb:1/90000 fr:30000/1001 sar:0/1 sws_param:flags=2 [h264_vaapi @ 0x25a6400] Input surface format is nv12. [h264_vaapi @ 0x25a6400] Using VAAPI profile VAProfileH264High (7). [h264_vaapi @ 0x25a6400] Using VAAPI entrypoint VAEntrypointEncSlice (6). [h264_vaapi @ 0x25a6400] Using VAAPI render target format YUV420 (0x1). [h264_vaapi @ 0x25a6400] RC mode: VBR. [h264_vaapi @ 0x25a6400] RC target: 90% of 3300000 bps over 1818 ms. [h264_vaapi @ 0x25a6400] RC buffer: 6000000 bits, initial fullness 4500000 bits. [h264_vaapi @ 0x25a6400] RC framerate: 30000/1001 (29.97 fps). [h264_vaapi @ 0x25a6400] Using intra, P- and B-frames (supported references: 1 / 1). [h264_vaapi @ 0x25a6400] All wanted packed headers available (wanted 0xd, found 0x1f). Output #0, null, to '/dev/null': Metadata: encoder : Lavf58.29.100 Stream #0:0: Video: h264 (h264_vaapi) (High), 1 reference frame, vaapi_vld(center), 1280x720, q=-1--1, 3000 kb/s, 29.97 fps, 29.97 tbn, 29.97 tbc Metadata: encoder : Lavc58.54.100 h264_vaapi [h264 @ 0x261e580] Reinit context to 1920x1088, pix_fmt: vaapi_vld [graph 0 input from stream 0:1 @ 0x26e9d40] w:1920 h:1080 pixfmt:vaapi_vld tb:1/90000 fr:30000/1001 sar:0/1 sws_param:flags=2 [scaler_out_0_0 @ 0x27cb8c0] w:1280 h:720 flags:'bicubic' interl:0 [auto_scaler_0 @ 0x27a6200] w:iw h:ih flags:'bicubic' interl:0 [scaler_out_0_0 @ 0x27cb8c0] auto-inserting filter 'auto_scaler_0' between the filter 'Parsed_scale_vaapi_0' and the filter 'scaler_out_0_0' Impossible to convert between the formats supported by the filter 'Parsed_scale_vaapi_0' and the filter 'auto_scaler_0' Error reinitializing filters! Failed to inject frame into filter network: Function not implemented Error while processing the decoded data for stream #0:1 [AVIOContext @ 0x25725c0] Statistics: 6606992 bytes read, 2 seeks Conversion failed! }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/8067> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#8044(ffmpeg:new): A potential NPD bug in the source file zmqsend.c
by FFmpeg 08 Aug '19

08 Aug '19

#8044: A potential NPD bug in the source file zmqsend.c -----------------------------------+-------------------------------------- Reporter: wurongxin | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+-------------------------------------- Summary of the bug: 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. In the source file zmqsend.c, at Line 126, the invocation to the function "av_bprint_finalize" will make src_buf as null pointer. This will lead to a NPD at Line 128, with the function call to strlen(src_buf). 126. av_bprint_finalize(&src, &src_buf); 127. 128. if (zmq_send(socket, src_buf, strlen(src_buf), 0) == -1) { 129. av_log(NULL, AV_LOG_ERROR, "Could not send message: %s\n", zmq_strerror(errno)); 130. ret = 1; 131. goto end; 132. } In the source file bprint.c, at Line 248, the variable str will receive the return value from the function av_malloc. In some case, this function can return null pointer. I think, the developer has noticed such case. That is why the developer will assign the variable ret as an error code. However, the null pointer will be assigned to *ret_str at Line 254. 235. int av_bprint_finalize(AVBPrint *buf, char **ret_str) 236. { 237. unsigned real_size = FFMIN(buf->len + 1, buf->size); 238. char *str; 239. int ret = 0; 240. 241. if (ret_str) { 242. if (av_bprint_is_allocated(buf)) { 243. str = av_realloc(buf->str, real_size); 244. if (!str) 245. str = buf->str; 246. buf->str = NULL; 247. } else { 248. str = av_malloc(real_size); 249. if (str) 250. memcpy(str, buf->str, real_size); 251. else 252. ret = AVERROR(ENOMEM); 253. } 254. *ret_str = str; 255. } else { 256. if (av_bprint_is_allocated(buf)) 257. av_freep(&buf->str); 258. } 259. buf->size = real_size; 260. return ret; 261. } -- Ticket URL: <https://trac.ffmpeg.org/ticket/8044> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 7

#8050(avfilter:new): Active Format Description missing (MPEG-2 and H.264)
by FFmpeg 08 Aug '19

08 Aug '19

#8050: Active Format Description missing (MPEG-2 and H.264) -------------------------------------+------------------------------------- Reporter: atorp | Type: | enhancement Status: new | Priority: normal Component: avfilter | Version: git- Keywords: adf, | master mpeg2_metadata, h264_metadata | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: When capturing some DVB-S and DVB-T broadcasts, we can see that the bitstream of the MPEG-2 and AVC/H.264 services include often the Active Format Description (adf): https://en.wikipedia.org/wiki/Active_Format_Description This flag is usually transmited in: - MPEG-2: As "User Data" section (user id: "DTG1"). - H.264: As "Auxiliary data" in a SEI unit (user id: "DTG1"). None of the current mpeg2 and h264 encoders handle that flag. However, as the Bitstream Filters for MPEG-2 (mpeg2_metadata) and H.264 (h264_metadata) can handle different flags similar to this, I request to add support for set/get the ADF flag. Thank you! -- Ticket URL: <https://trac.ffmpeg.org/ticket/8050> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2