December 2017 - FFmpeg-trac - lists.ffmpeg.org

#6893(avutil:new): Compile hwcontext_opencl.c: undefined reference to several OpenCL functions
by FFmpeg 12 Dec '17

12 Dec '17

#6893: Compile hwcontext_opencl.c: undefined reference to several OpenCL functions --------------------------------+-------------------------------------- Reporter: LigH | Type: defect Status: new | Priority: normal Component: avutil | Version: git-master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------+-------------------------------------- Trying to compile ffmpeg for Win32 with OpenCL support in media- autobuild_suite. {{{ Likely error: LD libavutil/avutil-56.dll libavutil/hwcontext_opencl.o:hwcontext_opencl.c:(.text+0xe33): undefined reference to `clCreateImage@28' libavutil/hwcontext_opencl.o:hwcontext_opencl.c:(.text+0x137f): undefined reference to `clGetExtensionFunctionAddressForPlatform@8' libavutil/hwcontext_opencl.o:hwcontext_opencl.c:(.text+0x153b): undefined reference to `clGetExtensionFunctionAddressForPlatform@8' libavutil/hwcontext_opencl.o:hwcontext_opencl.c:(.text+0x3431): undefined reference to `clGetExtensionFunctionAddressForPlatform@8' libavutil/hwcontext_opencl.o:hwcontext_opencl.c:(.text+0x3472): undefined reference to `clGetExtensionFunctionAddressForPlatform@8' libavutil/hwcontext_opencl.o:hwcontext_opencl.c:(.text+0x34b3): undefined reference to `clGetExtensionFunctionAddressForPlatform@8' libavutil/hwcontext_opencl.o:hwcontext_opencl.c:(.text+0x35be): more undefined references to `clGetExtensionFunctionAddressForPlatform@8' follow collect2.exe: error: ld returned 1 exit status make: *** [/build/ffmpeg-git/ffbuild/library.mak:103: libavutil/avutil-56.dll] Error 1 }}} Log file collection attached. -- Ticket URL: <https://trac.ffmpeg.org/ticket/6893> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 14

#6852(ffmpeg:new): Encoding process gets stuck and cpu load goes to 100% on Linux (ffmpeg version 2.8.13)
by FFmpeg 12 Dec '17

12 Dec '17

#6852: Encoding process gets stuck and cpu load goes to 100% on Linux (ffmpeg version 2.8.13) -------------------------------------+------------------------------------- Reporter: fcarvalho | Type: defect Status: new | Priority: important Component: ffmpeg | Version: 2.8.11 Keywords: ffmpeg | Blocked By: encoding mp4 process stuck | Reproduced by developer: 1 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- I am having issues with ffmpeg version 2.8.13 while trying to encode a ulaw to mp4. For more than 95% of the files it works fine, but some of the encoding process simply get stuck and the cpu load goes up to 100% until i kill the process. Details: - Command line: /bin/ffmpeg -f mulaw -ar 8000 -y -i /home/recording_outbound_394485.ulaw -strict -2 /home/recording_outbound_394485.mp4 - I am running on CentOS Linux release 7.3.1611 (Core) - On version 2.8.11 and 2.8.13 the process gets stuck with 100% cpu load - On version 2.5.4 the same files that cause the ffmpeg encoding process to get stuck work as expected in a couple of seconds. - On windows version 2.2.2 it works too and the file is encoded to mp4 as expected. Command ran with valgrind: valgrind /bin/ffmpeg -f mulaw -ar 8000 -y -i /home/recording_outbound_394485.ulaw -strict -2 /home/recording_outbound_394485.mp4 ==48708== Memcheck, a memory error detector ==48708== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==48708== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==48708== Command: /bin/ffmpeg -f mulaw -ar 8000 -y -i /home/recording_outbound_394485.ulaw -strict -2 /home/recording_outbound_394485.mp4 ==48708== ffmpeg version 2.8.13 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-11) configuration: --prefix=/usr --bindir=/usr/bin --datadir=/usr/share/ffmpeg --incdir=/usr/include/ffmpeg --libdir=/usr/lib64 --mandir=/usr/share/man --arch=x86_64 --optflags='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector- strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic' --extra-ldflags='-Wl,-z,relro ' --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-version3 --enable-bzlib --disable-crystalhd --enable-gnutls --enable-ladspa --enable-libass --enable-libcdio --enable-libdc1394 --disable-indev=jack --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-openal --enable-libopenjpeg --enable-libopus --enable-libpulse --enable- libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libv4l2 --enable-libx264 --enable-libx265 --enable-libxvid --enable-x11grab --enable-avfilter --enable-avresample --enable-postproc --enable-pthreads --disable-static --enable-shared --enable-gpl --disable-debug --disable-stripping --shlibdir=/usr/lib64 --enable-runtime-cpudetect libavutil 54. 31.100 / 54. 31.100 libavcodec 56. 60.100 / 56. 60.100 libavformat 56. 40.101 / 56. 40.101 libavdevice 56. 4.100 / 56. 4.100 libavfilter 5. 40.101 / 5. 40.101 libavresample 2. 1. 0 / 2. 1. 0 libswscale 3. 1.101 / 3. 1.101 libswresample 1. 2.101 / 1. 2.101 libpostproc 53. 3.100 / 53. 3.100 [mulaw @ 0x162de840] Estimating duration from bitrate, this may be inaccurate Guessed Channel Layout for Input Stream #0.0 : mono Input #0, mulaw, from '/home/recording_outbound_394485.ulaw': Duration: 00:04:17.12, bitrate: 64 kb/s Stream #0:0: Audio: pcm_mulaw, 8000 Hz, 1 channels, s16, 64 kb/s [aac @ 0x163093c0] Too many bits per frame requested, clamping to max Output #0, mp4, to '/home/recording_outbound_394485.mp4': Metadata: encoder : Lavf56.40.101 Stream #0:0: Audio: aac ([64][0][0][0] / 0x0040), 8000 Hz, mono, fltp, 48 kb/s Metadata: encoder : Lavc56.60.100 aac Stream mapping: Stream #0:0 -> #0:0 (pcm_mulaw (native) -> aac (native)) Press [q] to stop, [?] for help size= 322kB time=00:01:04.51 bitrate= 40.9kbits/s ===>> And it gets stuck <<=== Unfortunatelly i can't attach the audio file (ulaw) due to client's privacy. -- Ticket URL: <https://trac.ffmpeg.org/ticket/6852> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#6906(avfilter:new): Option order wrong for filter 'color'
by FFmpeg 11 Dec '17

