November 2020 - FFmpeg-trac - lists.ffmpeg.org

Re: [FFmpeg-trac] #5(avformat:closed): jp2k muxed into mov by FFmpeg can't be played by QuickTime
by FFmpeg 12 Nov '20

12 Nov '20

#5: jp2k muxed into mov by FFmpeg can't be played by QuickTime -------------------------------------+------------------------------------- Reporter: cehoyos | Owner: Type: defect | Status: closed Priority: normal | Component: avformat Version: git | Resolution: Keywords: j2k mov | worksforme roundup | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Changes (by emcodem): * status: open => closed * resolution: => worksforme * reproduced: 1 => 0 Comment: No Black screen anymore using recent version, can i just close such old tickets that are not reproduceable anymore and years old? -- Ticket URL: <https://trac.ffmpeg.org/ticket/5#comment:9> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#8983(undetermined:new): Video Sync Support
by FFmpeg 12 Nov '20

12 Nov '20

#8983: Video Sync Support -------------------------------------+------------------------------------- Reporter: villmer | Type: | enhancement Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- '''Synchronously''' acquiring two camera streams (such as V4L2) is '''critical''' for both recording (and live streaming of) stereoscopic video and, in our case, 360° video (using two back-to-back cameras). Both 360° video and stereo video utilize ffmpeg framepack filter to place the two streams side-by-side. Unfortunately, the synchronous acquisition of two V4L2 video streams is currently not possible with ffmpeg. While two streams can be requested, there is '''always''' a delay of at least ~1second. Despite using various filters, such as itsoffset, setpts etc, we have been unable to synchronize two streams. As the ffmpeg team has already taken steps implementing various 360° video support, we would like to see dual-stream synchronization capabilities added to ffmpeg. In this way, ffmpeg can be directly used to '''create''' 360° video - instead of just performing post-production effects to it. Our current ffmpeg pipeline to capture two V4L2 streams and one alsa audio stream looks like this: ffmpeg -y \ -f v4l2 -input_format h264 -video_size 1080x1080 -framerate 20 -thread_queue_size 32k -i /dev/video0 \ -f v4l2 -input_format h264 -video_size 1080x1080 -framerate 20 -thread_queue_size 32k -i /dev/video1 \ -f alsa -ac 2 -acodec pcm_s32le -sample_rate 11025 -thread_queue_size 32k -async 1 -itsoffset 0.3 -i hw:1,0 \ -filter_complex "[0:v][1:v]framepack=sbs" \ -f mp4 \ -c:v libx264 \ -b:v 2M \ -b:a 128k \ -preset ultrafast \ -pix_fmt yuv420p \ video.mp4 The code above successfully records two V4L2 videos into a side-by-side formation, synchronously merges one alsa audio stream (via -itsoffset 0.3) and exports everything out to an mp4 file on-the-fly! The '''ONLY''' (unsolvable) problem is the ~1 second lag between videos. We are, quite literally, one second from a workable solution. However, removing this issue has not been successful despite many days of effort. On the Raspberry Pi (Compute Module 4) we can use the Raspivid application to capture frame-accurate, synchronous video from two cameras @ 30fps by simply adding the '''-3d sbs''' tag. We believe ffmpeg oils potentially use similar techniques / code to synchronize the videos with a modified V4L2 driver. We have a new post on the Raspberry Pi forums describing this: https://www.raspberrypi.org/forums/viewtopic.php?f=61&t=290197&p=1754295#p1… We are attaching a file showing the results of the code above. As you see, FFMPEG successfully places two (circular) videos side-by-side. The ONLY issue is the ~1second time lag. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8983> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#8971(ffmpeg:new): Contrast Adaptive Sharpening (CAS) is broken
by FFmpeg 12 Nov '20

12 Nov '20

