Changes between Initial Version and Version 9 of Ticket #2809


Ignore:
Timestamp:
Jul 25, 2013, 10:18:35 PM (6 years ago)
Author:
llogan
Comment:

Please confirm if native AAC encoder also fails:

ffmpeg -i input -c:a aac -strict -2 -ar 44100 -vn output.m4a

Does remuxing the working output from faac produce a non-working file?

ffmpeg -i faacoutput -c copy output.m4a

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2809

    • Property Keywords nintendo unplayable encoding removed
    • Property Priority changed from important to normal
    • Property Version changed from 1.2.1 to git-master
    • Property Summary changed from AAC files encoded with ffmpeg/avconv do not play on Nintendo devices to AAC output does not play on Nintendo devices
  • Ticket #2809 – Description

    initial v9  
    11Summary of the bug: When converting files of any input format to AAC audio (in .mp4, .m4a, or .aac containers), the files will not play on Nintendo DSi/DSi XL/3DS/3DS XL. The files are detected, but when selected, they display "Could not play." It does not matter which AAC encoder is used. The fact that files encoded with libfaac in ffmpeg fail to play while the standalone faac works flawlessly suggests a problem in ffmpeg rather than the encoder.
    22
    3 How to reproduce: Convert any file to AAC audio with frequency 41000-48000 Hz and bitrate 16-320 kbps, copy to SD card, and attempt to play on a Nintendo handheld. One of the commands that I tried is listed below, but any variation (such as with avconv command and -c:a aac and -strict -2 parameters) should produce the same results.
     3How to reproduce: Convert any file to AAC audio with frequency 41000-48000 Hz and bitrate 16-320 kbps, copy to SD card, and attempt to play on a Nintendo handheld. One of the commands that I tried is listed below, but any variation (such as with ffmpeg command and -c:a aac and -strict -2 parameters) should produce the same results.
    44
    55{{{