Discrete cosine transform

From testwiki
Jump to navigation Jump to search

Template:Short description Template:Jagged 85 cleanup

A discrete cosine transform (DCT) expresses a finite sequence of data points in terms of a sum of cosine functions oscillating at different frequencies. The DCT, first proposed by Nasir Ahmed in 1972, is a widely used transformation technique in signal processing and data compression. It is used in most digital media, including digital images (such as JPEG and HEIF), digital video (such as MPEG and Template:Nowrap), digital audio (such as Dolby Digital, MP3 and AAC), digital television (such as SDTV, HDTV and VOD), digital radio (such as AAC+ and DAB+), and speech coding (such as AAC-LD, Siren and Opus). DCTs are also important to numerous other applications in science and engineering, such as digital signal processing, telecommunication devices, reducing network bandwidth usage, and spectral methods for the numerical solution of partial differential equations.

A DCT is a Fourier-related transform similar to the discrete Fourier transform (DFT), but using only real numbers. The DCTs are generally related to Fourier series coefficients of a periodically and symmetrically extended sequence whereas DFTs are related to Fourier series coefficients of only periodically extended sequences. DCTs are equivalent to DFTs of roughly twice the length, operating on real data with even symmetry (since the Fourier transform of a real and even function is real and even), whereas in some variants the input or output data are shifted by half a sample.

There are eight standard DCT variants, of which four are common. The most common variant of discrete cosine transform is the type-II DCT, which is often called simply the DCT. This was the original DCT as first proposed by Ahmed. Its inverse, the type-III DCT, is correspondingly often called simply the inverse DCT or the IDCT. Two related transforms are the discrete sine transform (DST), which is equivalent to a DFT of real and odd functions, and the modified discrete cosine transform (MDCT), which is based on a DCT of overlapping data. Multidimensional DCTs (MD DCTs) are developed to extend the concept of DCT to multidimensional signals. A variety of fast algorithms have been developed to reduce the computational complexity of implementing DCT. One of these is the integer DCT (IntDCT),[1] an integer approximation of the standard DCT,[2]Template:Rp used in several ISO/IEC and ITU-T international standards.[1][2]

DCT compression, also known as block compression, compresses data in sets of discrete DCT blocks.[3] DCT blocks sizes including 8x8 pixels for the standard DCT, and varied integer DCT sizes between 4x4 and 32x32 pixels.[1][4] The DCT has a strong energy compaction property,[5][6] capable of achieving high quality at high data compression ratios.[7][8] However, blocky compression artifacts can appear when heavy DCT compression is applied.

History

The DCT was first conceived by Nasir Ahmed, T. Natarajan and K. R. Rao while working at Kansas State University. The concept was proposed to the National Science Foundation in 1972. The DCT was originally intended for image compression.[9][1] Ahmed developed a practical DCT algorithm with his PhD students T. Raj Natarajan, Wills Dietrich, and Jeremy Fries, and his friend Dr. K. R. Rao at the University of Texas at Arlington in 1973.[9] They presented their results in a January 1974 paper, titled Discrete Cosine Transform.[5][6][10] It described what is now called the type-II DCT (DCT-II),[2]Template:Rp as well as the type-III inverse DCT (IDCT).[5]

Since its introduction in 1974, there has been significant research on the DCT.[10] In 1977, Wen-Hsiung Chen published a paper with C. Harrison Smith and Stanley C. Fralick presenting a fast DCT algorithm.[11][10] Further developments include a 1978 paper by M. J. Narasimha and A. M. Peterson, and a 1984 paper by B. G. Lee.[10] These research papers, along with the original 1974 Ahmed paper and the 1977 Chen paper, were cited by the Joint Photographic Experts Group as the basis for JPEG's lossy image compression algorithm in 1992.[10][12]

The discrete sine transform (DST) was derived from the DCT, by replacing the Neumann condition at x=0 with a Dirichlet condition.[2]Template:Rp The DST was described in the 1974 DCT paper by Ahmed, Natarajan and Rao.[5] A type-I DST (DST-I) was later described by Anil K. Jain in 1976, and a type-II DST (DST-II) was then described by H.B. Kekra and J.K. Solanka in 1978.[13]

In 1975, John A. Roese and Guner S. Robinson adapted the DCT for inter-frame motion-compensated video coding. They experimented with the DCT and the fast Fourier transform (FFT), developing inter-frame hybrid coders for both, and found that the DCT is the most efficient due to its reduced complexity, capable of compressing image data down to 0.25-bit per pixel for a videotelephone scene with image quality comparable to an intra-frame coder requiring 2-bit per pixel.[14][15] In 1979, Anil K. Jain and Jaswant R. Jain further developed motion-compensated DCT video compression,[16][17] also called block motion compensation.[17] This led to Chen developing a practical video compression algorithm, called motion-compensated DCT or adaptive scene coding, in 1981.[17] Motion-compensated DCT later became the standard coding technique for video compression from the late 1980s onwards.[18][19]

A DCT variant, the modified discrete cosine transform (MDCT), was developed by John P. Princen, A.W. Johnson and Alan B. Bradley at the University of Surrey in 1987,[20] following earlier work by Princen and Bradley in 1986.[21] The MDCT is used in most modern audio compression formats, such as Dolby Digital (AC-3),[22][23] MP3 (which uses a hybrid DCT-FFT algorithm),[24] Advanced Audio Coding (AAC),[25] and Vorbis (Ogg).[26]

