[FFmpeg-trac] #2307(undetermined:new): Stream segmenter bug if total recorded length > 12 hours

FFmpeg trac at avcodec.org
Thu Mar 28 13:25:38 CET 2013

#2307: Stream segmenter bug if total recorded length > 12 hours
             Reporter:  dgillier     |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  1.1.3        |  undetermined
             Keywords:  segment,     |               Resolution:
  duration                           |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |

Comment (by cehoyos):

 Replying to [comment:16 dgillier]:
 > The problem with $ ffmpeg -f lavfi -i testsrc -f s16le -i /dev/zero
 -vcodec mpeg4 -vb 400000 -strict -2 -acodec aac -f segment -segment_time
 1800 -map 0 -map 1 outsegment-%03d.mp4 is that it is supposed to create a
 segment every 1800 seconds (30min) and in fact it creates one every 60
 seconds. And the result files are declared of having 30min lenght (but
 actually recorded 1min of content)...

 Which application are you using to test? I only tested ffplay and MPlayer,
 but I cannot imagine an application that would play these 30min samples in
 one minute.

 Or do you really mean you are unhappy that it took FFmpeg only one minute
 (on your hardware) to encode a 30 minute file? The reason I ask is that I
 assume your original report (using udp) will take many hours to reproduce
 and I have the feeling that most developers will refuse to wait so long
 that is why I suggested to test with a file (it is already difficult
 enough to encode 25 - or twelve - hours with a file as input but easier
 than via udp) and with -i testsrc.

 > Anyway my point is not on using testsrc...

 The point is to find out how to reproduce the problem without using udp
 (or huge files) or clarify that it cannot be reproduced with testsrc.

 > I tested with no audio as you requested.
 > Result is a bit different but still not ok.
 > As with audio, segmented .mp4 files are not readable after the first

 Is this the issue you originally reported or a different one? Iirc,
 originally only the 25th segment was incorrect or did I misunderstand?

Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2307#comment:17>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list