[FFmpeg-cvslog] r25840 - trunk/tests/ref/fate/h264-conformance-frext-frext_mmco4_sony_b

Baptiste Coudurier baptiste.coudurier
Mon Nov 29 02:48:23 CET 2010


On 11/28/10 5:39 PM, Michael Niedermayer wrote:
> On Mon, Nov 29, 2010 at 12:09:30AM +0100, bcoudurier wrote:
>> Author: bcoudurier
>> Date: Mon Nov 29 00:09:30 2010
>> New Revision: 25840
>>
>> Log:
>> Update fate h264 test due to r25824, this file has 2 frames delay
>>
>> Modified:
>>    trunk/tests/ref/fate/h264-conformance-frext-frext_mmco4_sony_b
>>
>> Modified: trunk/tests/ref/fate/h264-conformance-frext-frext_mmco4_sony_b
>> ==============================================================================
>> --- trunk/tests/ref/fate/h264-conformance-frext-frext_mmco4_sony_b	Sun Nov 28 22:17:39 2010	(r25839)
>> +++ trunk/tests/ref/fate/h264-conformance-frext-frext_mmco4_sony_b	Mon Nov 29 00:09:30 2010	(r25840)
>> @@ -1,60 +1,59 @@
>> -0, 0, 152064, 0x24846654
>> -0, 3600, 152064, 0xd33945be
>> -0, 7200, 152064, 0x961cbbfb
>> -0, 10800, 152064, 0x91eb854d
> [...]
>> +0, 0, 152064, 0xd33945be
>> +0, 3600, 152064, 0x961cbbfb
>> +0, 7200, 152064, 0x91eb854d
> [...]
> 
> This change looks incorrect.
> The bitstream documentation also mentions that this file is supposed to contain
> 60 frames and not 59 frames

Yes, -vsync 0 outputs 60 frames, and previously it would only output 59
frames.

-- 
Baptiste COUDURIER
Key fingerprint                 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
FFmpeg maintainer                                  http://www.ffmpeg.org



More information about the ffmpeg-cvslog mailing list