[FFmpeg-trac] #7768(undetermined:new): ffmpeg does not handle HTTP read errors (e.g. from cloud storage)

FFmpeg trac at avcodec.org
Thu Mar 7 03:38:14 EET 2019

#7768: ffmpeg does not handle HTTP read errors (e.g. from cloud storage)
             Reporter:  dprestegard  |                    Owner:
                 Type:  enhancement  |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:  http         |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |

Comment (by dprestegard):

 Here's a sample command:

 ffmpeg -report -loglevel debug -y -i
 NR_51_LTRT_UHD_20160913_OV_01.mxf" -pix_fmt yuv420p10 -c:v libx265
 -threads 1 -preset veryslow -crf 12 test_01.mp4

 This reads a very large (715 GB) j2k mxf file from one of Netflix's public
 S3 buckets and encodes it into HEVC. I'm running this now and expect it to
 time out in the next few hours. I'll provide the full debug report from

 Probing the source reveals the following:

 Duration: 00:11:58.93, start: 0.000000, bitrate: 8548764 kb/s
     Stream #0:0, 1, 1001/60000: Video: jpeg2000, 1 reference frame,
 rgb48le(12 bpc, progressive), 3840x2160, 0/1, lossless, SAR 1:1 DAR 16:9,
 59.94 tbr, 59.94 tbn, 59.94 tbc
       file_package_name: File Package: PROTOTYPE SMPTE ST 422 / ST 2067-5
 frame wrapping of JPEG 2000 codestreams with HDR metadata
       track_name      : PHDR Image Track

 So, we should get a file that's 00:11:58.93 in duration.

Ticket URL: <https://trac.ffmpeg.org/ticket/7768#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list