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

#7671(avfilter:new): Filters, add the RGB version of “chromahold”
by FFmpeg 04 Sep '19

04 Sep '19

#7671: Filters, add the RGB version of “chromahold” ----------------------------------+--------------------------------------- Reporter: Kdmeizk | Type: enhancement Status: new | Priority: normal Component: avfilter | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- An example related to “[https://ffmpeg.org/ffmpeg-filters.html#chromahold chromahold]”: The RGB version of “[https://ffmpeg.org/ffmpeg-filters.html#chromakey chromakey]” is “[https://ffmpeg.org/ffmpeg-filters.html#colorkey colorkey]”. -- Ticket URL: <https://trac.ffmpeg.org/ticket/7671> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#7982(undetermined:new): null pointer passed at frame_thread_encoder.c:213 and undefined behaviour at r210enc.c
by FFmpeg 03 Sep '19

03 Sep '19

#7982: null pointer passed at frame_thread_encoder.c:213 and undefined behaviour at r210enc.c -------------------------------------+------------------------------------- Reporter: Suhwan | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: crash, | Blocked By: r210enc | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: There's two null pointer passed as argument at libavcodec/frame_thread_encoder.c:213:20: and undefined behaviour at libavcodec/r210enc.c:69:28. (left shift of 522 by 22) How to reproduce: {{{ Run following cmd: % ffmpeg_g -t 3 -y -i tmp.avi -map 0 -c:s:1 h263p -c:v r10k -disposition:a r10k -disposition:s adpcm_adx -vframes 64 -aframes 81 tmp_.adx ffmpeg version N-94142-g3b2082c663 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/7982> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#7981(undetermined:new): null pointer passed as argument at libavcodec/frame_thread_encoder.c:213:20
by FFmpeg 03 Sep '19

03 Sep '19

#7981: null pointer passed as argument at libavcodec/frame_thread_encoder.c:213:20 -------------------------------------+------------------------------------- Reporter: Suhwan | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: Null | Blocked By: Pointer passed, Division by Zero, | ASAN, FFMpeg, avformat | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: There are 2 null pointer passed as argument at libavcodec/frame_thread_encoder.c:213:45 and a division by zero at libavformat/rawenc.c:70:50. How to reproduce: {{{ Run the following cmd: % ffmpeg_g -t 0 -stream_loop 20 -y -r 49 -i tmp.avi -map 0 -c:v v408 -c:s:8 pcm_s8 -disposition:a cinepak -disposition:v:109 ffv1 -aframes 38 -ar 48000 -b:v 627 tmp_.adx ffmpeg version: N-94137-g89b96900fa 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/7981> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#8018(ffmpeg:new): RPi 4 h264_mmal error
by FFmpeg 02 Sep '19

02 Sep '19

#8018: RPi 4 h264_mmal error -----------------------------------+-------------------------------------- Reporter: RAJensen | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: git-master Keywords: h264_mmal | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+-------------------------------------- Summary of the bug: h264_mmal is no longer working on RPi4 with the new Broadcom chip 64-bit BCM2711 quad-core A72 CPU @ 1.5GHz VideoCore VI GPU. With same file, same compile it works on RPi3. GPU Ram set to 256Gb. How to reproduce: {{{ sudo ffmpeg -y -v 9 -loglevel 99 -report -ss 00:00:00 -c:v h264_mmal -i 'RPI4_h264_mmal.ts' -to 00:01:00 -map 0:0 -map 0:3 -c:v h264_omx -b:v 1500k -flags +global_header -c:a:0 copy 'test.mkv' ffmpeg version N-94282-g80dacbedba Copyright (c) 2000-2019 the FFmpeg developers built with gcc 8 (Raspbian 8.3.0-6+rpi1) configuration: --arch=armel --target-os=linux --enable-gpl --enable-mmal --enable-omx --enable-omx-rpi --enable-nonfree built on ... RAspberry Pi 4 OS=Buster }}} I don't know but i think the error occurs because that the new chip has HDMI 0 and HDMI 1. I have tried with and without 4K resolution enabled on RPi4. Testet on Buster with desktop and Buster Lite without desktop. Test done on RPi4 2Gb Ram and 4Gb RAM. FFMPEG info: V..... h264_omx OpenMAX IL H.264 video encoder (codec h264) V..... h264_v4l2m2m V4L2 mem2mem H.264 encoder wrapper (codec h264) V..... h264_vaapi H.264/AVC (VAAPI) (codec h264) VFS..D h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 V..... h264_v4l2m2m V4L2 mem2mem H.264 decoder wrapper (codec h264) V..... h264_mmal h264 (mmal) (codec h264) -- Ticket URL: <https://trac.ffmpeg.org/ticket/8018> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#8103(undetermined:new): ffmpeg unable to use specific 3dlut file
by FFmpeg 01 Sep '19

01 Sep '19

#8103: ffmpeg unable to use specific 3dlut file --------------------------------------+---------------------------------- Reporter: Bernardus | Type: defect Status: new | Priority: normal Component: undetermined | Version: 3.4.6 Keywords: 3dlut | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+---------------------------------- Hi there, I have some D-log M video files from my DJI Mavic 2 drone that I would like to process on my linux system in Openshot. In order to apply a 3d LUT I use ffmpeg with the option -vf lut3d=<LUT file>. However using a default LUT file provided by DJI results in a error. PLease help! Summary of the bug: How to reproduce: {{{ % ffmpeg -i input.mp4 -vf lut3d="DLog-M+to+Rec709.cube" output.mp4 ffmpeg version 3.4.6-0ubuntu0.18.04.1 built with gcc 7 (Ubuntu 7.3.0-16ubuntu3) }}} The output of ffmpeg is: [Parsed_lut3d_0 @ 0x55fd3ad23e20] 3D LUT is empty [AVFilterGraph @ 0x55fd3ad21c20] Error initializing filter 'lut3d' with args 'DLog-M+to+Rec709.cube' Error reinitializing filters! Failed to inject frame into filter network: Invalid data found when processing input Error while processing the decoded data for stream #0:0 Conversion failed! I have an other LUT file (thisoneworks.cube) that does work as expected when applied to the same video file, so I'm wondering what's going wrong here. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8103> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4