[Libav-user] Questions regarding change in lib behaviour for mpeg2 fourCCs in mov
Paul B Mahol
onemda at gmail.com
Wed Oct 30 12:32:23 CET 2013
On 10/30/13, Robert Krueger <krueger at lesspain.de> wrote:
> Hi,
>
> a recent update of our application showed that setting the codec_tag
> for muxing no longer worked for mpeg2. AFAICS the reason is commit
> 713dcdbfcbaa305050ae6362e5131e0e2e705135.
>
> If I see this correctly, this means if I disagree for whatever reason
> with the fourcc that ffmpeg decodes on, my application has no way to
> override it. Is this intentional? Couldn't one imagine a case where I
> wanted or have to make that decision outside, be it to fulfill some
> proprietary requirements?
Such as?
>
> Is the behaviour regarding muxer and codec_tag defined somewhere?
>
> Thanks for any insights on this.
IIRC that commit is there for some reason.
If that commit disabled something which was possible before than
that may be bad/good.
>
> Robert
> _______________________________________________
> Libav-user mailing list
> Libav-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/libav-user
>
More information about the Libav-user
mailing list