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

Re: [FFmpeg-trac] #2099(avformat:closed): FFMPEG Does not allow TrueHD, DTS-Master Audio or DTS in .M4V even though format supports it
by FFmpeg 08 Aug '19

08 Aug '19

#2099: FFMPEG Does not allow TrueHD, DTS-Master Audio or DTS in .M4V even though format supports it -------------------------------------+------------------------------------- Reporter: JohnGalt | Owner: Type: enhancement | Status: closed Priority: wish | Component: avformat Version: git-master | Resolution: | needs_more_info Keywords: mov dca thd | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Comment (by cehoyos): A specification for TrueHD in isom exists now and ticket #8051 was created. -- Ticket URL: <https://trac.ffmpeg.org/ticket/2099#comment:55> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 0

#7133(undetermined:new): [FFProbe] invalid byte range requests
by FFmpeg 06 Aug '19

06 Aug '19

#7133: [FFProbe] invalid byte range requests -------------------------------------+------------------------------------- Reporter: tjenkinson | Type: defect Status: new | Priority: normal Component: | Version: git- undetermined | master Keywords: ffprobe, | Blocked By: HTTP error 416 | Reproduced by developer: 0 Blocking: | Analyzed by developer: 0 | -------------------------------------+------------------------------------- '''Summary of the bug:''' When seeking isn't disabled (`-seekable 0`), with some input files ffprobe attempts to make byte range requests past the end of the file. The response for the file (from s3) that is being requested has a {{{ Content-Length: 393740 }}} header. You can see from the output below that ffprobe is requesting from byte 393740 and then from byte 8590008746, both of which are invalid. ffprobe works correctly with the `-seekable 0` flag on the same file. I am not sure what the correct behaviour should be here. Maybe: - Exit with an error immediately before attempting a request with an invalid byte range - If the `seekable` option is `-1`, automatically retry with seeking disabled - ?? '''How to reproduce:''' Unfortunately I am unable to provide a file with this problem here. But this shows the output. {{{ % ffprobe "https://example.com/somefile.caf" -loglevel debug ffprobe version N-90650-g3e9d676192 Copyright (c) 2007-2018 the FFmpeg developers built with Apple LLVM version 9.0.0 (clang-900.0.39.2) configuration: --disable-x86asm libavutil 56. 13.100 / 56. 13.100 libavcodec 58. 17.100 / 58. 17.100 libavformat 58. 11.101 / 58. 11.101 libavdevice 58. 2.100 / 58. 2.100 libavfilter 7. 14.100 / 7. 14.100 libswscale 5. 0.102 / 5. 0.102 libswresample 3. 0.101 / 3. 0.101 [NULL @ 0x7f7f2f002e00] Opening 'https://<<redacted>>' for reading [https @ 0x7f7f2ef00140] Setting default whitelist 'http,https,tls,rtp,tcp,udp,crypto,httpproxy' [https @ 0x7f7f2ef00140] request: GET /<<redacted>> HTTP/1.1 User-Agent: Lavf/58.11.101 Accept: */* Range: bytes=0- Connection: close Host: <<redacted>>.s3.amazonaws.com Icy-MetaData: 1 [caf @ 0x7f7f2f002e00] Format caf probed with size=2048 and score=100 [https @ 0x7f7f2ef00140] request: GET /<<redacted>> HTTP/1.1 User-Agent: Lavf/58.11.101 Accept: */* Range: bytes=393740- Connection: close Host: <<redacted>>.s3.amazonaws.com Icy-MetaData: 1 [https @ 0x7f7f2ef00140] HTTP error 416 Requested Range Not Satisfiable [https @ 0x7f7f2ef00140] request: GET /<<redacted>> HTTP/1.1 User-Agent: Lavf/58.11.101 Accept: */* Range: bytes=393740- Connection: close Host: <<redacted>>.s3.amazonaws.com Icy-MetaData: 1 [https @ 0x7f7f2ef00140] HTTP error 416 Requested Range Not Satisfiable [caf @ 0x7f7f2f002e00] skipping CAF chunk: 00000000 ([0][0][0][0]), size 0 Last message repeated 375 times [caf @ 0x7f7f2f002e00] skipping CAF chunk: 00000000 ([0][0][0][0]), size 8590000126 [https @ 0x7f7f2ef00140] request: GET /<<redacted>> HTTP/1.1 User-Agent: Lavf/58.11.101 Accept: */* Range: bytes=8590008746- Connection: close Host: <<redacted>.s3.amazonaws.com Icy-MetaData: 1 [https @ 0x7f7f2ef00140] HTTP error 416 Requested Range Not Satisfiable [caf @ 0x7f7f2f002e00] skipping CAF chunk: 00000000 ([0][0][0][0]), size 281457796579324 [https @ 0x7f7f2ef00140] request: GET /<<redacted>> HTTP/1.1 User-Agent: Lavf/58.11.101 Accept: */* Range: bytes=281457796587956- Connection: close Host: <<redacted>.s3.amazonaws.com Icy-MetaData: 1 [https @ 0x7f7f2ef00140] HTTP error 416 Requested Range Not Satisfiable [caf @ 0x7f7f2f002e00] skipping CAF chunk: FFFBFFF9 ([255][251][255][249]), size -562971428651010 [AVIOContext @ 0x7f7f2ec12140] Statistics: 16347 bytes read, 0 seeks https://<<redacted>>: Invalid data found when processing input }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/7133> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 5

