virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2024-12-12 19:18:44 +02:00
Code Issues Releases Activity
19802d170a
FFmpeg/tests/ref/fate/h264-conformance-frext-hpcamapalq_bcrm_b

306 lines
17 KiB
Plaintext
Raw Normal View History

frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
#tb 0: 1/25
avformat/framecrc: enable new output Reviewed-by: Michael Niedermayer <michael@niedermayer.cc> Signed-off-by: James Almer <jamrial@gmail.com>
2016-04-13 16:18:59 +02:00
#media_type 0: video
#codec_id 0: rawvideo
#dimensions 0: 352x288
#sar 0: 0/1
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 1, 1, 1, 152064, 0xf8248ceb
0, 2, 2, 1, 152064, 0xb6204c81
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 2, 2, 1, 152064, 0x22fb1737
0, 3, 3, 1, 152064, 0xce8c3fd7
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 5, 5, 1, 152064, 0xee88cedc
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 5, 5, 1, 152064, 0x1d4209ca
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 7, 7, 1, 152064, 0x6fb15238
0, 8, 8, 1, 152064, 0x505200c2
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 8, 8, 1, 152064, 0xb73574ba
0, 9, 9, 1, 152064, 0x0586a097
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 11, 11, 1, 152064, 0xed50fe02
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 11, 11, 1, 152064, 0x222221ab
0, 12, 12, 1, 152064, 0x8afefd46
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 14, 14, 1, 152064, 0x6832c5cc
0, 15, 15, 1, 152064, 0xba4c8110
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 15, 15, 1, 152064, 0x95c07e1e
0, 16, 16, 1, 152064, 0xc5d6fde9
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 18, 18, 1, 152064, 0xe75a4921
0, 19, 19, 1, 152064, 0x53b61688
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 19, 19, 1, 152064, 0x0335424b
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 21, 21, 1, 152064, 0x621742c7
0, 22, 22, 1, 152064, 0x4f69f41b
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 22, 22, 1, 152064, 0x6b3f65d7
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 24, 24, 1, 152064, 0x8dfde04f
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 24, 24, 1, 152064, 0x30750ff5
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 26, 26, 1, 152064, 0xe3d70f3c
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 26, 26, 1, 152064, 0x0c1af825
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 28, 28, 1, 152064, 0x58a53935
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 28, 28, 1, 152064, 0xc63d9e98
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 30, 30, 1, 152064, 0xa85fdc48
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 30, 30, 1, 152064, 0x01bb9784
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 32, 32, 1, 152064, 0xdd5cb509
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 32, 32, 1, 152064, 0x29ae7d2b
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 34, 34, 1, 152064, 0xdb08593e
0, 35, 35, 1, 152064, 0x372d5d4e
0, 36, 36, 1, 152064, 0x31522664
0, 37, 37, 1, 152064, 0x3f13f335
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 37, 37, 1, 152064, 0xfd10c19a
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 39, 39, 1, 152064, 0xef728975
0, 40, 40, 1, 152064, 0x8e79234d
0, 41, 41, 1, 152064, 0x47022791
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 41, 41, 1, 152064, 0x1ef9d297
0, 42, 42, 1, 152064, 0x77bf9738
0, 43, 43, 1, 152064, 0xd6bc8f03
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 45, 45, 1, 152064, 0x283ded4a
0, 46, 46, 1, 152064, 0xd87098d1
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 46, 46, 1, 152064, 0x300077a2
0, 47, 47, 1, 152064, 0x30ffbea4
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 49, 49, 1, 152064, 0x5dc5356b
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 49, 49, 1, 152064, 0x31cce185
0, 50, 50, 1, 152064, 0x47fc9148
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 52, 52, 1, 152064, 0x1641491e
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 52, 52, 1, 152064, 0x2184937d
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 54, 54, 1, 152064, 0x126eb74a
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 54, 54, 1, 152064, 0x25c07593
0, 55, 55, 1, 152064, 0xb1294e7e
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 57, 57, 1, 152064, 0x8b35f45d
0, 58, 58, 1, 152064, 0x54765025
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 58, 58, 1, 152064, 0x1d17e901
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 60, 60, 1, 152064, 0xaeab358d
0, 61, 61, 1, 152064, 0xf682c91f
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 61, 61, 1, 152064, 0x0b4c9b06
0, 62, 62, 1, 152064, 0x45f326dc
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 64, 64, 1, 152064, 0x132eeda3
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 64, 64, 1, 152064, 0x3c9b8e16
0, 65, 65, 1, 152064, 0x1be133c1
0, 66, 66, 1, 152064, 0xfa876720
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 68, 68, 1, 152064, 0x1666cdb8
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 68, 68, 1, 152064, 0x362f418f
0, 69, 69, 1, 152064, 0x926b4a96
0, 70, 70, 1, 152064, 0xee3da1df
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 72, 72, 1, 152064, 0xc11f025d
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 72, 72, 1, 152064, 0x9ba62c19
0, 73, 73, 1, 152064, 0x0d66194f
0, 74, 74, 1, 152064, 0x2fd09340
0, 75, 75, 1, 152064, 0x3dfb9e4d
0, 76, 76, 1, 152064, 0xa3192ce6
0, 77, 77, 1, 152064, 0x6bfce0e1
0, 78, 78, 1, 152064, 0x3b7c5286
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 80, 80, 1, 152064, 0xb52f4bf5
0, 81, 81, 1, 152064, 0x30870027
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 81, 81, 1, 152064, 0x6f8e71c3
0, 82, 82, 1, 152064, 0x8d41b09a
0, 83, 83, 1, 152064, 0xc1ff1d05
0, 84, 84, 1, 152064, 0xca54125c
0, 85, 85, 1, 152064, 0x3342d823
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 87, 87, 1, 152064, 0xcc4a7542
0, 88, 88, 1, 152064, 0x21fc9a9d
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 88, 88, 1, 152064, 0x91587574
0, 89, 89, 1, 152064, 0x30929cc2
0, 90, 90, 1, 152064, 0xf07606b7
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 92, 92, 1, 152064, 0x0476b876
0, 93, 93, 1, 152064, 0x213333dc
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 93, 93, 1, 152064, 0x87c67597
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 95, 95, 1, 152064, 0x05434641
0, 96, 96, 1, 152064, 0x959eeffc
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 96, 96, 1, 152064, 0x92a130b4
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 98, 98, 1, 152064, 0x53d0b544
0, 99, 99, 1, 152064, 0xaf8c233e
0, 100, 100, 1, 152064, 0xd3d4259a
0, 101, 101, 1, 152064, 0xa0287753
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 101, 101, 1, 152064, 0xfa23972a
0, 102, 102, 1, 152064, 0xacae756d
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 104, 104, 1, 152064, 0xd8b58b5c
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 104, 104, 1, 152064, 0x7db2c755
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 106, 106, 1, 152064, 0x31e7b79a
0, 107, 107, 1, 152064, 0xd8660d98
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 107, 107, 1, 152064, 0xdcf0d10d
0, 108, 108, 1, 152064, 0x3e6567e6
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 110, 110, 1, 152064, 0xec3530fd
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 110, 110, 1, 152064, 0xf686c61a
0, 111, 111, 1, 152064, 0x6e706804
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 113, 113, 1, 152064, 0x5fd4a1a3
0, 114, 114, 1, 152064, 0xbb3384f7
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 114, 114, 1, 152064, 0x8ffb14dd
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 116, 116, 1, 152064, 0x01253a73
0, 117, 117, 1, 152064, 0xf89c15df
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 117, 117, 1, 152064, 0xda2b0b4c
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 119, 119, 1, 152064, 0xfc9dfcc1
0, 120, 120, 1, 152064, 0xfef4f0fa
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 120, 120, 1, 152064, 0x91669bea
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 122, 122, 1, 152064, 0x3664a565
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 122, 122, 1, 152064, 0x32dd7923
0, 123, 123, 1, 152064, 0x26825231
0, 124, 124, 1, 152064, 0x5f81896e
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 126, 126, 1, 152064, 0x0c64ca2f
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 126, 126, 1, 152064, 0x488bb665
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 128, 128, 1, 152064, 0x4d183a0f
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 128, 128, 1, 152064, 0xed169321
0, 129, 129, 1, 152064, 0xcec22917
0, 130, 130, 1, 152064, 0xbe04ea6c
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 132, 132, 1, 152064, 0x32b8bf9f
0, 133, 133, 1, 152064, 0x9c7c2e13
0, 134, 134, 1, 152064, 0x232e3016
0, 135, 135, 1, 152064, 0x1b76c08e
0, 136, 136, 1, 152064, 0x7425d821
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 136, 136, 1, 152064, 0x0818ff3c
0, 137, 137, 1, 152064, 0xb4f2c42b
0, 138, 138, 1, 152064, 0xe029f979
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 140, 140, 1, 152064, 0x97c54c2f
0, 141, 141, 1, 152064, 0xd101c3b5
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 141, 141, 1, 152064, 0x5ed1f5d4
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 143, 143, 1, 152064, 0xc28264d1
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 143, 143, 1, 152064, 0xa162dd31
0, 144, 144, 1, 152064, 0x2ee872ce
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 146, 146, 1, 152064, 0x809a8fce
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 146, 146, 1, 152064, 0xcfcc3ef9
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 148, 148, 1, 152064, 0xa5be6ce3
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 148, 148, 1, 152064, 0xd75930a0
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 150, 150, 1, 152064, 0x28acb80f
0, 151, 151, 1, 152064, 0x223f2152
0, 152, 152, 1, 152064, 0x0cf070cb
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 152, 152, 1, 152064, 0xcc7d011e
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 154, 154, 1, 152064, 0xb2c2a63c
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 154, 154, 1, 152064, 0x15514caa
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 156, 156, 1, 152064, 0x0c6d18ee
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 156, 156, 1, 152064, 0x33b4265d
0, 157, 157, 1, 152064, 0xb4abaaaf
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 159, 159, 1, 152064, 0x26a7a856
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 159, 159, 1, 152064, 0xc75249cc
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 161, 161, 1, 152064, 0x59ccb0e1
0, 162, 162, 1, 152064, 0xc613f202
0, 163, 163, 1, 152064, 0xd1c0e171
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 163, 163, 1, 152064, 0xa195da2b
0, 164, 164, 1, 152064, 0xbc7ed475
0, 165, 165, 1, 152064, 0x99206e2c
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 167, 167, 1, 152064, 0x0ef04e03
0, 168, 168, 1, 152064, 0x68cbc6a1
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 168, 168, 1, 152064, 0x2a5304b1
0, 169, 169, 1, 152064, 0xf017978b
0, 170, 170, 1, 152064, 0x94f5641a
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 172, 172, 1, 152064, 0xd681bd8f
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 172, 172, 1, 152064, 0x16e1e3a3
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 174, 174, 1, 152064, 0xe4486c7e
0, 175, 175, 1, 152064, 0xa1bd394e
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 175, 175, 1, 152064, 0x49ad5959
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 177, 177, 1, 152064, 0x82219b70
0, 178, 178, 1, 152064, 0x64e2abcf
0, 179, 179, 1, 152064, 0x6d7d05d8
0, 180, 180, 1, 152064, 0xd9ac2251
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 180, 180, 1, 152064, 0xf477eee5
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 182, 182, 1, 152064, 0xb9826a78
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 182, 182, 1, 152064, 0x97828a37
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 184, 184, 1, 152064, 0x12099b1f
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 184, 184, 1, 152064, 0x1ec45fa7
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 186, 186, 1, 152064, 0xfd5501c9
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 186, 186, 1, 152064, 0x6a8b26a3
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 188, 188, 1, 152064, 0xae58ff40
0, 189, 189, 1, 152064, 0xc0f47aa1
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 189, 189, 1, 152064, 0x08bfa548
0, 190, 190, 1, 152064, 0x7f2ff5ef
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 192, 192, 1, 152064, 0x5efa94a3
0, 193, 193, 1, 152064, 0xf786f970
0, 194, 194, 1, 152064, 0xab6bc712
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 194, 194, 1, 152064, 0x25647bee
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 196, 196, 1, 152064, 0x54333ad5
0, 197, 197, 1, 152064, 0xb3a99413
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 197, 197, 1, 152064, 0xe7a78a0d
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 199, 199, 1, 152064, 0xa5054abc
0, 200, 200, 1, 152064, 0xb94896ea
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 200, 200, 1, 152064, 0x9f641bca
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 202, 202, 1, 152064, 0x7363901c
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 202, 202, 1, 152064, 0xd340a000
0, 203, 203, 1, 152064, 0x0217f413
0, 204, 204, 1, 152064, 0xbbdba6e6
0, 205, 205, 1, 152064, 0xabc42617
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 207, 207, 1, 152064, 0xa3442925
0, 208, 208, 1, 152064, 0x7d06c7e9
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 208, 208, 1, 152064, 0xa45e32df
0, 209, 209, 1, 152064, 0xf5ed407f
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 211, 211, 1, 152064, 0x5ec235d5
0, 212, 212, 1, 152064, 0xa5706635
0, 213, 213, 1, 152064, 0xa44a209b
0, 214, 214, 1, 152064, 0xf2137e37
0, 215, 215, 1, 152064, 0x5220508f
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 215, 215, 1, 152064, 0xae6b37da
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 217, 217, 1, 152064, 0xdf09b6cd
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 217, 217, 1, 152064, 0x2d39e1c0
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 219, 219, 1, 152064, 0xc8284a76
0, 220, 220, 1, 152064, 0x7d7bbe76
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 220, 220, 1, 152064, 0xcfed7416
0, 221, 221, 1, 152064, 0x81caaedd
0, 222, 222, 1, 152064, 0x9dcdd771
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 224, 224, 1, 152064, 0x46c1331b
0, 225, 225, 1, 152064, 0xace60efa
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 225, 225, 1, 152064, 0x9e0909f7
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 227, 227, 1, 152064, 0x72f5a321
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 227, 227, 1, 152064, 0x68f8cdcc
0, 228, 228, 1, 152064, 0xcc59fdd9
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 230, 230, 1, 152064, 0xc0a700c6
0, 231, 231, 1, 152064, 0xf4254dcf
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 231, 231, 1, 152064, 0xc59b46d1
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 233, 233, 1, 152064, 0x2e5b2524
0, 234, 234, 1, 152064, 0x46051293
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 234, 234, 1, 152064, 0x3cbcd1cd
0, 235, 235, 1, 152064, 0x9f308587
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 237, 237, 1, 152064, 0x6b91633f
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 237, 237, 1, 152064, 0xb7191012
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 239, 239, 1, 152064, 0xd2fd030f
0, 240, 240, 1, 152064, 0x15a0ae2e
0, 241, 241, 1, 152064, 0xac3920d0
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 241, 241, 1, 152064, 0x0eef80aa
0, 242, 242, 1, 152064, 0x319008f1
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 244, 244, 1, 152064, 0x7734450c
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 244, 244, 1, 152064, 0xf112df62
0, 245, 245, 1, 152064, 0x1dd8ffae
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 247, 247, 1, 152064, 0x655ef429
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 247, 247, 1, 152064, 0x27026213
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 249, 249, 1, 152064, 0x5c14b015
0, 250, 250, 1, 152064, 0x9512abeb
0, 251, 251, 1, 152064, 0x961812b2
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 251, 251, 1, 152064, 0xb8890aea
0, 252, 252, 1, 152064, 0x4519db9a
0, 253, 253, 1, 152064, 0xf358034a
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 255, 255, 1, 152064, 0x45d9f2ab
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 255, 255, 1, 152064, 0xebd47e7d
0, 256, 256, 1, 152064, 0x15578be9
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 258, 258, 1, 152064, 0x1b373b2d
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 258, 258, 1, 152064, 0xbbe707e5
0, 259, 259, 1, 152064, 0x5bf62385
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 261, 261, 1, 152064, 0x832e6ef5
0, 262, 262, 1, 152064, 0x761e5968
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 262, 262, 1, 152064, 0x251f984d
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 264, 264, 1, 152064, 0xbda48899
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 264, 264, 1, 152064, 0x3fd843b9
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 266, 266, 1, 152064, 0x00485425
0, 267, 267, 1, 152064, 0x4e282b39
0, 268, 268, 1, 152064, 0x2630a8ea
0, 269, 269, 1, 152064, 0x5ea5c973
0, 270, 270, 1, 152064, 0xfc436d21
0, 271, 271, 1, 152064, 0x69852ef5
0, 272, 272, 1, 152064, 0x44cb5589
0, 273, 273, 1, 152064, 0x32f32725
0, 274, 274, 1, 152064, 0x54d50aca
0, 275, 275, 1, 152064, 0xe7a639bb
0, 276, 276, 1, 152064, 0x01be2ad5
0, 277, 277, 1, 152064, 0x5c63eca4
0, 278, 278, 1, 152064, 0x94e91116
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 278, 278, 1, 152064, 0x9a8be637
0, 279, 279, 1, 152064, 0x165d9a12
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 281, 281, 1, 152064, 0x8c25ca0a
0, 282, 282, 1, 152064, 0x4ee2ed32
0, 283, 283, 1, 152064, 0x4b2fe0c6
0, 284, 284, 1, 152064, 0x521e434e
0, 285, 285, 1, 152064, 0x97679d7e
0, 286, 286, 1, 152064, 0x886b9506
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 286, 286, 1, 152064, 0x4283eda8
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 288, 288, 1, 152064, 0xef793c49
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 288, 288, 1, 152064, 0x68ac2afe
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 290, 290, 1, 152064, 0x3d1ab510
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 290, 290, 1, 152064, 0x98d3ec95
0, 291, 291, 1, 152064, 0x09f7e512
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 293, 293, 1, 152064, 0x801355dd
0, 294, 294, 1, 152064, 0xf2e87a11
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 294, 294, 1, 152064, 0x16757601
0, 295, 295, 1, 152064, 0x3074d74a
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later.
2020-11-30 15:13:51 +02:00
0, 297, 297, 1, 152064, 0xec8c1290
0, 298, 298, 1, 152064, 0x46fb1877
frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.
2012-02-02 16:20:43 +03:00
0, 298, 298, 1, 152064, 0xf0b662c4
0, 299, 299, 1, 152064, 0xf8683940
Reference in New Issue Copy Permalink