Nasir Ahmed also developed a lossless DCT algorithm with Giridhar Mandyam and Neeraj Magotra at the University of New Mexico in 1995. This allows the DCT technique to be used for lossless compression of images. It is a modification of the original DCT algorithm, and incorporates elements of inverse DCT and delta modulation. It is a more effective lossless compression algorithm than entropy coding.[27] Lossless DCT is also known as LDCT.[28]

Applications

The DCT is the most widely used transformation technique in signal processing,[29] and by far the most widely used linear transform in data compression.[30] Uncompressed digital media as well as lossless compression have high memory and bandwidth requirements, which is significantly reduced by the DCT lossy compression technique,[7][8] capable of achieving data compression ratios from 8:1 to 14:1 for near-studio-quality,[7] up to 100:1 for acceptable-quality content.[8] DCT compression standards are used in digital media technologies, such as digital images, digital photos,[31][32] digital video,[18][33] streaming media,[34] digital television, streaming television, video on demand (VOD),[8] digital cinema,[22] high-definition video (HD video), and high-definition television (HDTV).[7][35]

The DCT, and in particular the DCT-II, is often used in signal and image processing, especially for lossy compression, because it has a strong energy compaction property.[5][6] In typical applications, most of the signal information tends to be concentrated in a few low-frequency components of the DCT. For strongly correlated Markov processes, the DCT can approach the compaction efficiency of the Karhunen-Loève transform (which is optimal in the decorrelation sense). As explained below, this stems from the boundary conditions implicit in the cosine functions.

DCTs are widely employed in solving partial differential equations by spectral methods, where the different variants of the DCT correspond to slightly different even and odd boundary conditions at the two ends of the array.

DCTs are closely related to Chebyshev polynomials, and fast DCT algorithms (below) are used in Chebyshev approximation of arbitrary functions by series of Chebyshev polynomials, for example in Clenshaw–Curtis quadrature.

General applications

The DCT is widely used in many applications, which include the following.

Template:Columns-list

Visual media standards

The DCT-II is an important image compression technique. It is used in image compression standards such as JPEG, and video compression standards such as Template:Nowrap, MJPEG, MPEG, DV, Theora and Daala. There, the two-dimensional DCT-II of N×N blocks are computed and the results are quantized and entropy coded. In this case, N is typically 8 and the DCT-II formula is applied to each row and column of the block. The result is an 8 × 8 transform coefficient array in which the (0,0) element (top-left) is the DC (zero-frequency) component and entries with increasing vertical and horizontal index values represent higher vertical and horizontal spatial frequencies.

The integer DCT, an integer approximation of the DCT,[2][1] is used in Advanced Video Coding (AVC),[36][1] introduced in 2003, and High Efficiency Video Coding (HEVC),[4][1] introduced in 2013. The integer DCT is also used in the High Efficiency Image Format (HEIF), which uses a subset of the HEVC video coding format for coding still images.[4] AVC uses 4 x 4 and 8 x 8 blocks. HEVC and HEIF use varied block sizes between 4 x 4 and 32 x 32 pixels.[4][1] Template:As of, AVC is by far the most commonly used format for the recording, compression and distribution of video content, used by 91% of video developers, followed by HEVC which is used by 43% of developers.[37]

Image formats

Image compression standard Year Common applications
JPEG[1] 1992 The most widely used image compression standard[38][39] and digital image format.[40]
JPEG XR 2009 Open XML Paper Specification
WebP 2010 A graphic format that supports the lossy compression of digital images. Developed by Google.
High Efficiency Image Format (HEIF) 2013 Image file format based on HEVC compression. It improves compression over JPEG,[4] and supports animation with much more efficient compression than the animated GIF format.[41]
BPG 2014 Based on HEVC compression
JPEG XL[42] 2020 A royalty-free raster-graphics file format that supports both lossy and lossless compression.

Video formats