#8058(documentation:new): scale_* filters missing documentation
by FFmpeg 05 Aug '19

05 Aug '19

#8058: scale_* filters missing documentation -------------------------------------+------------------------------------- Reporter: fortman | Type: defect Status: new | Priority: normal Component: | Version: git- documentation | master Keywords: scale_cuda, | Blocked By: scale_qsv | Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: In the official documentation https://ffmpeg.org/ffmpeg-filters.html these HW filters are missing: - scale_cuda - thumbnail_cuda - scale_qsv - deinterlace_qsv - overlay_qsv - vpp_qsv However, others like yadif_cuda and scale_npp are documented. I suggest to almost ''list'' them in the documentation. With special care to scale_cuda and scale_qsv as they are very useful. Regards. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8058> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1

#8060(avfilter:new): hwupload_qsv
by FFmpeg 05 Aug '19

05 Aug '19

#8060: hwupload_qsv -------------------------------------+------------------------------------- Reporter: fortman | Type: | enhancement Status: new | Priority: normal Component: avfilter | Version: git- Keywords: | master hwupload_qsv | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: When mixing multiple HW contexts at the same time, some filter graphs are impossible. That's because in some cases we lack the option for selecting the target HW device. For example, if we're using "-filter_hw_device cuda", then it's impossible to upload to a QSV device. But if you use "-filter_hw_device qsv" then you have the option to use the filter "hwupload_cuda". So, I suggest to create the filter "hwupload_qsv" too (and even other versions like "hwupload_vappi" for example). Please consider this enhancement. Thank you! -- Ticket URL: <https://trac.ffmpeg.org/ticket/8060> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#5917(website:new): applehttp vs hls in documentation
by FFmpeg 04 Aug '19

04 Aug '19

#5917: applehttp vs hls in documentation ---------------------------------+--------------------------------------- Reporter: joshka | Type: defect Status: new | Priority: normal Component: website | Version: unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ---------------------------------+--------------------------------------- Summary of the bug: A little investigation suggested that the applehttp demuxer was renamed to hls a few years ago, leaving the applehttp name as a legacy for backwards compatibility. I was reading into ffmpeg to get an understanding of how this worked and found it a little confusing why this was so. Perhaps a quick doco change is appropriate here, or I'm misunderstanding the nature of the rename. How to reproduce: https://www.ffmpeg.org/ffmpeg-formats.html#applehttp Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/5917> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#8049(undetermined:new): dash muxer does not specify full codec string parameters for AV1
by FFmpeg 03 Aug '19