#8971: Contrast Adaptive Sharpening (CAS) is broken -------------------------------------+------------------------------------- Reporter: lextra2 | Type: defect Status: new | Priority: normal Component: ffmpeg | Version: Keywords: CAS | unspecified Contrast Adaptive Sharpening | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- The [https://ffmpeg.org/ffmpeg-filters.html#cas Contrast Adaptive Sharpening filter] is broken. It causes chroma artefacts. I used the following command: {{{ ffmpeg.exe -i input.png -vf cas=1 outputFFMPEG.png }}} The build version was this: {{{ ffmpeg version 4.3.1-2020-11-08-full_build-www.gyan.dev Copyright (c) 2000-2020 the FFmpeg developers built with gcc 10.2.0 (Rev3, Built by MSYS2 project) configuration: --enable-gpl --enable-version3 --enable-static --disable- w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable- libsnappy --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libdav1d --enable-libzvbi --enable-librav1e --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-frei0r --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable- libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libcdio --enable-libgme --enable- libmodplug --enable-libopenmpt --enable-libopencore-amrwb --enable- libmp3lame --enable-libshine --enable-libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libilbc --enable-libgsm --enable- libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b --enable-libflite --enable-libmysofa --enable-librubberband --enable-libsoxr --enable-chromaprint libavutil 56. 51.100 / 56. 51.100 libavcodec 58. 91.100 / 58. 91.100 libavformat 58. 45.100 / 58. 45.100 libavdevice 58. 10.100 / 58. 10.100 libavfilter 7. 85.100 / 7. 85.100 libswscale 5. 7.100 / 5. 7.100 libswresample 3. 7.100 / 3. 7.100 libpostproc 55. 7.100 / 55. 7.100 }}} When used on [https://i.postimg.cc/KZNqRd7B/input.png this image] I get [https://i.postimg.cc/WjD8vDyM/output-FFMPEG.png this output] Meanwhile, when using the following command with [https://github.com /GPUOpen-Effects/FidelityFX- CAS/blob/master/CasCmdLine/x64/Release/CasCmdLine.exe CasCmdLine.exe] {{{ CasCmdLine.exe -Sharpness 1 -FP16 input.png outputCAS.png }}} I get [https://i.postimg.cc/Wp2sMRxV/output-CAS.png the correct output]. Please note, the artifacts (with FFMPEG) are even worse when used on a video file, instead of an image. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8971> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#8975(undetermined:new): ffmpeg dependency security bug
by FFmpeg 12 Nov '20

12 Nov '20

#8975: ffmpeg dependency security bug -------------------------------------+------------------------------------- Reporter: fastfading | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Current ffmpeg version 4.3.1 ffmpeg version 4.3.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2020 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 depend on 3rd party Lib Bug ID Version Latest Known Version openjpeg CVE-2016-7163 2.3.1 2.3.1 libpng CVE-2019-7317 1.6.36 1.6.37 bzip2 CVE-2019-12900 1.0.6 1.0.8 expat CVE-2019-15903 2.2.6 2.2.10 alsa CVE-2019-13351 1.0.17 These 3rd party libs all have security bugs. you can google CVE bug id for detail easily. For Example https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7163 Please upgrade these libs to newest version to fix that. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8975> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#8974(undetermined:new): ffmpeg dependency security bug
by FFmpeg 12 Nov '20

12 Nov '20

#8974: ffmpeg dependency security bug -------------------------------------+------------------------------------- Reporter: fastfading | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Current ffmpeg version 4.3.1 ffmpeg version 4.3.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2020 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 depend on 3rd party Lib Bug ID Version Latest Known Version openjpeg CVE-2016-7163 2.3.1 2.3.1 libpng CVE-2019-7317 1.6.36 1.6.37 bzip2 CVE-2019-12900 1.0.6 1.0.8 expat CVE-2019-15903 2.2.6 2.2.10 alsa CVE-2019-13351 1.0.17 These 3rd party libs all have security bugs. you can google CVE bug id for detail easily. For Example https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7163 Please upgrade these libs to newest version to fix that. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8974> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#8976(undetermined:new): ffmpeg dependency security bug
by FFmpeg 12 Nov '20

12 Nov '20

