generic-library/ffmpeg
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
e0febda22d
ffmpeg/tests/ref/fate/adpcm-ea-tqi

54 lines
2.9 KiB
Plaintext
Raw Normal View History

avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
#tb 0: 1/90000
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 14:20:43 +01:00
#tb 1: 1/22050
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 0, 0, 0, 115200, 0x375ec573
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 14:20:43 +01:00
1, 0, 0, 1484, 5936, 0x00000000
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 6000, 6000, 0, 115200, 0x375ec573
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 14:20:43 +01:00
1, 1484, 1484, 1456, 5824, 0x00000000
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 12000, 12000, 0, 115200, 0x375ec573
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 14:20:43 +01:00
1, 2940, 2940, 1484, 5936, 0x00000000
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 18000, 18000, 0, 115200, 0x375ec573
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 14:20:43 +01:00
1, 4424, 4424, 1456, 5824, 0x00000000
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 24000, 24000, 0, 115200, 0x375ec573
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 14:20:43 +01:00
1, 5880, 5880, 1484, 5936, 0x00000000
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 30000, 30000, 0, 115200, 0x375ec573
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 14:20:43 +01:00
1, 7364, 7364, 1456, 5824, 0x00000000
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 36000, 36000, 0, 115200, 0x375ec573
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 14:20:43 +01:00
1, 8820, 8820, 1484, 5936, 0x00000000
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 42000, 42000, 0, 115200, 0x375ec573
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 14:20:43 +01:00
1, 10304, 10304, 1456, 5824, 0x0f06f5bb
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 48000, 48000, 0, 115200, 0x0b4d31bf
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 14:20:43 +01:00
1, 11760, 11760, 1484, 5936, 0xb0dbfc46
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 54000, 54000, 0, 115200, 0xdd724598
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 14:20:43 +01:00
1, 13244, 13244, 1456, 5824, 0x9daa9f9c
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 60000, 60000, 0, 115200, 0xc3077e75
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 14:20:43 +01:00
1, 14700, 14700, 1484, 5936, 0x61400d2f
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 66000, 66000, 0, 115200, 0xbf70778a
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 14:20:43 +01:00
1, 16184, 16184, 1456, 5824, 0x34a5b0e3
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 72000, 72000, 0, 115200, 0x117eb766
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 14:20:43 +01:00
1, 17640, 17640, 1484, 5936, 0x6e546f72
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 78000, 78000, 0, 115200, 0x4617fbad
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 14:20:43 +01:00
1, 19124, 19124, 1456, 5824, 0x4f093b35
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 84000, 84000, 0, 115200, 0x5f5b02d2
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 14:20:43 +01:00
1, 20580, 20580, 1484, 5936, 0x95b5b599
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 90000, 90000, 0, 115200, 0x2a9c5325
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 14:20:43 +01:00
1, 22064, 22064, 1456, 5824, 0x75e15e60
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 96000, 96000, 0, 115200, 0x14a89e2a
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 14:20:43 +01:00
1, 23520, 23520, 1484, 5936, 0xd1077d39
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 102000, 102000, 0, 115200, 0xe69aa994
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 14:20:43 +01:00
1, 25004, 25004, 1456, 5824, 0x956e21ca
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 108000, 108000, 0, 115200, 0xfbacf589
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 14:20:43 +01:00
1, 26460, 26460, 1484, 5936, 0x33bac234
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 114000, 114000, 0, 115200, 0x1d714c6e
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 14:20:43 +01:00
1, 27944, 27944, 1456, 5824, 0x5df37824
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 120000, 120000, 0, 115200, 0x6eff66cb
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 14:20:43 +01:00
1, 29400, 29400, 1484, 5936, 0xc174af24
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 126000, 126000, 0, 115200, 0xee21c1cb
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 14:20:43 +01:00
1, 30884, 30884, 1456, 5824, 0xe5dc2159
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 132000, 132000, 0, 115200, 0xce714ada
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 14:20:43 +01:00
1, 32340, 32340, 1484, 5936, 0x63ffc8b1
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 138000, 138000, 0, 115200, 0xf89d56c3
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 14:20:43 +01:00
1, 33824, 33824, 1456, 5824, 0xefe4c365
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 144000, 144000, 0, 115200, 0x65fd5e60
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 14:20:43 +01:00
1, 35280, 35280, 1484, 5936, 0x2174304d
avconv: saner output video timebase. r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a6539bd7fc2dc4c1740fbcbd498c0c0a2
2012-02-07 11:03:33 +01:00
0, 150000, 150000, 0, 115200, 0x0c256424
Reference in New Issue Copy Permalink