FFmpeg/tests/ref/lavf/gxf

346d38d330ab5cb0caa6b5537167bc0d *./tests/data/lavf/lavf.gxf
796392 ./tests/data/lavf/lavf.gxf
./tests/data/lavf/lavf.gxf CRC=0x246186eb
Update gxf regression tests because of r25399 Originally committed as revision 25400 to svn://svn.ffmpeg.org/ffmpeg/trunk 2010-10-07 22:37:37 +03:00			`346d38d330ab5cb0caa6b5537167bc0d *./tests/data/lavf/lavf.gxf`
Place regression test output files in subdirs per family Originally committed as revision 22155 to svn://svn.ffmpeg.org/ffmpeg/trunk 2010-03-02 23:41:52 +02:00			`796392 ./tests/data/lavf/lavf.gxf`
rawenc: switch to encode2(). This changes a number of FATE results, since before this commit, the timestamps in all tests using rawenc were made up by lavf. In most cases, the previous timestamps were completely bogus. In some other cases -- raw formats, mostly h264 -- the new timestamps are bogus as well. The only difference is that timestamps invented by the muxer are replaced by timestamps invented by the demuxer. cscd -- avconv sets output codec timebase from r_frame_rate and r_frame_rate is in this case some guessed number 31.42 (377/12), which is not accurate enough to represent all timestamps. This results in some frames having duplicate pts. Therefore, vsync 0 needs to be changed to vsync 2 and avconv drops two frames. A proper fix in the future would be to set output timebase to something saner in avconv. nuv -- previous timestamps for video were wrong AND the cscd comment applies, one frame is dropped. vp8-signbias -- the file contains two frames with identical timestamps, so -vsync 0 needs to be removed/changed to -vsync 2 and avconv drops one frame. vc1-ism -- apparrently either the demuxer lies about timestamps or the file is broken, since dts == pts on all packets, but reordering clearly takes place. 2012-02-01 17:33:51 +03:00			`./tests/data/lavf/lavf.gxf CRC=0x246186eb`