#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 cehoyos):
Replying to [ticket:3842 viperfx]:
> {{{
> configuration: --prefix=/usr/local/Cellar/ffmpeg/2.2.1 --enable-shared
--enable-pthreads --enable-gpl --enable-version3 --enable-nonfree
--enable-hardcoded-tables --enable-avresample --enable-vda --cc=clang
--host-cflags= --host-ldflags= --enable-libx264 --enable-libfaac --enable-
libmp3lame --enable-libxvid --enable-ffplay --enable-libfdk-aac --enable-
openssl
> }}}
Unrelated: {{{--enable-vda}}} and {{{--enable-ffplay}}} do not work the
way you seem to believe these options work, please remove them
({{{configure}}} will silently ignore those options if SDL or vda are not
available, if they are available, ffplay and vda will be enabled
automatically). I also believe it is better to remove {{{--host-cflags=
--host-ldflags=}}} since they might lead to confusion.
Is {{{--cc=clang}}} necessary? It looks redundant to me.
Most users prefer libfdk over libfaac, is there a particular reason why
you enable libfaac?
I am curious: Did you test {{{--enable-hardcoded-tables}}}? (I never did.)
Does it have any measurable effect?
--
Ticket URL: <https://trac.ffmpeg.org/ticket/3842#comment:5>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://avcodec.org/mailman/listinfo/ffmpeg-trac