11 Dec '17

#6906: Option order wrong for filter 'color' ----------------------------------+--------------------------------------- Reporter: Misaki | Type: defect Status: new | Priority: minor Component: avfilter | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+--------------------------------------- According to the manual, option four for filter 'color' should be sample aspect ratio: https://ffmpeg.org/ffmpeg-filters.html However, the command {{{ffmpeg -filter_complex "color=white:160x160:1:1:10" output.mp4}}} produces output of 1 frame. -- Ticket URL: <https://trac.ffmpeg.org/ticket/6906> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#6908(ffmpeg:new): Concatenating mpegts files into stream longer than timestamp wrap can produce non-monotonic timestamps
by FFmpeg 11 Dec '17

11 Dec '17

#6908: Concatenating mpegts files into stream longer than timestamp wrap can produce non-monotonic timestamps -------------------------------------+------------------------------------- Reporter: calwilson | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: git- Keywords: concatdec | master mpegts | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: When concatenating multiple mpeg transport stream assets into a continuous mpeg transport stream, ffmpeg reports errors of non-monotonic timestamps. These timestamps are then changed to old_timestamp + 1 which produces an invalid stream. As far as I can tell it seems to be some interplay between the concat demuxer and the timestamp wrapping logic. If the timestamp is within 60s before the the max timestamp at a file inpoint, it triggers the subtract offset timestamp wrap logic which produces negative timestamps. I include the asset and playlist, and the ffmpeg logs. How to reproduce: {{{ % ffmpeg -report -nostdin -hide_banner -loglevel trace -nostats -probesize 1000000 -analyzeduration 5000000 -max_delay 0 -fflags +genpts -async 1 -f concat -y -i tears_playlist.ffmpeg -map 0 -c copy -copy_unknown -f mpegts -muxrate 1 -pcr_period 30 -pes_payload_size 50 -metadata service_provider=test -metadata service_name=test -mpegts_original_network_id 31303 -mpegts_transport_stream_id 1 -mpegts_flags +system_b -tables_version 0 /dev/null ffmpeg version git master built on Ubuntu 16.04 LTS 64bit }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/6908> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#6775(avcodec:new): gst-libav can no longer decode video (3.4 regression)
by FFmpeg 10 Dec '17

10 Dec '17