#8976: ffmpeg dependency security bug -------------------------------------+------------------------------------- Reporter: fastfading | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Current ffmpeg version 4.3.1 ffmpeg version 4.3.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2020 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 depend on 3rd party Lib Bug ID Version Latest Known Version openjpeg CVE-2016-7163 2.3.1 2.3.1 libpng CVE-2019-7317 1.6.36 1.6.37 bzip2 CVE-2019-12900 1.0.6 1.0.8 expat CVE-2019-15903 2.2.6 2.2.10 alsa CVE-2019-13351 1.0.17 These 3rd party libs all have security bugs. you can google CVE bug id for detail easily. For Example https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7163 Please upgrade these libs to newest version to fix that. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8976> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#8978(undetermined:new): ffmpeg dependency security bug
by FFmpeg 12 Nov '20

12 Nov '20

#8978: ffmpeg dependency security bug -------------------------------------+------------------------------------- Reporter: fastfading | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Current ffmpeg version 4.3.1 ffmpeg version 4.3.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2020 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 depend on 3rd party Lib Bug ID Version Latest Known Version openjpeg CVE-2016-7163 2.3.1 2.3.1 libpng CVE-2019-7317 1.6.36 1.6.37 bzip2 CVE-2019-12900 1.0.6 1.0.8 expat CVE-2019-15903 2.2.6 2.2.10 alsa CVE-2019-13351 1.0.17 These 3rd party libs all have security bugs. you can google CVE bug id for detail easily. For Example https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7163 Please upgrade these libs to newest version to fix that. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8978> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#8979(undetermined:new): ffmpeg dependency security bug
by FFmpeg 12 Nov '20

12 Nov '20

#8979: ffmpeg dependency security bug -------------------------------------+------------------------------------- Reporter: fastfading | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Current ffmpeg version 4.3.1 ffmpeg version 4.3.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2020 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 depend on 3rd party Lib Bug ID Version Latest Known Version openjpeg CVE-2016-7163 2.3.1 2.3.1 libpng CVE-2019-7317 1.6.36 1.6.37 bzip2 CVE-2019-12900 1.0.6 1.0.8 expat CVE-2019-15903 2.2.6 2.2.10 alsa CVE-2019-13351 1.0.17 These 3rd party libs all have security bugs. you can google CVE bug id for detail easily. For Example https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7163 Please upgrade these libs to newest version to fix that. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8979> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#8977(undetermined:new): ffmpeg dependency security bug
by FFmpeg 12 Nov '20

12 Nov '20

#8977: ffmpeg dependency security bug -------------------------------------+------------------------------------- Reporter: fastfading | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Current ffmpeg version 4.3.1 ffmpeg version 4.3.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2020 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 depend on 3rd party Lib Bug ID Version Latest Known Version openjpeg CVE-2016-7163 2.3.1 2.3.1 libpng CVE-2019-7317 1.6.36 1.6.37 bzip2 CVE-2019-12900 1.0.6 1.0.8 expat CVE-2019-15903 2.2.6 2.2.10 alsa CVE-2019-13351 1.0.17 These 3rd party libs all have security bugs. you can google CVE bug id for detail easily. For Example https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7163 Please upgrade these libs to newest version to fix that. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8977> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#8980(undetermined:new): ffmpeg dependency security bug
by FFmpeg 12 Nov '20

12 Nov '20

#8980: ffmpeg dependency security bug -------------------------------------+------------------------------------- Reporter: fastfading | Type: defect Status: new | Priority: important Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Current ffmpeg version 4.3.1 ffmpeg version 4.3.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2020 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 depend on 3rd party Lib Bug ID Version Latest Known Version openjpeg CVE-2016-7163 2.3.1 2.3.1 libpng CVE-2019-7317 1.6.36 1.6.37 bzip2 CVE-2019-12900 1.0.6 1.0.8 expat CVE-2019-15903 2.2.6 2.2.10 alsa CVE-2019-13351 1.0.17 These 3rd party libs all have security bugs. you can google CVE bug id for detail easily. For Example https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7163 Please upgrade these libs to newest version to fix that. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8980> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1