03 Aug '19

#8049: dash muxer does not specify full codec string parameters for AV1 -------------------------------------+------------------------------------- Reporter: brion | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: av1,dash | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Summary of the bug: When using the dash muxer to produce DASH output containing an AV1 video stream, the codec string is listed only as "av01" without the full parameters, such as "av01.0.04M.08". This results in failure to play in Chrome, where MediaSource.isTypeSupported('video/mp4; codecs="av01"') without those parameters returns false. The parameters should be extracted from the extradata per https://aomediacodec.github.io/av1-isobmff/#codecsparam How to reproduce: {{{ % $ ffmpeg -t 1 -i crowd_run_1080p50.y4m -s 640x360 -strict -2 -c:v libaom-av1 -cpu-used 8 -tile-columns 2 -g 50 -keyint_min 50 -f dash foo.mpd ffmpeg version 4.1.4 Copyright (c) 2000-2019 the FFmpeg developers built with Apple LLVM version 10.0.1 (clang-1001.0.46.4) configuration: --prefix=/usr/local/Cellar/ffmpeg/4.1.4_1 --enable-shared --enable-pthreads --enable-version3 --enable-avresample --cc=clang --host- cflags='-I/Library/Java/JavaVirtualMachines/adoptopenjdk-12.0.1.jdk/Contents/Home/include -I/Library/Java/JavaVirtualMachines/adoptopenjdk-12.0.1.jdk/Contents/Home/include/darwin' --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable- libaom --enable-libbluray --enable-libmp3lame --enable-libopus --enable- librubberband --enable-libsnappy --enable-libtesseract --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable- libopencore-amrwb --enable-libopenjpeg --enable-librtmp --enable-libspeex --enable-videotoolbox --disable-libjack --disable-indev=jack --enable- libaom --enable-libsoxr 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, yuv4mpegpipe, from 'crowd_run_1080p50.y4m': Duration: 00:00:10.00, start: 0.000000, bitrate: 1244162 kb/s Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p(progressive), 1920x1080, SAR 1:1 DAR 16:9, 50 fps, 50 tbr, 50 tbn, 50 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> av1 (libaom-av1)) Press [q] to stop, [?] for help [libaom-av1 @ 0x7fb83f002a00] 1.0.0 [dash @ 0x7fb83f012a00] Opening 'init-stream0.m4s' for writing Output #0, dash, to 'foo.mpd': Metadata: encoder : Lavf58.20.100 Stream #0:0: Video: av1 (libaom-av1), yuv420p, 640x360 [SAR 1:1 DAR 16:9], q=-1--1, 200 kb/s, 50 fps, 12800 tbn, 50 tbc Metadata: encoder : Lavc58.35.100 libaom-av1 Side data: cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1 [dash @ 0x7fb83f012a00] Opening 'chunk-stream0-00001.m4s.tmp' for writing [dash @ 0x7fb83f012a00] Opening 'foo.mpd.tmp' for writingate=N/A speed=0.0205x frame= 50 fps=1.0 q=-0.0 Lsize=N/A time=00:00:00.98 bitrate=N/A speed=0.02x video:88kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown % $ cat foo.mpd <?xml version="1.0" encoding="utf-8"?> <MPD xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:mpeg:dash:schema:mpd:2011" xmlns:xlink="http://www.w3.org/1999/xlink" xsi:schemaLocation="urn:mpeg:DASH:schema:MPD:2011 http://standards.iso.org/ittf/PubliclyAvailableStandards/MPEG- DASH_schema_files/DASH-MPD.xsd" profiles="urn:mpeg:dash:profile:isoff-live:2011" type="static" mediaPresentationDuration="PT1.0S" minBufferTime="PT2.0S"> <ProgramInformation> </ProgramInformation> <Period id="0" start="PT0.0S"> <AdaptationSet id="0" contentType="video" segmentAlignment="true" bitstreamSwitching="true"> <Representation id="0" mimeType="video/mp4" codecs="av01" bandwidth="200000" width="640" height="360" frameRate="50/1"> <SegmentTemplate timescale="12800" initialization="init-stream$RepresentationID$.m4s" media="chunk- stream$RepresentationID$-$Number%05d$.m4s" startNumber="1"> <SegmentTimeline> <S t="0" d="12800" /> </SegmentTimeline> </SegmentTemplate> </Representation> </AdaptationSet> </Period> </MPD> }}} -- Ticket URL: <https://trac.ffmpeg.org/ticket/8049> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#8053(undetermined:new): `-sseof 0`, "-sseof value must be negative; aborting"
by FFmpeg 02 Aug '19

