http://avisynth.nl/index.php?action=history&feed=atom&title=RGB32RGB32 - Revision history2026-04-23T06:13:32ZRevision history for this page on the wikiMediaWiki 1.19.24http://avisynth.nl/index.php?title=RGB32&diff=884&oldid=prevAdmin: 1 revision2013-05-09T21:34:06Z<p>1 revision</p>
<table class='diff diff-contentalign-left'>
<tr valign='top'>
<td colspan='1' style="background-color: white; color:black;">← Older revision</td>
<td colspan='1' style="background-color: white; color:black;">Revision as of 21:34, 9 May 2013</td>
</tr></table>Adminhttp://avisynth.nl/index.php?title=RGB32&diff=883&oldid=prev31.172.30.4 at 19:04, 1 October 20122012-10-01T19:04:54Z<p></p>
<p><b>New page</b></p><div>RGB32 is an [[RGB]] video format where each pixel of the image contains one byte for each of the R (red), G (green) and B (blue) components plus an additional byte for transparency mask (A component) in successive places of memory. Since one byte occupies 8 bits, the total number of bits consumed by one pixel is 4*8 = 32 and thus the 32 at the end of the format's name.<br />
<br />
As it is apparent, the layout of bytes in memory for an RGB32 video frame follows (assuming a least-significant-bit-is-first memory layout) the pattern below:<br />
<br />
low memory address ----> high memory address<br />
| pixel | pixel | pixel | pixel | pixel | pixel |...<br />
|-------|-------|-------|-------|-------|-------|...<br />
|B|G|R|A|B|G|R|A|B|G|R|A|B|G|R|A|B|G|R|A|B|G|R|A|...<br />
<br />
Using the RGB32 video format provides in modern processors faster access to video data because the data is aligned to machine's word boundaries. For this reason many applications use it instead of [[RGB24]] even when there is no transparency mask information in the fourth (A) byte, since in general the improved processing speed outweighs the memory overhead introduced by the unused A byte per pixel.<br />
<br />
[[Category:Glossary]]</div>31.172.30.4