[FFmpeg-user] Reversed order of video audio after audio merging (0:0 audio, 0:1 video)

Christoph Gerstbauer christophgerstbauer at gmail.com
Mon Jun 2 15:00:29 CEST 2014

Am 02.06.2014 14:01, schrieb Carl Eugen Hoyos:
> Christoph Gerstbauer <christophgerstbauer <at> gmail.com> writes:
>>> Seeking in large files with WMP fails sometimes,
>>> indicating that (afaict) something is wrong with
>>> the ODML index.
>> Yes, this bug I know:
>> The problem happens every time when the AUDIO DATA
>> in the AVI is bigger than 2 Gigabytes
> This is another bug.
>> which ffmpeg version 2.1 the problem is gone.
> Sorry: Is there this (other) bug or not?
> I don't understand...
> Unrelated:
> If you do "huge tests" and you find problems and
> you do not report them, it is unlikely that they
> get fixed. Do you agree?
> [...]
They were reported, not from me but from my collegue Tobias Rapp. As 
seen here:

> Again:
> I had not realized you can use ffv1 in avi with
> third party applications. You have explained that
> it works fine and I did - iirc - answer that I
> understand now (but not before).
>> So, to get the things straight,
>> the main bugs are:
>> 1.) ODML index wrong (when audio is bigger than 2gb?)
> As said, please elaborate.
> Iiuc, you write above that this is not reproducible.
>> 2.) Interlaced Flag is always set to progressive
> Please point me to the report.
I cant because, I did not menationed this bug at first.
Tim Nicholson said:

> One significant one from your point of view might
> be the failure to set the interlaced flag if
> relevant, it always flags material as progressive.


At my point of view there were/are these problems with AVI:

1.) Carl Eugen mentioned: Seeking in large files with WMP fails 
sometimes, indicating that (afaict) something is wrong with the ODML index.
Carl, is there a ticket exisitng for this bug?

2.) Christoph Gerstbauer mentioned: Problem with AVI files where audio 
data is bigger than 2gb -> FIXED with ffmpeg version 2.1 -> bug is not 
reproducible anymore
     FIX INFO: 

3.) Tim Nicholson mentioned INTERLACED FLAG problem in AVI:
     As I can see, the problem Tom mention regard to the "vprp chunk" -> 
The "FieldPerFrame" value is always "1".
     I never saw a AVI file with an value of "2" (interlaced). And I do 
not know about any ticket about this bug.

Chunk(vprp) {
             ChunkType: VideoPropertiesHeaderChunk
             Position: 0x000010F0, Size: 68
             VideoFormatToken: 0, VideoStandard: 0
             VerticalRefreshRate: 25, HTotal: 1920, VTotal: 1080
             FrameAspectRatio: 0x00100009 (16:9), FrameWidth: 1920, 
FrameHeight: 1080
             FieldPerFrame: 1
                CompressedBMWidth: 1920, CompressedBMHeight: 1080
                ValidBMWidth: 1920, ValidBMHeight: 1080
                ValidBMXOffset: 0, ValidBMYOffset: 0
                VideoXOffsetInT: 0, VideoYValidStartLine: 0


More information about the ffmpeg-user mailing list