I am wondering if I should file a bug report about the MOV output. Open questions in that vein, though, are:
- Is it a bug that mpg2 and mpgv cause MOV output to fail or is that correct behavior?
There seem to be numerous possible tags in use for MPEG-2 video, in particular
Now, ffmpeg fails with e.g. "Tag mpgv/0x7667706d incompatible with
output codec id '2' (m2v1)" when the output is MOV and either
mpgv is specified:
ffmpeg ... -vcodec mpeg2video -f mov ... # succeeds (m1v1) ffmpeg ... -vcodec mpeg2video -vtag mp2v -f mov ... # succeeds ffmpeg ... -vcodec mpeg2video -vtag mpg2 -f mov ... # fails ffmpeg ... -vcodec mpeg2video -vtag mpgv -f mov ... # fails
All of those succeed for AVI. Ffmpeg's default tag for MPEG-2 in AVIs is
Part of a bug report that I am writing for ffmpeg's MOV output handling may include the
mpgv failure behavior (with the desired behavior being success), but before I do that I need to be certain that this behavior is a bug rather than appropriate behavior.
So my question boils down to this: Are
mpgv valid, allowable alternative tags for MPEG-2 video in an MOV file, and are there others? I am looking for official Apple sources and MOV specifications rather than anecdotal evidence or lists of generally observed FourCC's / codec IDs.
I know that, at least according to Wikipedia, MPEG-2 video in an MOV is an acceptable combination, I'm just not sure what the acceptable set of codec tags are in MOVs. This question is not about the "correct" MPEG-2 ID in general cases, it is about the allowable variants specifically in MOVs.