[FFmpeg-devel] [PATCH] avfilter: Enable in MP4 container both AMR-NB and AMR-WB
bkirnum at gmail.com
Mon May 22 21:06:46 EEST 2017
I resolved our issue with the MOV changes and now have H.264 / AMR-NB and
H.264 / AMR-WB recording to MOV using non-patched FFmpeg. The former plays
in both QuickTime and the Windows 10 'Movies & TV' app, video and audio.
The MOV containing AMR-WB plays video only in QuickTime and neither in the
Windows 10 'Movies & TV' app. This is equivalent to the MP4 files we
record with our proposed patch.
On Mon, May 22, 2017 at 11:41 AM, Bob Kirnum <bkirnum at gmail.com> wrote:
> The MOV issue I am working on is likely an issue with our framework. I
> hope to have this resolved soon.
> Assuming MOV works, we still would like to use MP4 with AMR NB/WB. What
> is the difficulty with enabling this? Seems it has been updated to accept
> Opus recently.
> On Fri, May 19, 2017 at 10:19 AM, Bob Kirnum <bkirnum at gmail.com> wrote:
>> I tried adding support for MOV to see if I could use unpatched FFmpeg
>> libraries. Although both AMR-NB and AMR-WB do appear to record to MOV,
>> neither result plays properly using QuickTime or Windows 'Movies & TV'
>> app. The MOV (H.264 / AMR-NB) sometimes audio plays, sometimes video.
>> Appears that the MOV contains two moov atoms, one for audio one for video.
>> Similar is true for AMR-WB, however, there is never audio as QuickTime and
>> Windows app do not support AMR-WB.
>> I also tried both MP4 and MOV using linear PCM (s16le @ 16 kHz). MP4
>> rejects the codec, MOV seems to have a similar issue as AMR, only video
>> I am using the exact same code as we use for MP4 so I am not sure what we
>> are doing wrong. Any suggestions for how to debug this?
>> The recorded files are here . . .
>> On Thu, May 18, 2017 at 8:34 AM, Bob Kirnum <bkirnum at gmail.com> wrote:
>>> Hey Carl,
>>> I am not aware of non-FFmpeg apps which can record to MP4 containing
>>> AMR. That's not to say one does not exist.
>>> I would agree that we likely need no changes for playing these MP4 files.
>>> The MP4 requirement was from one of our customers.
>>> On Wed, May 17, 2017 at 8:01 PM, Carl Eugen Hoyos <ceffmpeg at gmail.com>
>>>> 2017-05-17 23:26 GMT+02:00 Bob Kirnum <bkirnum at gmail.com>:
>>>> > Did not realize the files I shared were too large. I copied them to a
>>>> > shared Google Drive here . . .
>>>> The question was if you have files that were not created with FFmpeg.
>>>> Anyway: Since both files can be decoded with unpatched FFmpeg, I
>>>> assume the demuxing hunk of your patch is unneeded, correct?
>>>> Any reason why you cannot use mov for muxing?
>>>> Carl Eugen
>>>> ffmpeg-devel mailing list
>>>> ffmpeg-devel at ffmpeg.org
More information about the ffmpeg-devel