Video coding standard Year Common applications
Template:Nowrap[43][44] 1988 First of a family of video coding standards. Used primarily in older video conferencing and video telephone products.
Motion JPEG (MJPEG)[45] 1992 QuickTime, video editing, non-linear editing, digital cameras
MPEG-1 Video[46] 1993 Digital video distribution on CD or Internet video
MPEG-2 Video (Template:Nowrap)[46] 1995 Storage and handling of digital images in broadcast applications, digital television, HDTV, cable, satellite, high-speed Internet, DVD video distribution
DV 1995 Camcorders, digital cassettes
H.263 (MPEG-4 Part 2)[43] 1996 Video telephony over public switched telephone network (PSTN), Template:Nowrap, Integrated Services Digital Network (ISDN)[47][48]
Advanced Video Coding (AVC, Template:Nowrap, MPEG-4)[1][36] 2003 Popular HD video recording, compression and distribution format, Internet video, YouTube, Blu-ray Discs, HDTV broadcasts, web browsers, streaming television, mobile devices, consumer devices, Netflix,[49] video telephony, FaceTime[50]
Theora 2004 Internet video, web browsers
VC-1 2006 Windows media, Blu-ray Discs
Apple ProRes 2007 Professional video production.[51]
VP9 2010 A video codec developed by Google used in the WebM container format with HTML5.
High Efficiency Video Coding (HEVC, Template:Nowrap)[1][4] 2013 Successor to the Template:Nowrap standard, having substantially improved compression capability
Daala 2013 Research video format by Xiph.org
AV1[52] 2018 An open source format based on VP10 (VP9's internal successor), Daala and Thor; used by content providers such as YouTube[53][54] and Netflix.[55][56]

MDCT audio standards

Template:Further

General audio

Audio compression standard Year Common applications
Dolby Digital (AC-3)[22][23] 1991 Cinema, digital cinema, DVD, Blu-ray, streaming media, video games
Adaptive Transform Acoustic Coding (ATRAC)[22] 1992 MiniDisc
MP3[24][1] 1993 Digital audio distribution, MP3 players, portable media players, streaming media
Perceptual Audio Coder (PAC)[22] 1996 Digital audio radio service (DARS)
Advanced Audio Coding (AAC / MP4 Audio)[25][22] 1997 Digital audio distribution, portable media players, streaming media, game consoles, mobile devices, iOS, iTunes, Android, BlackBerry
High-Efficiency Advanced Audio Coding (AAC+)[57][58]Template:Rp 1997 Digital radio, digital audio broadcasting (DAB+),[58] Digital Radio Mondiale (DRM)
Cook Codec 1998 RealAudio
Windows Media Audio (WMA)[22] 1999 Windows Media
Vorbis[26][22] 2000 Digital audio distribution, radio stations, streaming media, video games, Spotify, Wikipedia
High-Definition Coding (HDC)[59] 2002 Digital radio, HD Radio
Dynamic Resolution Adaptation (DRA)[22] 2008 China national audio standard, China Multimedia Mobile Broadcasting, DVB-H
Opus[60] 2012 VoIP,[61] mobile telephony, WhatsApp,[62][63][64] PlayStation 4[65]
Dolby AC-4[66] 2015 ATSC 3.0, ultra-high-definition television (UHD TV)
MPEG-H 3D Audio[67]

Speech coding

Speech coding standard Year Common applications
AAC-LD (LD-MDCT)[68] 1999 Mobile telephony, voice-over-IP (VoIP), iOS, FaceTime[50]
Siren[69] 1999 VoIP, wideband audio, G.722.1
G.722.1[70] 1999 VoIP, wideband audio, G.722
G.729.1[71] 2006 G.729, VoIP, wideband audio,[71] mobile telephony
EVRC-WB[58]Template:Rp 2007 Wideband audio
G.718[72] 2008 VoIP, wideband audio, mobile telephony
G.719[58] 2008 Teleconferencing, videoconferencing, voice mail
CELT[73] 2011 VoIP,[74][75] mobile telephony
Enhanced Voice Services (EVS)[76] 2014 Mobile telephony, VoIP, wideband audio

Multidimensional DCT

Template:See also

Multidimensional DCTs (MD DCTs) have several applications, mainly 3-D DCTs such as the 3-D DCT-II, which has several new applications like Hyperspectral Imaging coding systems,[77] variable temporal length 3-D DCT coding,[78] video coding algorithms,[79] adaptive video coding[80] and 3-D Compression.[81] Due to enhancement in the hardware, software and introduction of several fast algorithms, the necessity of using MD DCTs is rapidly increasing. DCT-IV has gained popularity for its applications in fast implementation of real-valued polyphase filtering banks,[82] lapped orthogonal transform[83]Template:Sfn and cosine-modulated wavelet bases.[84]

Digital signal processing

DCT plays an important role in digital signal processing specifically data compression. The DCT is widely implemented in digital signal processors (DSP), as well as digital signal processing software. Many companies have developed DSPs based on DCT technology. DCTs are widely used for applications such as encoding, decoding, video, audio, multiplexing, control signals, signaling, and analog-to-digital conversion. DCTs are also commonly used for high-definition television (HDTV) encoder/decoder chips.[1]

Compression artifacts

A common issue with DCT compression in digital media are blocky compression artifacts,[85] caused by DCT blocks.[3] In a DCT algorithm, an image (or frame in an image sequence) is divided into square blocks which are processed independently from each other, then the DCT blocks is taken within each block and the resulting DCT coefficients are quantized. This process can cause blocking artifacts, primarily at high data compression ratios.[85] This can also cause the mosquito noise effect, commonly found in digital video.[86]

DCT blocks are often used in glitch art.[3] The artist Rosa Menkman makes use of DCT-based compression artifacts in her glitch art,[87] particularly the DCT blocks found in most digital media formats such as JPEG digital images and MP3 audio.[3] Another example is Jpegs by German photographer Thomas Ruff, which uses intentional JPEG artifacts as the basis of the picture's style.[88][89]

Informal overview

Like any Fourier-related transform, DCTs express a function or a signal in terms of a sum of sinusoids with different frequencies and amplitudes. Like the DFT, a DCT operates on a function at a finite number of discrete data points. The obvious distinction between a DCT and a DFT is that the former uses only cosine functions, while the latter uses both cosines and sines (in the form of complex exponentials). However, this visible difference is merely a consequence of a deeper distinction: a DCT implies different boundary conditions from the DFT or other related transforms.

The Fourier-related transforms that operate on a function over a finite domain, such as the DFT or DCT or a Fourier series, can be thought of as implicitly defining an extension of that function outside the domain. That is, once you write a function f(x) as a sum of sinusoids, you can evaluate that sum at any x, even for x where the original f(x) was not specified. The DFT, like the Fourier series, implies a periodic extension of the original function. A DCT, like a cosine transform, implies an even extension of the original function.

File:DCT-symmetries.svg
Illustration of the implicit even/odd extensions of DCT input data, for N=11 data points (red dots), for the four most common types of DCT (types I-IV). Note the subtle differences at the interfaces between the data and the extensions: in DCT-II and DCT-IV both the end points are replicated in the extensions but not in DCT-I or DCT-III (and a zero point is inserted at the sign reversal extension in DCT-III).

However, because DCTs operate on finite, discrete sequences, two issues arise that do not apply for the continuous cosine transform. First, one has to specify whether the function is even or odd at both the left and right boundaries of the domain (i.e. the min-n and max-n boundaries in the definitions below, respectively). Second, one has to specify around what point the function is even or odd. In particular, consider a sequence abcd of four equally spaced data points, and say that we specify an even left boundary. There are two sensible possibilities: either the data are even about the sample a, in which case the even extension is dcbabcd, or the data are even about the point halfway between a and the previous point, in which case the even extension is dcbaabcd (a is repeated).

Each boundary can be either even or odd (2 choices per boundary) and can be symmetric about a data point or the point halfway between two data points (2 choices per boundary), for a total of 2 × 2 × 2 × 2 = 16 possibilities. These choices lead to all the standard variations of DCTs and also discrete sine transforms (DSTs). Half of these possibilities, those where the left boundary is even, correspond to the 8 types of DCT; the other half are the 8 types of DST.

These different boundary conditions strongly affect the applications of the transform and lead to uniquely useful properties for the various DCT types. Most directly, when using Fourier-related transforms to solve partial differential equations by spectral methods, the boundary conditions are directly specified as a part of the problem being solved. Or, for the MDCT (based on the type-IV DCT), the boundary conditions are intimately involved in the MDCT's critical property of time-domain aliasing cancellation. In a more subtle fashion, the boundary conditions are responsible for the energy compactification properties that make DCTs useful for image and audio compression, because the boundaries affect the rate of convergence of any Fourier-like series.

In particular, it is well known that any discontinuities in a function reduce the rate of convergence of the Fourier series so that more sinusoids are needed to represent the function with a given accuracy. The same principle governs the usefulness of the DFT and other transforms for signal compression; the smoother a function is, the fewer terms in its DFT or DCT are required to represent it accurately, and the more it can be compressed.Template:Efn However, the implicit periodicity of the DFT means that discontinuities usually occur at the boundaries: any random segment of a signal is unlikely to have the same value at both the left and right boundaries.Template:Efn In contrast, a DCT where both boundaries are even always yields a continuous extension at the boundaries (although the slope is generally discontinuous). This is why DCTs, and in particular DCTs of types I, II, V, and VI (the types that have two even boundaries) generally perform better for signal compression than DFTs and DSTs. In practice, a type-II DCT is usually preferred for such applications, in part for reasons of computational convenience.

Formal definition

Formally, the discrete cosine transform is a linear, invertible function f:NN (where denotes the set of real numbers), or equivalently an invertible Template:Mvar × Template:Mvar square matrix. There are several variants of the DCT with slightly modified definitions. The Template:Mvar real numbers x0,  xN1 are transformed into the Template:Mvar real numbers X0,,XN1 according to one of the formulas:

DCT-I

Xk=12(x0+(1)kxN1)+n=1N2xncos[ πN1nk] for k=0,  N1.

Some authors further multiply the x0 and xN1 terms by 2, and correspondingly multiply the X0 and XN1 terms by 1/2, which, if one further multiplies by an overall scale factor of 2N1,, makes the DCT-I matrix orthogonal but breaks the direct correspondence with a real-even DFT.

The DCT-I is exactly equivalent (up to an overall scale factor of 2), to a DFT of 2(N1) real numbers with even symmetry. For example, a DCT-I of N=5 real numbers a b c d e is exactly equivalent to a DFT of eight real numbers Template:Not a typo (even symmetry), divided by two. (In contrast, DCT types II-IV involve a half-sample shift in the equivalent DFT.)

Note, however, that the DCT-I is not defined for N less than 2, while all other DCT types are defined for any positive N.

Thus, the DCT-I corresponds to the boundary conditions: xn is even around n=0 and even around n=N1; similarly for Xk.

DCT-II

Xk=n=0N1xncos[πN(n+12)k] for k=0,  N1.

The DCT-II is probably the most commonly used form, and is often simply referred to as "the DCT".[5][6]

This transform is exactly equivalent (up to an overall scale factor of 2) to a DFT of 4N real inputs of even symmetry where the even-indexed elements are zero. That is, it is half of the DFT of the 4N inputs yn, where y2n=0, y2n+1=xn for 0n<N, y2N=0, and y4Nn=yn for 0<n<2N. DCT-II transformation is also possible using 2Template:Mvar signal followed by a multiplication by half shift. This is demonstrated by Makhoul.

Some authors further multiply the X0 term by 1/N and multiply the rest of the matrix by an overall scale factor of 2/N (see below for the corresponding change in DCT-III). This makes the DCT-II matrix orthogonal, but breaks the direct correspondence with a real-even DFT of half-shifted input. This is the normalization used by Matlab, for example, see.[90] In many applications, such as JPEG, the scaling is arbitrary because scale factors can be combined with a subsequent computational step (e.g. the quantization step in JPEG[91]), and a scaling can be chosen that allows the DCT to be computed with fewer multiplications.[92][93]

The DCT-II implies the boundary conditions: xn is even around n=1/2 and even around n=N1/2; Xk is even around k=0 and odd around k=N.

DCT-III

Xk=12x0+n=1N1xncos[πN(k+12)n] for k=0,  N1.

Because it is the inverse of DCT-II up to a scale factor (see below), this form is sometimes simply referred to as "the inverse DCT" ("IDCT").[6]

Some authors divide the x0 term by 2 instead of by 2 (resulting in an overall x0/2 term) and multiply the resulting matrix by an overall scale factor of 2/N (see above for the corresponding change in DCT-II), so that the DCT-II and DCT-III are transposes of one another. This makes the DCT-III matrix orthogonal, but breaks the direct correspondence with a real-even DFT of half-shifted output.

The DCT-III implies the boundary conditions: xn is even around n=0 and odd around n=N; Xk is even around k=1/2 and even around k=N1/2.

DCT-IV

Xk=n=0N1xncos[πN(n+12)(k+12)] for k=0,  N1.

The DCT-IV matrix becomes orthogonal (and thus, being clearly symmetric, its own inverse) if one further multiplies by an overall scale factor of 2/N.

A variant of the DCT-IV, where data from different transforms are overlapped, is called the modified discrete cosine transform (MDCT).[94]

The DCT-IV implies the boundary conditions: xn is even around n=1/2 and odd around n=N1/2; similarly for Xk.

DCT V-VIII

DCTs of types I–IV treat both boundaries consistently regarding the point of symmetry: they are even/odd around either a data point for both boundaries or halfway between two data points for both boundaries. By contrast, DCTs of types V-VIII imply boundaries that are even/odd around a data point for one boundary and halfway between two data points for the other boundary.

In other words, DCT types I–IV are equivalent to real-even DFTs of even order (regardless of whether N is even or odd), since the corresponding DFT is of length 2(N1) (for DCT-I) or 4N (for DCT-II & III) or 8N (for DCT-IV). The four additional types of discrete cosine transform[95] correspond essentially to real-even DFTs of logically odd order, which have factors of N±1/2 in the denominators of the cosine arguments.

However, these variants seem to be rarely used in practice. One reason, perhaps, is that FFT algorithms for odd-length DFTs are generally more complicated than FFT algorithms for even-length DFTs (e.g. the simplest radix-2 algorithms are only for even lengths), and this increased intricacy carries over to the DCTs as described below.

(The trivial real-even array, a length-one DFT (odd length) of a single number Template:Mvar , corresponds to a DCT-V of length N=1.)

Inverse transforms

Using the normalization conventions above, the inverse of DCT-I is DCT-I multiplied by 2/(N − 1). The inverse of DCT-IV is DCT-IV multiplied by 2/N. The inverse of DCT-II is DCT-III multiplied by 2/N and vice versa.[6]

Like for the DFT, the normalization factor in front of these transform definitions is merely a convention and differs between treatments. For example, some authors multiply the transforms by 2/N so that the inverse does not require any additional multiplicative factor. Combined with appropriate factors of Template:Sqrt (see above), this can be used to make the transform matrix orthogonal.

Multidimensional DCTs

Multidimensional variants of the various DCT types follow straightforwardly from the one-dimensional definitions: they are simply a separable product (equivalently, a composition) of DCTs along each dimension.

M-D DCT-II

For example, a two-dimensional DCT-II of an image or a matrix is simply the one-dimensional DCT-II, from above, performed along the rows and then along the columns (or vice versa). That is, the 2D DCT-II is given by the formula (omitting normalization and other scale factors, as above):

Xk1,k2=n1=0N11(n2=0N21xn1,n2cos[πN2(n2+12)k2])cos[πN1(n1+12)k1]=n1=0N11n2=0N21xn1,n2cos[πN1(n1+12)k1]cos[πN2(n2+12)k2].
The inverse of a multi-dimensional DCT is just a separable product of the inverses of the corresponding one-dimensional DCTs (see above), e.g. the one-dimensional inverses applied along one dimension at a time in a row-column algorithm.

The 3-D DCT-II is only the extension of 2-D DCT-II in three dimensional space and mathematically can be calculated by the formula

Xk1,k2,k3=n1=0N11n2=0N21n3=0N31xn1,n2,n3cos[πN1(n1+12)k1]cos[πN2(n2+12)k2]cos[πN3(n3+12)k3],for ki=0,1,2,,Ni1.

The inverse of 3-D DCT-II is 3-D DCT-III and can be computed from the formula given by

xn1,n2,n3=k1=0N11k2=0N21k3=0N31Xk1,k2,k3cos[πN1(n1+12)k1]cos[πN2(n2+12)k2]cos[πN3(n3+12)k3],for ni=0,1,2,,Ni1.

Technically, computing a two-, three- (or -multi) dimensional DCT by sequences of one-dimensional DCTs along each dimension is known as a row-column algorithm. As with multidimensional FFT algorithms, however, there exist other methods to compute the same thing while performing the computations in a different order (i.e. interleaving/combining the algorithms for the different dimensions). Owing to the rapid growth in the applications based on the 3-D DCT, several fast algorithms are developed for the computation of 3-D DCT-II. Vector-Radix algorithms are applied for computing M-D DCT to reduce the computational complexity and to increase the computational speed. To compute 3-D DCT-II efficiently, a fast algorithm, Vector-Radix Decimation in Frequency (VR DIF) algorithm was developed.

3-D DCT-II VR DIF

In order to apply the VR DIF algorithm the input data is to be formulated and rearranged as follows.[96][97] The transform size N × N × N is assumed to be 2.

File:Stages of the 3-D DCT-II VR DIF algorithm.jpg
The four basic stages of computing 3-D DCT-II using VR DIF Algorithm.
x~(n1,n2,n3)=x(2n1,2n2,2n3)x~(n1,n2,Nn31)=x(2n1,2n2,2n3+1)x~(n1,Nn21,n3)=x(2n1,2n2+1,2n3)x~(n1,Nn21,Nn31)=x(2n1,2n2+1,2n3+1)x~(Nn11,n2,n3)=x(2n1+1,2n2,2n3)x~(Nn11,n2,Nn31)=x(2n1+1,2n2,2n3+1)x~(Nn11,Nn21,n3)=x(2n1+1,2n2+1,2n3)x~(Nn11,Nn21,Nn31)=x(2n1+1,2n2+1,2n3+1)
where 0n1,n2,n3N21

The figure to the adjacent shows the four stages that are involved in calculating 3-D DCT-II using VR DIF algorithm. The first stage is the 3-D reordering using the index mapping illustrated by the above equations. The second stage is the butterfly calculation. Each butterfly calculates eight points together as shown in the figure just below, where c(φi)=cos(φi).

The original 3-D DCT-II now can be written as

X(k1,k2,k3)=n1=1N1n2=1N1n3=1N1x~(n1,n2,n3)cos(φk1)cos(φk2)cos(φk3)

where φi=π2N(4Ni+1), and i=1,2,3.

If the even and the odd parts of

k1,k2

and

k3

and are considered, the general formula for the calculation of the 3-D DCT-II can be expressed as

The single butterfly stage of VR DIF algorithm.
X(k1,k2,k3)=n1=1N21n2=1N21n1=1N21x~ijl(n1,n2,n3)cos(φ(2k1+i)cos(φ(2k2+j)cos(φ(2k3+l))

where

x~ijl(n1,n2,n3)=x~(n1,n2,n3)+(1)lx~(n1,n2,n3+n2)
+(1)jx~(n1,n2+n2,n3)+(1)j+lx~(n1,n2+n2,n3+n2)
+(1)ix~(n1+n2,n2,n3)+(1)i+jx~(n1+n2+n2,n2,n3)
+(1)i+lx~(n1+n2,n2,n3+n3)
+(1)i+j+lx~(n1+n2,n2+n2,n3+n2) where i,j,l=0 or 1.
Arithmetic complexity

The whole 3-D DCT calculation needs [log2N] stages, and each stage involves 18 N3 butterflies. The whole 3-D DCT requires [18 N3log2N] butterflies to be computed. Each butterfly requires seven real multiplications (including trivial multiplications) and 24 real additions (including trivial additions). Therefore, the total number of real multiplications needed for this stage is [78 N3 log2N], and the total number of real additions i.e. including the post-additions (recursive additions) which can be calculated directly after the butterfly stage or after the bit-reverse stage are given by[97] [32N3log2N]Real+[32N3log2N3N3+3N2]Recursive=[92N3log2N3N3+3N2].

The conventional method to calculate MD-DCT-II is using a Row-Column-Frame (RCF) approach which is computationally complex and less productive on most advanced recent hardware platforms. The number of multiplications required to compute VR DIF Algorithm when compared to RCF algorithm are quite a few in number. The number of Multiplications and additions involved in RCF approach are given by [32N3log2N] and [92N3log2N3N3+3N2], respectively. From Table 1, it can be seen that the total number

TABLE 1 Comparison of VR DIF & RCF Algorithms for computing 3D-DCT-II
Transform Size 3D VR Mults RCF Mults 3D VR Adds RCF Adds
8 × 8 × 8 2.625 4.5 10.875 10.875
16 × 16 × 16 3.5 6 15.188 15.188
32 × 32 × 32 4.375 7.5 19.594 19.594
64 × 64 × 64 5.25 9 24.047 24.047

of multiplications associated with the 3-D DCT VR algorithm is less than that associated with the RCF approach by more than 40%. In addition, the RCF approach involves matrix transpose and more indexing and data swapping than the new VR algorithm. This makes the 3-D DCT VR algorithm more efficient and better suited for 3-D applications that involve the 3-D DCT-II such as video compression and other 3-D image processing applications.

The main consideration in choosing a fast algorithm is to avoid computational and structural complexities. As the technology of computers and DSPs advances, the execution time of arithmetic operations (multiplications and additions) is becoming very fast, and regular computational structure becomes the most important factor.[98] Therefore, although the above proposed 3-D VR algorithm does not achieve the theoretical lower bound on the number of multiplications,[99] it has a simpler computational structure as compared to other 3-D DCT algorithms. It can be implemented in place using a single butterfly and possesses the properties of the Cooley–Tukey FFT algorithm in 3-D. Hence, the 3-D VR presents a good choice for reducing arithmetic operations in the calculation of the 3-D DCT-II, while keeping the simple structure that characterize butterfly-style Cooley–Tukey FFT algorithms.

File:DCT-8x8.png
Two-dimensional DCT frequencies from the JPEG DCT

The image to the right shows a combination of horizontal and vertical frequencies for an Template:Nobr (N1=N2=8) two-dimensional DCT. Each step from left to right and top to bottom is an increase in frequency by 1/2 cycle. For example, moving right one from the top-left square yields a half-cycle increase in the horizontal frequency. Another move to the right yields two half-cycles. A move down yields two half-cycles horizontally and a half-cycle vertically. The source data Template:Nobr is transformed to a linear combination of these 64 frequency squares.

MD-DCT-IV

The M-D DCT-IV is just an extension of 1-D DCT-IV on to Template:Mvar dimensional domain. The 2-D DCT-IV of a matrix or an image is given by

Xk,=n=0N1m=0M1 xn,mcos( (2m+1)(2k+1) π4N )cos( (2n+1)(2+1) π4M ),
for k=0, 1, 2  N1 and =0, 1, 2,  M1.

We can compute the MD DCT-IV using the regular row-column method or we can use the polynomial transform method[100] for the fast and efficient computation. The main idea of this algorithm is to use the Polynomial Transform to convert the multidimensional DCT into a series of 1-D DCTs directly. MD DCT-IV also has several applications in various fields.

Computation

Although the direct application of these formulas would require 𝒪(N2) operations, it is possible to compute the same thing with only 𝒪(NlogN) complexity by factorizing the computation similarly to the fast Fourier transform (FFT). One can also compute DCTs via FFTs combined with 𝒪(N) pre- and post-processing steps. In general, 𝒪(NlogN) methods to compute DCTs are known as fast cosine transform (FCT) algorithms.

The most efficient algorithms, in principle, are usually those that are specialized directly for the DCT, as opposed to using an ordinary FFT plus 𝒪(N) extra operations (see below for an exception). However, even "specialized" DCT algorithms (including all of those that achieve the lowest known arithmetic counts, at least for power-of-two sizes) are typically closely related to FFT algorithms – since DCTs are essentially DFTs of real-even data, one can design a fast DCT algorithm by taking an FFT and eliminating the redundant operations due to this symmetry. This can even be done automatically Template:Harv. Algorithms based on the Cooley–Tukey FFT algorithm are most common, but any other FFT algorithm is also applicable. For example, the Winograd FFT algorithm leads to minimal-multiplication algorithms for the DFT, albeit generally at the cost of more additions, and a similar algorithm was proposed by Template:Harv for the DCT. Because the algorithms for DFTs, DCTs, and similar transforms are all so closely related, any improvement in algorithms for one transform will theoretically lead to immediate gains for the other transforms as well Template:Harv.

While DCT algorithms that employ an unmodified FFT often have some theoretical overhead compared to the best specialized DCT algorithms, the former also have a distinct advantage: Highly optimized FFT programs are widely available. Thus, in practice, it is often easier to obtain high performance for general lengths Template:Mvar with FFT-based algorithms.Template:Efn Specialized DCT algorithms, on the other hand, see widespread use for transforms of small, fixed sizes such as the Template:Nobr DCT-II used in JPEG compression, or the small DCTs (or MDCTs) typically used in audio compression. (Reduced code size may also be a reason to use a specialized DCT for embedded-device applications.)

In fact, even the DCT algorithms using an ordinary FFT are sometimes equivalent to pruning the redundant operations from a larger FFT of real-symmetric data, and they can even be optimal from the perspective of arithmetic counts. For example, a type-II DCT is equivalent to a DFT of size 4N with real-even symmetry whose even-indexed elements are zero. One of the most common methods for computing this via an FFT (e.g. the method used in FFTPACK and FFTW) was described by Template:Harvtxt and Template:Harvtxt, and this method in hindsight can be seen as one step of a radix-4 decimation-in-time Cooley–Tukey algorithm applied to the "logical" real-even DFT corresponding to the DCT-II.Template:Efn Because the even-indexed elements are zero, this radix-4 step is exactly the same as a split-radix step. If the subsequent size N real-data FFT is also performed by a real-data split-radix algorithm (as in Template:Harvtxt), then the resulting algorithm actually matches what was long the lowest published arithmetic count for the power-of-two DCT-II (2Nlog2NN+2 real-arithmetic operationsTemplate:Efn).

A recent reduction in the operation count to 179Nlog2N+𝒪(N) also uses a real-data FFT.[101] So, there is nothing intrinsically bad about computing the DCT via an FFT from an arithmetic perspective – it is sometimes merely a question of whether the corresponding FFT algorithm is optimal. (As a practical matter, the function-call overhead in invoking a separate FFT routine might be significant for small N, but this is an implementation rather than an algorithmic question since it can be solved by unrolling or inlining.)

Example of IDCT

File:DCT filter comparison.png
An example showing eight different filters applied to a test image (top left) by multiplying its DCT spectrum (top right) with each filter.

Consider this 8x8 grayscale image of capital letter A.

File:Letter-a-8x8.png
Original size, scaled 10x (nearest neighbor), scaled 10x (bilinear).
Basis functions of the discrete cosine transformation with corresponding coefficients (specific for our image).
DCT of the image = [6.19170.34111.24180.14920.15830.27420.07240.05610.22050.02140.45030.39470.78460.43910.10010.25541.04230.22141.00170.27200.07890.19520.28010.47130.23400.03920.26170.28660.63510.35010.14330.35500.27500.02260.12290.21830.25830.07420.20420.59060.06530.04280.47210.29050.47450.28750.02840.13110.31690.05410.10330.02250.00560.10170.16500.15000.29700.06270.19600.06440.11360.10310.18870.1444].

Each basis function is multiplied by its coefficient and then this product is added to the final image.

File:Idct-animation.gif
On the left is the final image. In the middle is the weighted function (multiplied by a coefficient) which is added to the final image. On the right is the current function and corresponding coefficient. Images are scaled (using bilinear interpolation) by factor 10×.

See also

Notes

Template:Reflist

References

Template:Reflist

Further reading

Template:Commons category

Template:Compression Methods Template:Compression formats Template:DSP Template:Telecommunications

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 Cite error: Invalid <ref> tag; no text was provided for refs named Stankovic
  2. 2.0 2.1 2.2 2.3 2.4 Cite error: Invalid <ref> tag; no text was provided for refs named Britanak2010
  3. 3.0 3.1 3.2 3.3 Template:Cite web
  4. 4.0 4.1 4.2 4.3 4.4 4.5 Template:Cite web
  5. 5.0 5.1 5.2 5.3 5.4 5.5 Cite error: Invalid <ref> tag; no text was provided for refs named pubDCT
  6. 6.0 6.1 6.2 6.3 6.4 6.5 Cite error: Invalid <ref> tag; no text was provided for refs named pubRaoYip
  7. 7.0 7.1 7.2 7.3 Template:Cite journal
  8. 8.0 8.1 8.2 8.3 Template:Cite journal
  9. 9.0 9.1 Cite error: Invalid <ref> tag; no text was provided for refs named Ahmed
  10. 10.0 10.1 10.2 10.3 10.4 Template:Cite web
  11. Template:Cite journal
  12. Template:Cite journal
  13. Template:Cite journal
  14. Template:Cite book
  15. Template:Cite journal
  16. Template:Cite book
  17. 17.0 17.1 17.2 Template:Cite web
  18. 18.0 18.1 Template:Cite book
  19. Template:Cite book
  20. Template:Cite book
  21. Template:Cite journal
  22. 22.0 22.1 22.2 22.3 22.4 22.5 22.6 22.7 22.8 Cite error: Invalid <ref> tag; no text was provided for refs named Luo
  23. 23.0 23.1 Cite error: Invalid <ref> tag; no text was provided for refs named Britanak2011
  24. 24.0 24.1 Template:Cite web
  25. 25.0 25.1 Template:Cite web
  26. 26.0 26.1 Cite error: Invalid <ref> tag; no text was provided for refs named vorbis-mdct
  27. Template:Cite journal
  28. Template:Cite book
  29. Template:Cite book
  30. Template:Cite book
  31. Template:Cite web
  32. Template:Cite news
  33. Template:Cite journal
  34. Template:Cite book
  35. Template:Cite book
  36. 36.0 36.1 Template:Cite journal
  37. Template:Cite web
  38. Template:Cite journal
  39. Template:Cite web
  40. Template:Cite news
  41. Template:Cite web
  42. Template:Cite web
  43. 43.0 43.1 Template:Cite web
  44. Template:Cite web
  45. Template:Cite book
  46. 46.0 46.1 Template:Cite book
  47. Template:Cite news
  48. Template:Cite book
  49. Template:Cite news
  50. 50.0 50.1 Template:Cite web
  51. Template:Cite web
  52. Template:Cite web
  53. Template:Cite web
  54. Template:Cite web
  55. Template:Cite web
  56. Template:Cite web
  57. Cite error: Invalid <ref> tag; no text was provided for refs named Herre
  58. 58.0 58.1 58.2 58.3 Cite error: Invalid <ref> tag; no text was provided for refs named Britanak
  59. Cite error: Invalid <ref> tag; no text was provided for refs named Jones
  60. Cite error: Invalid <ref> tag; no text was provided for refs named Valin
  61. Cite error: Invalid <ref> tag; no text was provided for refs named homepage
  62. Cite error: Invalid <ref> tag; no text was provided for refs named Register
  63. Cite error: Invalid <ref> tag; no text was provided for refs named Hazra
  64. Cite error: Invalid <ref> tag; no text was provided for refs named Srivastava
  65. Cite error: Invalid <ref> tag; no text was provided for refs named PlayStation
  66. Cite error: Invalid <ref> tag; no text was provided for refs named Dolby AC-4
  67. Cite error: Invalid <ref> tag; no text was provided for refs named Bleidt
  68. Cite error: Invalid <ref> tag; no text was provided for refs named Schnell
  69. Cite error: Invalid <ref> tag; no text was provided for refs named Hersent
  70. Cite error: Invalid <ref> tag; no text was provided for refs named Lutzky
  71. 71.0 71.1 Cite error: Invalid <ref> tag; no text was provided for refs named Nagireddi
  72. Cite error: Invalid <ref> tag; no text was provided for refs named ITU-T
  73. Cite error: Invalid <ref> tag; no text was provided for refs named Terriberry
  74. Cite error: Invalid <ref> tag; no text was provided for refs named ekiga
  75. Cite error: Invalid <ref> tag; no text was provided for refs named FreeSWITCH
  76. Cite error: Invalid <ref> tag; no text was provided for refs named EVS
  77. Template:Citation
  78. Template:Citation
  79. Template:Citation
  80. Template:Citation
  81. Template:Citation
  82. Template:Cite book
  83. Template:Cite journal
  84. Template:Cite journal
  85. 85.0 85.1 Template:Cite book
  86. Template:Cite web
  87. Template:Cite book
  88. Template:Cite book
  89. Template:Cite web
  90. Template:Cite web
  91. Template:Cite book
  92. Template:Cite journal
  93. Template:Cite journal
  94. Template:Harvnb
  95. Template:Harvnb
  96. Template:Cite journal
  97. 97.0 97.1 Template:Cite journal
  98. Template:Cite journal
  99. Template:Cite journal
  100. Template:Cite book
  101. Template:Cite journal