Log in

View Full Version : avi h264 with audio aac conv to mov (ffmpeg)


djembe
28th November 2012, 16:18
ffmpeg fails to convert audio stream while converting to mov.
options i am using are:
-y -i -b 7600k -r 29.97 -ab 128k -ar 48000 -ac 2

why this fails ?

error log is:

Error # 1
----------
Date & Time: 2012-11-28 / 13:36:10
ExitCode: 1
Input #0, avi, from 'C:Documents and SettingsJaMoje dokumentyMoje obrazypracticazimaIMAG0026.AVI':
Duration: 00:00:09.90, start: 0.000000, bitrate: 4281 kb/s
Stream #0.0: Video: h264, yuv420p, 1280x720 [PAR 1:1 DAR 16:9], 29.97 tb(r)
Stream #0.1: Audio: libfaad, 48000 Hz, stereo, s16, 128 kb/s
Output #0, mov, to 'C:Documents and SettingsJaMoje dokumentyMoje obrazypracticazimaIMAG0026.mov':
Stream #0.0: Video: mpeg4, yuv420p, 1280x720 [PAR 1:1 DAR 16:9], q=2-31, 7600 kb/s, 29.97 tb(c)
Stream #0.1: Audio: libfaac, 48000 Hz, stereo, s16, 128 kb/s
Stream mapping:
Stream #0.0 -> #0.0
Stream #0.1 -> #0.1
[libfaad @ 01378820]faac: frame decoding failed: Maximum number of bitstream elements exceeded
Error while decoding stream #0.1
[libfaad @ 01378820]faac: frame decoding failed: Unexpected channel configuration change
Error while decoding stream #0.1
[h264 @ 01378070]B picture before any references, skipping
[h264 @ 01378070]decode_slice_header error
[h264 @ 01378070]no frame!
Error while decoding stream #0.0
[libfaad @ 01378820]faac: frame decoding failed: Unexpected channel configuration change
Error while decoding stream #0.1
[libfaad @ 01378820]faac: frame decoding failed: Unexpected channel configuration change
Error while decoding stream #0.1
[h264 @ 01378070]B picture before any references, skipping
[h264 @ 01378070]decode_slice_header error
[h264 @ 01378070]no frame!
Error while decoding stream #0.0
[libfaad @ 01378820]faac: frame decoding failed: Unexpected channel configuration change
Error while decoding stream #0.1
[libfaad @ 01378820]faac: frame decoding failed: Unexpected channel configuration change
Error while decoding stream #0.1

fvisagie
1st December 2012, 10:11
My guess would be that either your input file is damaged/non-standard, or the particular version ffmpeg you have has trouble handling it properly. So the question is what other decoders or players do with this input?

If the evidence seems to point at ffmpeg, what I normally do is see if a more recent version no longer has that bug, or use something like Avidemux to do an intermediate re-encode (of the audio in this case) hoping that ffmpeg can handle that.