- 30 Jun, 2015 1 commit
-
-
Martin Storsjö authored
Most of the fate-dds-* and fate-txd-* tests already output into the same pixel format regardless of platform endianness, so there's no need to force conversion to another format. This fixes the tests fate-txd-16bpp, fate-txd-odd, fate-dds-rgb16, fate-dds-rgb24 and fate-dds-xrgb on big endian, where the tests seem to fail due to issues with certain conversion codepaths in swscale. Those conversion codepaths should of course be fixed, but the individual decoder tests should use as little extra conversion steps as possible. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 22 Jun, 2015 1 commit
-
-
Vittorio Giovara authored
Using the internal DXTC routines brings support for non multiple of 4 textures. A new test is added to cover this feature. Hashes differ since the decoding algorithm is different, though no visual changes have been spotted. Signed-off-by: Vittorio Giovara <vittorio.giovara@gmail.com>
-
- 22 Apr, 2014 1 commit
-
-
Anton Khirnov authored
It is not supposed to be changed from outside of lavc. Set the stream timebase and average framerate instead.
-
- 26 Feb, 2012 1 commit
-
-
Anton Khirnov authored
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 cd1ad18a
-
- 03 Feb, 2012 1 commit
-
-
Anton Khirnov authored
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.
-
- 24 Aug, 2010 1 commit
-
-
Vitor Sessak authored
Originally committed as revision 24911 to svn://svn.ffmpeg.org/ffmpeg/trunk
-