02 Aug '19

#8053: `-sseof 0`, "-sseof value must be negative; aborting" -------------------------------------+------------------------------------- Reporter: gdgsdg123 | Type: | enhancement Status: new | Priority: minor Component: | Version: git- undetermined | master Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Build from: https://ffmpeg.zeranoe.com/builds/win64/static/ffmpeg-20190731 -42a2edc-win64-static.zip {{{ C:\>ffmpeg -sseof 0 -i "!TEMP.avi" -frames 1 -compression_level 10 -pred mixed -pix_fmt rgb24 -sws_flags spline+accurate_rnd+full_chroma_int "PNG.png" ffmpeg version N-94431-g42a2edcc1d Copyright (c) 2000-2019 the FFmpeg developers built with gcc 9.1.1 (GCC) 20190716 configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable- fontconfig --enable-gnutls --enable-iconv --enable-libass --enable- libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --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-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable- nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt libavutil 56. 32.100 / 56. 32.100 libavcodec 58. 55.100 / 58. 55.100 libavformat 58. 30.100 / 58. 30.100 libavdevice 58. 9.100 / 58. 9.100 libavfilter 7. 58.100 / 7. 58.100 libswscale 5. 6.100 / 5. 6.100 libswresample 3. 6.100 / 3. 6.100 libpostproc 55. 6.100 / 55. 6.100 -sseof value must be negative; aborting }}} [[BR]] Well... in the [https://ffmpeg.org/ffmpeg-all.html#Main-options doc]: > -sseof position (input) > Like the -ss option but relative to the "end of file". That is negative values are earlier in the file, 0 is at EOF. [[BR]] Failed to see the point of preventing `-sseof 0` though... -- Ticket URL: <https://trac.ffmpeg.org/ticket/8053> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 2

#8052(avfilter:new): Option 'pad_dur' not found
by FFmpeg 01 Aug '19

01 Aug '19

#8052: Option 'pad_dur' not found ----------------------------------+---------------------------------- Reporter: oskycar | Type: defect Status: new | Priority: normal Component: avfilter | Version: 4.1 Keywords: pad_dur | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | ----------------------------------+---------------------------------- Summary of the bug: I used brew to install ffmpeg 4.1.4 on mac ,and when run the fllowing command: ffmpeg -report -loglevel 99 -i ~/Desktop/zz.wav -filter_complex '[0:0]adelay=1000|500[hp];[hp]apad=pad_dur=44100[out]' -map '[out]' s3.wav I got an error the fllowing error Parsed_apad_1 @ 0x7fddadd00cc0] Option 'pad_dur' not found [AVFilterGraph @ 0x7fddadd016c0] Error initializing filter 'apad' with args 'pad_dur=44100' How to reproduce: {{{ % ffmpeg -report -loglevel 99 -i ~/Desktop/zz.wav -filter_complex '[0:0]adelay=1000|500[hp];[hp]apad=pad_dur=44100[out]' -map '[out]' s3.wav ffmpeg version 4.1.4 built on ... }}} Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8052> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 3