On Mon, Mar 21, 2016 at 6:32 PM, Robert Krüger wrote:
>
>
> On Mon, Mar 21, 2016 at 5:31 PM, Carl Eugen Hoyos
> wrote:
>
>> Robert Krüger lesspain.de> writes:
>>
>> > major_brand : mp42
>>
>> > Stream #0:1(und): Audio: pcm_s16be (twos /
On Mon, Mar 21, 2016 at 5:31 PM, Carl Eugen Hoyos wrote:
> Robert Krüger lesspain.de> writes:
>
> > major_brand : mp42
>
> > Stream #0:1(und): Audio: pcm_s16be (twos / 0x736F7774)
>
> If this is not invalid (I don't know) than the issue remains
> that FFmpeg does
On Mon, Mar 21, 2016 at 4:59 PM, Moritz Barsnick wrote:
> On Mon, Mar 21, 2016 at 15:59:04 +0100, Robert Krüger wrote:
>
> > the mp4 muxer currently does not accept pcm in mp4. However, there are
> > several cameras out there, that produce such files. Would it be possible
> to
On Mon, Mar 21, 2016 at 15:59:04 +0100, Robert Krüger wrote:
> the mp4 muxer currently does not accept pcm in mp4. However, there are
> several cameras out there, that produce such files. Would it be possible to
> support this option when using -strict -2?
If the cameras are doing it wrong, why
Hi,
the mp4 muxer currently does not accept pcm in mp4. However, there are
several cameras out there, that produce such files. Would it be possible to
support this option when using -strict -2? This way a user could create
non-spec-conformant files but it would not happen, when not explicitly