Texture compression

Texture compression is a specialized form of image compression designed for storing texture maps in 3D computer graphics rendering systems. Unlike conventional image compression algorithms, texture compression algorithms are optimized for random access.

Three-dimensional (3D)
computer graphics
Fundamentals
Primary uses
Related topics

Tradeoffs

In their seminal paper on texture compression,[1] Beers, Agrawala and Chaddha list four features that tend to differentiate texture compression from other image compression techniques. These features are:

Decoding Speed
It is highly desirable to be able to render directly from the compressed texture data and so, in order not to impact rendering performance, decompression must be fast.
Random Access
Since predicting the order that a renderer accesses texels would be difficult, any texture compression scheme must allow fast random access to decompressed texture data. This tends to rule out many better-known image compression schemes such as JPEG or run-length encoding.
Compression Rate and Visual Quality
In a rendering system, lossy compression can be more tolerable than for other use cases. Some texture compression libraries, such as crunch,[2] allow the developer to flexibly trade off compression rate vs. visual quality, using methods such as rate-distortion optimization (RDO).
Encoding Speed
Texture compression is more tolerant of asymmetric encoding/decoding rates as the encoding process is often done only once during the application authoring process.

Given the above, most texture compression algorithms involve some form of fixed-rate lossy vector quantization of small fixed-size blocks of pixels into small fixed-size blocks of coding bits, sometimes with additional extra pre-processing and post-processing steps. Block Truncation Coding is a very simple example of this family of algorithms.

Because their data access patterns are well-defined, texture decompression may be executed on-the-fly during rendering as part of the overall graphics pipeline, reducing overall bandwidth and storage needs throughout the graphics system. As well as texture maps, texture compression may also be used to encode other kinds of rendering map, including bump maps and surface normal maps. Texture compression may also be used together with other forms of map processing such as MIP maps and anisotropic filtering.

Availability

Some examples of practical texture compression systems are S3 Texture Compression (S3TC), PVRTC, Ericsson Texture Compression (ETC) and Adaptive Scalable Texture Compression (ASTC); these may be supported by special function units in modern Graphics processing units.

OpenGL and OpenGL ES, as implemented on many video accelerator cards and mobile GPUs, can support multiple common kinds of texture compression - generally through the use of vendor extensions.

Texture compression can be applied to reduce memory usage at runtime, as opposed to texture compression designed to reduce download or disk size. Texture data is often the largest source of memory usage in a mobile application.

gollark: Honestly none of this matters because even 170 templates rendered per second on much larger datasets than I'm likely to be using is probably fast enough.
gollark: *Low* performance?
gollark: Yes. These are Rust HTML templating engines.
gollark: I mean, I looked at some of these and they seem perfectly fine.
gollark: *Why* is there such a huge disparity between template engines? What could they possibly be doing to have such large speed differences? How does any of this work?!?!?!

See also

References
  1. Andrew Beers; Maneesh Agrawala; Navin Chaddha (1996), "Rendering from Compressed Textures", Computer Graphics, Proc. SIGGRAPH: 373–378
  2. "crunch open source texture compression library". GitHub. Retrieved 2016-09-13.



This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.