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

#8698(undetermined:new): ERROR: ffmpeg exited with code 3221225477
by FFmpeg 02 Jun '20

02 Jun '20

#8698: ERROR: ffmpeg exited with code 3221225477 -------------------------------------+------------------------------------- Reporter: Kkabadd | Type: defect Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Hi, First off, I dont understand about codes, so I am sorry if this a stupid question (and for my bad english). I donwload videos from mewatch from youtube-dl and everything is ok but with this video I cant. I appreciate the help. https://www.mewatch.sg/en/series/through-it-all/ep5/300718 C:\Users\Esme\Videos\DD\YY>youtube-dl https://www.mewatch.sg/en/series /through-it-all/ep5/300718 [toggle] 300718: Downloading video page [toggle] 300718: Downloading video info json [toggle] 300718: Downloading SS_Web ISM manifest [toggle] 300718: Downloading SS_TV ISM manifest [toggle] 300718: Downloading DASH_Mobile MPD manifest [toggle] 300718: Downloading DASH_Web MPD manifest [toggle] 300718: Downloading DASH_TV MPD manifest [toggle] 300718: Downloading HLS_Mobile m3u8 information [toggle] 300718: Downloading HLS_Web m3u8 information [toggle] 300718: Downloading HLS_TV m3u8 information [toggle] 300718: Downloading DASH_Tablet MPD manifest [toggle] 300718: Downloading HLS_Tablet m3u8 information [toggle] 300718: Downloading DASH_HBBTV MPD manifest WARNING: Failed to download DASH_HBBTV MPD manifest: HTTP Error 404: Not Found [toggle] 300718: Downloading DASH_TV_4K MPD manifest [download] Destination: Through It All 海的儿子-300718.mp4 ffmpeg version git-2020-05-28-c0f01ea Copyright (c) 2000-2020 the FFmpeg developers built with gcc 9.3.1 (GCC) 20200523 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-libsrt --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-libvmaf --enable-libvorbis --enable-libvo- amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable- libaom --disable-w32threads --enable-libmfx --enable-ffnvcodec --enable- cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf libavutil 56. 49.100 / 56. 49.100 libavcodec 58. 89.100 / 58. 89.100 libavformat 58. 43.100 / 58. 43.100 libavdevice 58. 9.103 / 58. 9.103 libavfilter 7. 83.100 / 7. 83.100 libswscale 5. 6.101 / 5. 6.101 libswresample 3. 6.100 / 3. 6.100 libpostproc 55. 6.100 / 55. 6.100 [hls @ 000001d97910cb00] Skip ('#EXT-X-ALLOW-CACHE:YES') [hls @ 000001d97910cb00] Skip ('#EXT-X-VERSION:5') ERROR: ffmpeg exited with code 3221225477 -- Ticket URL: <https://trac.ffmpeg.org/ticket/8698> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 8

#8693(avformat:new): DASH HTTP PUT fails with http_persistent and connection closed
by FFmpeg 01 Jun '20

01 Jun '20

#8693: DASH HTTP PUT fails with http_persistent and connection closed --------------------------------------+---------------------------------- Reporter: chris.ribble | Type: defect Status: new | Priority: normal Component: avformat | Version: 4.2 Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | --------------------------------------+---------------------------------- Summary of the bug: When live streaming (HLS) with a persistent HTTP connection, if the web server closes the connection ffmpeg shuts down. How to reproduce: Streaming to an Apache web server with "KeepAlive On" and "MaxKeepAliveRequests 10", ffmpeg will fail on the 11th PUT request when Apache closes the TCP connection. Streaming to Tomcat service with default configuration, ffmpeg will fail on the 101st PUT request when Tomcat closes the connection. `ffmpeg -report -i /home/chris/Desktop/B3__1080p29_x264_3_1080-full.mp4 -c copy -f dash -seg_duration 2 -http_persistent 1 http://localhost:8080/Manifest.mpd` Output: {{{ [http @ 0x55e4fe65d780] Opening 'http://localhost:8080/chunk- stream1-00100.m4s' for writing [http @ 0x55e4fe639780] URL read error: End of file [http @ 0x55e4fe748a40] Opening 'http://localhost:8080/Manifest.mpd' for writing [http @ 0x55e4fe66e780] Opening 'http://localhost:8080/chunk- stream0-00101.m4s' for writing [dash @ 0x55e4fe658500] Unable to open http://localhost:8080/chunk- stream0-00101.m4s for writing: Broken pipe av_interleaved_write_frame(): Broken pipe [http @ 0x55e4fe65d780] Opening 'http://localhost:8080/chunk- stream1-00101.m4s' for writing [dash @ 0x55e4fe658500] Unable to open http://localhost:8080/chunk- stream1-00101.m4s for writing: Connection reset by peer [http @ 0x55e4fe748a40] Opening 'http://localhost:8080/Manifest.mpd' for writing Error writing trailer of http://localhost:8080/Manifest.mpd: Connection reset by peer frame= 6031 fps=0.0 q=-1.0 Lsize=N/A time=00:03:21.20 bitrate=N/A speed= 965x video:84499kB audio:3186kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown Conversion failed! }}} This was fixed for HLS by https://trac.ffmpeg.org/ticket/7975 and I have attempted to create a similar patch for libavformat/dashenc.c (attached). I tested the patch against master and also against the 4.2 branch (with f267a2ac9c740c77cee2f2c5fd2bd9bc048768b1 also applied) and it seems to fix the problem, although I am no C expert and I'm sure there are flaws in my patch. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8693> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 4

#8701(undetermined:new): Increase a reliability of capturing a video against disruptions
by FFmpeg 01 Jun '20

01 Jun '20

#8701: Increase a reliability of capturing a video against disruptions -------------------------------------+------------------------------------- Reporter: user725 | Type: | enhancement Status: new | Priority: normal Component: | Version: undetermined | unspecified Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+------------------------------------- Assume, you have been capturing video from a screen for three hours and eventually you're about to finish but any issue occurs killing your application or entire system (Windows BSOD, electricity cut off, out of memory (RAM), therefore a crash report). In this case you've lost your three hours of your valuable work because the captured video is corrupted. Since capturing a video is lasting process that highly likely will take place it would be reasonable to prevent users from such a disruptions to avoid painful loss of data and angry user reports. Is it possible to prevent this issue? When I kill ffmpeg during the capturing process I have a video file that gives an error on opening. -- Ticket URL: <https://trac.ffmpeg.org/ticket/8701> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker

1 1