[FFmpeg-trac] #3842(avformat:new): AAC (mp4a) DASH takes abnormally long to detect (~4 - 6s)

FFmpeg trac at avcodec.org
Sun Aug 10 14:19:12 CEST 2014


#3842: AAC (mp4a) DASH takes abnormally long to detect (~4 - 6s)
---------------------------------+------------------------------------
             Reporter:  viperfx  |                    Owner:
                 Type:  defect   |                   Status:  new
             Priority:  normal   |                Component:  avformat
              Version:  2.2.4    |               Resolution:
             Keywords:  mov      |               Blocked By:
             Blocking:           |  Reproduced by developer:  0
Analyzed by developer:  0        |
---------------------------------+------------------------------------

Comment (by viperfx):

 I should note that I am compiling FFmpeg on iOS so those flags I posted a
 slightly different to what I have configured on the iOS app.

 Snippet of the configure flags.
 {{{
         ./configure --disable-programs --disable-shared --enable-static
 --enable-pic --enable-small --enable-openssl ${DEBUG_CONFIG_ARGS} \
         --disable-decoders --enable-decoder=aac --enable-decoder=h264
 --enable-decoder=vorbis \
         --disable-encoders --enable-encoder=aac \
         --disable-demuxers --enable-demuxer=aac --enable-demuxer=mov
 --enable-demuxer=matroska --enable-demuxer=h264 \
         --disable-muxers --enable-muxer=mov --enable-muxer=mp4 --enable-
 muxer=hls --enable-muxer=h264 \
         --disable-filters --disable-doc
 }}}

 As gjdfgh said, I recieved a suggestion of disabling indexing to make the
 seeking faster. It does indeed make the file open faster, almost instantly
 through HTTP infact. However, the issue is that it thinks that the
 duration of the file is 10s. It does not seem to detect the full duration.
 Therefore, for a UI perspective I cannot seek the audio track since I do
 not know the full duration of the file. The good thing is that the audio
 plays till the end of the file.

 cehoyos: The issue is that it does seek to the end of the file when
 opening. This is evident when using ffmpeg -i to test with an HTTP URL
 rather than a local file. Using avformat_open_input call, takes >~4s.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3842#comment:10>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list