- S3 Texture Compression
-
S3 Texture Compression (S3TC) (sometimes also called DXTn or DXTC) is a group of related lossy texture compression algorithms originally developed by Iourcha et al. of S3 Graphics, Ltd. [1] for use in their Savage 3D computer graphics accelerator. The method of compression is strikingly similar to the previously published Color Cell Compression,[2] which is in turn an adaptation of Block Truncation Coding published in the late 1970s. Unlike some image compression algorithms (e.g. JPEG), S3TC's fixed-rate data compression coupled with the single memory access (cf. Color Cell Compression and some VQ-based schemes) made it well-suited for use in compressing textures in hardware-accelerated 3D computer graphics. Its subsequent inclusion in Microsoft's DirectX 6.0 and OpenGL 1.3 (via the GL_EXT_texture_compression_s3tc extension) led to widespread adoption of the technology among hardware and software makers. While S3 Graphics is no longer a competitor in the graphics accelerator market, license fees are still levied and collected for the use of S3TC technology, for example in game consoles and graphics cards. The patent-encumbered status of S3TC and its wide use in software, despite non-encumbered alternatives, have led to a de facto requirement for OpenGL drivers to support it and present a major obstacle[3] to open source implementations.
In September of 2011, Intel employee Ian Romanick mentioned that the S3TC patent had been marked as invalid in patent litigation between Apple and HTC [4], the latter of which acquired S3 and all of their patents. If the patent does prove to be invalid, it would be a simple matter of enabling support for it in Mesa 3D, a popular open source OpenGL-compatible computer graphics library. Currently, the only way Mesa 3D can work around the patent issue is to look for an external library capable of handling the S3TC formats (libtxc_dxtn.so), and loading it if found. There is another option, set through an environment variable, that will cause Mesa 3D to expose the S3TC extension without actually supporting it. While this will not work for most applications that expect the functionality, there are some applications that check for the functionality and fail to start without it, but which do not actually or correctly use the functionality of S3TC. If that is the case, this alternative might make the application work anyway without S3TC support.[5]
Contents
Codecs
There are five variations of the S3TC algorithm (named DXT1 through DXT5, referring to the FourCC code assigned by Microsoft to each format), each designed for specific types of image data. All convert a 4×4 block of pixels to a 64-bit or 128-bit quantity, resulting in compression ratios of 6:1 with 24-bit RGB input data or 4:1 with 32-bit RGBA input data. S3TC is a lossy compression algorithm, resulting in image quality degradation, an effect which is minimized by the ability to increase texture resolutions while maintaining the same memory requirements. Hand-drawn cartoon-like images do not compress well, nor do normal map data, both of which usually generate artifacts. ATI's 3Dc compression algorithm is a modification of DXT5 designed to overcome S3TC's shortcomings with regard to normal maps. id Software worked around the normalmap compression issues in Doom 3 by moving the red component into the alpha channel before compression and moving it back during rendering in the pixel shader.[6]
Like many modern image compression algorithms, S3TC only specifies the method used to decompress images, allowing implementers to design the compression algorithm to suit their specific needs, although the patent still covers compression algorithms. The nVidia GeForce 1 through to GeForce 4 cards also used 16-bit interpolation to render DXT1 textures, which resulted in banding when unpacking textures with color gradients. Again, this created an unfavorable impression of texture compression, not related to the fundamentals of the codec itself.
DXT1
DXT1 (also known as Block Compression 1 or BC1) is the smallest variation of S3TC, storing 16 input pixels in 64 bits of output, consisting of two 16-bit RGB 5:6:5 color values and a 4x4 two bit lookup table.
If the first color value (c0) is numerically greater than the second color value (c1), then two other colors are calculated, such that and . This mode operates similarly to mode 0xC0 of the original Apple Video codec.[7]
Otherwise, if , then and c3 is transparent black corresponding to a premultiplied alpha format.
The lookup table is then consulted to determine the color value for each pixel, with a value of 0 corresponding to c0 and a value of 3 corresponding to c3. DXT1 does not store alpha data enabling higher compression ratios.
DXT2 and DXT3
DXT2 and DXT3 (collectively also known as Block Compression 2 or BC2) converts 16 input pixels (corresponding to a 4x4 pixel block) into 128 bits of output, consisting of 64 bits of alpha channel data (4 bits for each pixel) followed by 64 bits of color data, encoded the same way as DXT1 (with the exception that the 4 color version of the DXT1 algorithm is always used instead of deciding which version to use based on the relative values of c0 and c1).
In DXT2, the color data is interpreted as being premultiplied by alpha, in DXT3 it is interpreted as not having been premultiplied by alpha. Typically DXT2/3 are well suited to images with sharp alpha transitions, between translucent and opaque areas.DXT4 and DXT5
DXT4 and DXT5 (collectively also known as Block Compression 3 or BC3) converts 16 input pixels into 128 bits of output, consisting of 64 bits of alpha channel data (two 8 bit alpha values and a 4x4 3 bit lookup table) followed by 64 bits of color data (encoded the same way as DXT2 and DXT3).
If α0 > α1, then six other alpha values are calculated, such that , , , , , and .
Otherwise, if , four other alpha values are calculated such that , , , and with α6 = 0 and α7 = 255.
The lookup table is then consulted to determine the alpha value for each pixel, with a value of 0 corresponding to α0 and a value of 7 corresponding to α7. DXT4's color data is premultiplied by alpha, whereas DXT5's is not. Because DXT4/5 use an interpolated alpha scheme, they generally produce superior results for alpha (transparency) gradients than DXT2/3.
S3TC Format Comparison
FOURCC DX 10 Name Description Alpha premultiplied? Compression ratio Texture Type DXT1 BC1 1-bit Alpha / Opaque N/A 6:1(for 24 bit source image) Simple non-alpha DXT2 (none) Explicit alpha Yes 4:1 Sharp alpha DXT3 BC2 Explicit alpha No 4:1 Sharp alpha DXT4 (none) Interpolated alpha Yes 4:1 Gradient alpha DXT5 BC3 Interpolated alpha No 4:1 Gradient alpha See also
References
- ^ US 5956431 "Fixed-rate block-based image compression with inferred pixel values"
- ^ 1990 IEEE Color Cell Compression Paper[1]
- ^ S3TC situation on official DRI information page [2]
- ^ [3]
- ^ [4]
- ^ DOOM 3 Video Requirements
- ^ Togni, Roberto, et al. "Apple RPZA". MultimediaWiki.
External links
- Microsoft Developer Network article on Block Compression in Direct3D 10)
- NVIDIA Texture Tools
- AMD GPU Tools
- squish, an MIT-licensed S3TC compressor. The site also contains an article giving an introduction to compression algorithms.
- libtxc_dxtn, a BSD licensed module for Mesa
- Comparison between S3TC and FXT1 texture compression
- The Truth about S3TC Note: This article used an early S3TC compression engine, not nVidia's or ATI's updated codecs.
- Texture compression survey
Categories:- Lossy compression algorithms
- Texture compression
- 3D computer graphics
Wikimedia Foundation. 2010.