#6775: gst-libav can no longer decode video (3.4 regression) ------------------------------------+---------------------------------- Reporter: heftig | Type: defect Status: new | Priority: normal Component: avcodec | Version: Keywords: regression | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ------------------------------------+---------------------------------- Summary of the bug: gst-libav attempts to drain the decoder (by feeding avcodec_decode_video2 empty packets) before every discontinuity in the stream. The compat implementation used since 3.4 doesn't seem to handle this case correctly. It does not consume any data from the following (real) packets and further calls echo a message: "Got unexpected packet size after a partial decode" Since the start of the stream is also considered a discontinuity, the decode can't even start. Avoiding draining at the start of the stream doesn't solve the problem for any further discontinuity. Downstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=789193 How to reproduce: {{{ gst-launch-1.0 videotestsrc ! x264enc ! rtph264pay ! identity drop- probability=0.1 ! rtph264depay ! h264parse ! avdec_h264 ! videoconvert ! autovideosink }}} This creates a h264 stream which is missing 10% of frames. (1) With FFmpeg 3.3, it manages a best-effort (glitchy) decode. (2) With FFmpeg 3.4, it does not start decoding at all. (3) Reverting gst-libav commit 67e55e47 (or inserting a call to avcodec_flush_buffers after draining) allows decoding to start, but causes the decoder state to be cleared after each missing frame, creating much worse output than (1). -- Ticket URL: <https://trac.ffmpeg.org/ticket/6775> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 17

#6889(undetermined:new): ffmpeg.c stalls after N frames when capturing v4l2 video and pulse audio
by FFmpeg 09 Dec '17

09 Dec '17

#6889: ffmpeg.c stalls after N frames when capturing v4l2 video and pulse audio --------------------------------------+------------------------------------ Reporter: neverminder | Type: defect Status: new | Priority: critical Component: undetermined | Version: 3.4 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+------------------------------------ Summary of the bug: ffmpeg.c stalls after N frames when capturing v4l2 video and pulse audio output log: https://pastebin.com/8i3LMdgc How to reproduce: {{{ ffmpeg -y -report -debug_ts -f v4l2 -input_format mjpeg -s uhd2160 -i /dev/video0 -f pulse -channels 1 -i default -c:v libx264 -preset superfast video.mkv ffmpeg version 3.4-1~16.04.york0 }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/6889> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#6902(undetermined:new): concat outputs only the first file
by FFmpeg 08 Dec '17

08 Dec '17

#6902: concat outputs only the first file -------------------------------------+------------------------------------- Reporter: xamarin | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: I try to concatenate 3 videos, but the resulting video is just the first one. The other 2 are missing. How to reproduce: see the 4 attached files. {{{ % .\ffmpeg.exe -y -i "concat:./part1.mp4|./part2.mp4|./part3.mp4|" -c copy out.mp4 ffmpeg version N-89395-g71421f382f Copyright (c) 2000-2017 the FFmpeg developers built with gcc 7.2.0 (GCC) configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable- bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable- libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-dxva2 --enable-avisynth --enable- libmfx libavutil 56. 5.100 / 56. 5.100 libavcodec 58. 6.102 / 58. 6.102 libavformat 58. 2.103 / 58. 2.103 libavdevice 58. 0.100 / 58. 0.100 libavfilter 7. 6.100 / 7. 6.100 libswscale 5. 0.101 / 5. 0.101 libswresample 3. 0.101 / 3. 0.101 libpostproc 55. 0.100 / 55. 0.100 Hyper fast Audio and Video encoder usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}... }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/6902> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3

#6900(undetermined:new): ffmpeg versions above 3.3.4 can not open this AAC file
by FFmpeg 08 Dec '17

08 Dec '17

#6900: ffmpeg versions above 3.3.4 can not open this AAC file -------------------------------------+------------------------------------- Reporter: dka | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: How to reproduce: {{{ ffmpeg.exe -i 1.aac -f null - ffmpeg version N-89395-g71421f382f Copyright (c) 2000-2017 the FFmpeg developers built with gcc 7.2.0 (GCC) configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable- bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable- libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-dxva2 --enable-avisynth --enable- libmfx libavutil 56. 5.100 / 56. 5.100 libavcodec 58. 6.102 / 58. 6.102 libavformat 58. 2.103 / 58. 2.103 libavdevice 58. 0.100 / 58. 0.100 libavfilter 7. 6.100 / 7. 6.100 libswscale 5. 0.101 / 5. 0.101 libswresample 3. 0.101 / 3. 0.101 libpostproc 55. 0.100 / 55. 0.100 [aac @ 047cb0a0] More than one AAC RDB per ADTS frame is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [aac @ 047cb0a0] channel element 2.0 is not allocated [aac @ 047d46c0] decoding for stream 0 failed [aac @ 047d46c0] Estimating duration from bitrate, this may be inaccurate [aac @ 047d46c0] Could not find codec parameters for stream 0 (Audio: aac (SSR), 3.0, fltp, 116 kb/s): unspecified sample rate Consider increasing the value for the 'analyzeduration' and 'probesize' options Input #0, aac, from '1.aac': Metadata: artist : The Nexion Project title : Over the Mountains encoded_by : Ripped with Streamripper track : 11 Duration: 00:02:58.75, bitrate: 116 kb/s Stream #0:0: Audio: aac (SSR), 3.0, fltp, 116 kb/s Stream mapping: Stream #0:0 -> #0:0 (aac (native) -> pcm_s16le (native)) Press [q] to stop, [?] for help [aac @ 047fada0] More than one AAC RDB per ADTS frame is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented. [aac @ 047fada0] channel element 2.0 is not allocated Error while decoding stream #0:0: Invalid data found when processing input 1.aac: Invalid data found when processing input Finishing stream 0:0 without any data written to it. [abuffer @ 047e97c0] Value inf for parameter 'time_base' out of range [0 - 2.14748e+009] Last message repeated 3 times [abuffer @ 047e97c0] Error setting option time_base to value 1/0. [graph_0_in_0_0 @ 047ea7a0] Error applying options to the filter. Error configuring filter graph Conversion failed! }}} AAC file: [https://yadi.sk/d/7_P-CpEY3QQDwy] -- Ticket URL: <https://trac.ffmpeg.org/ticket/6900> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#6898(ffmpeg:new): Screen flickers/stutters during desktop recording when KDE compositing manager is on.
by FFmpeg 08 Dec '17

08 Dec '17

#6898: Screen flickers/stutters during desktop recording when KDE compositing manager is on. ---------------------------------+--------------------------------------- Reporter: edgarej | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+--------------------------------------- Summary of the bug: Screen flickers/stutters during desktop recording when KDE compositing manager is on. How to reproduce: FFMPEG Command: ffmpeg -n -framerate 30 -video_size 1920x1080 -f x11grab -i :0.0 -c:v libx264rgb -crf 0 -preset ultrafast -threads 4 test-bugReport.mp4 FFMPEG Version: ffmpeg version 3.4 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 7.2.0 (GCC) configuration: --prefix=/usr --disable-debug --disable-static --disable- stripping --enable-avisynth --enable-avresample --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl --enable-ladspa --enable-libass --enable-libbluray --enable-libfreetype --enable-libfribidi --enable- libgsm --enable-libiec61883 --enable-libmodplug --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxvid --enable-shared --enable-version3 libavutil 55. 78.100 / 55. 78.100 libavcodec 57.107.100 / 57.107.100 libavformat 57. 83.100 / 57. 83.100 libavdevice 57. 10.100 / 57. 10.100 libavfilter 6.107.100 / 6.107.100 libavresample 3. 7. 0 / 3. 7. 0 libswscale 4. 8.100 / 4. 8.100 libswresample 2. 9.100 / 2. 9.100 libpostproc 54. 7.100 / 54. 7.100 Splitting the commandline. Reading option '-v' ... matched as option 'v' (set logging level) with argument '9'. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument '99'. Reading option '-i' ...Missing argument for option 'i'. Error splitting the argument list: Invalid argument SYSTEM INFO: Hardware: 4 x Intel Core i7-6500U CPU @ 2.50 GHz 8 GB Ram Software Manjaro Linux KDE Plasma Version: 5.11.4 KDE Frameworks Version: 5.40.0 Qt Version: 5.9.3 Kernel Version: 4.14.3-1-Manjaro OS Type: 64-bit Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/6898> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 6

#6901(ffmpeg:new): FFmpeg mp4 bitrate is higher than specified
by FFmpeg 08 Dec '17

08 Dec '17

#6901: FFmpeg mp4 bitrate is higher than specified -------------------------------------+---------------------------------- Reporter: romario | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: 3.4 Keywords: mp4 bitrate | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+---------------------------------- Summary of the bug: How to reproduce: {{{ ffmpeg.exe -y -i example.flac -f mp4 -b:a 320k output_320.mp4 }}} Actual result : mp4 file has 334k bitrate Expected result : mp4 file has 320k bitrate -- Ticket URL: <https://trac.ffmpeg.org/ticket/6901> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2