Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Multisample anti-aliasing
open-in-new
<h2 id="definition">Definition</h2> <p>The term generally refers to a special case of <a href="/facts/Supersampling/15ysD7bJ">supersampling</a>. Initial implementations of full-scene anti-aliasing (<a href="/facts/FSAA/od0SgvLy">FSAA</a>) worked conceptually by simply rendering a scene at a higher resolution, and then downsampling to a lower-resolution output. Most modern <a href="/facts/Graphics_processing_unit/PTK1RQVp">GPUs</a> are capable of this form of anti-aliasing, but it greatly taxes resources such as texture, bandwidth, and <a href="/facts/Fillrate/c30gsbbt">fillrate</a>. (If a program is highly <a href="/facts/Transform,_clipping,_and_lighting/wnDkGH4W">TCL</a>-bound or <a href="/facts/Central_processing_unit/Jxp1bqMV">CPU</a>-bound, supersampling can be used without much performance hit.) </p><p>According to the <a href="/facts/OpenGL/xQoMWePr">OpenGL</a> GL_ARB_multisample specification,<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> "multisampling" refers to a specific optimization of supersampling. The specification dictates that the renderer evaluate the fragment program once per pixel, and only "truly" supersample the <a href="/facts/Z-buffer/HTyzcKbx">depth</a> and <a href="/facts/Stencil_buffer/BNGPjMJE">stencil</a> values. (This is not the same as supersampling but, by the OpenGL 1.5 specification,<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> the definition had been updated to include fully supersampling implementations as well.) </p><p>In graphics literature in general, "multisampling" refers to any special case of supersampling where some components of the final image are not fully supersampled. The lists below refer specifically to the ARB_multisample definition. </p> <h2 id="description">Description</h2> <p>In supersample anti-aliasing, multiple locations are sampled within every pixel, and each of those samples<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> is fully rendered and combined with the others to produce the pixel that is ultimately displayed. This is computationally expensive, because the entire rendering process must be repeated for each sample location. It is also inefficient, as aliasing is typically only noticed in <i>some</i> parts of the image, such as the edges, whereas supersampling is performed for every single pixel. </p><p>In multisample anti-aliasing, if any of the multi sample locations in a pixel is covered by the triangle being rendered, a shading computation must be performed for that triangle. However this calculation only needs to be performed <i>once</i> for the whole pixel regardless of how many sample positions are covered; the result of the shading calculation is simply applied to <i>all</i> of the relevant multi sample locations. </p><p>In the case where only one triangle covers every multi sample location within the pixel, only one shading computation is performed, and these pixels are little more expensive than (and the result is no different from) the non-anti-aliased image. This is true of the middle of triangles, where aliasing is not an issue. (<a href="/facts/Edge_detection/9VplpIcS">Edge detection</a> can reduce this further by explicitly limiting the MSAA calculation to pixels whose samples involve multiple triangles, or triangles at multiple depths.) In the extreme case where each of the multi sample locations is covered by a different triangle, a different shading computation will be performed for each location and the results then combined to give the final pixel, and the result and computational expense are the same as in the equivalent supersampled image. </p><p>The shading calculation is not the only operation that must be performed on a given pixel; multisampling implementations may variously sample other operations such as visibility at different sampling levels. </p> <h2 id="advantages">Advantages</h2> <ul><li>The <a href="/facts/Pixel_shader/qfhkKFwA">pixel shader</a> usually only needs to be evaluated once per pixel for every triangle covering at least one sample point.</li> <li>The edges of polygons (the most obvious source of <a href="/facts/Aliasing/Pzg84HL0">aliasing</a> in 3D graphics) are anti-aliased.</li> <li>Since multiple subpixels per pixel are sampled, polygonal details smaller than one pixel that might have been missed without MSAA can be captured and made a part of the final rendered image if enough samples are taken.</li></ul> <h2 id="disadvantages">Disadvantages</h2> <h3>Alpha testing</h3> <p>Alpha testing is a technique common to older video games used to render translucent objects by rejecting pixels from being written to the framebuffer.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> If the alpha value of a translucent fragment (pixel) is below a specified threshold, it will be discarded. Because this is performed on a pixel by pixel basis, the image does not receive the benefits of multi-sampling (all of the multisamples in a pixel are discarded based on the alpha test) for these pixels. The resulting image may contain aliasing along the edges of transparent objects or edges within textures, although the image quality will be no worse than it would be without any anti-aliasing.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> Translucent objects that are modelled using alpha-test textures will also be aliased due to alpha testing. This effect can be minimized by rendering objects with transparent textures multiple times, although this would result in a high performance reduction for scenes containing many transparent objects.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> </p> <h3>Aliasing</h3> <p>Because multi-sampling calculates interior polygon fragments only once per pixel, aliasing and other artifacts will still be visible inside rendered polygons where fragment shader output contains high frequency components. </p> <h3>Performance</h3> <p>While less performance-intensive than SSAA (supersampling), it is possible in certain scenarios (scenes heavy in complex fragments) for MSAA to be multiple times more intensive for a given frame than post processing anti-aliasing techniques such as <a href="/facts/FXAA/gokqlrr8">FXAA</a>, SMAA and <a href="/facts/MLAA/gqRR5M4G">MLAA</a>. Early techniques in this category tend towards a lower performance impact, but suffer from accuracy problems.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> More recent post-processing based anti-aliasing techniques such as <a href="/facts/Temporal_anti-aliasing/ktQNm1FH">temporal anti-aliasing</a> (TAA), which reduces aliasing by combining data from previously rendered frames, have seen the reversal of this trend, as post-processing AA becomes both more versatile and more expensive than MSAA, which cannot antialias an entire frame alone. </p> <h2 id="sampling-methods">Sampling methods</h2> <h3>Point sampling</h3> <p>In a point-sampled mask, the coverage bit for each multisample is only set if the multisample is located inside the rendered primitive. Samples are never taken from outside a rendered primitive, so images produced using point-sampling will be geometrically correct, but filtering quality may be low because the proportion of bits set in the pixel's coverage mask may not be equal to the proportion of the pixel that is actually covered by the fragment in question. </p> <h3>Area sampling</h3> <p>Filtering quality can be improved by using area sampled masks. In this method, the number of bits set in a coverage mask for a pixel should be proportionate to the actual area coverage of the fragment. This will result in some coverage bits being set for multisamples that are not actually located within the rendered primitive, and can cause aliasing and other artifacts. </p> <h2 id="sample-patterns">Sample patterns</h2> <h3>Regular grid</h3> <p>A regular grid sample pattern, where multisample locations form an evenly spaced grid throughout the pixel, is easy to implement and simplifies attribute evaluation (i.e. setting subpixel masks, sampling color and depth). This method is computationally expensive due to the large number of samples. Edge optimization is poor for screen-aligned edges, but image quality is good when the number of multisamples is large. </p> <h3>Sparse regular grid</h3> <p>A sparse regular grid sample pattern is a subset of samples that are chosen from the regular grid sample pattern. As with the regular grid, attribute evaluation is simplified due to regular spacing. The method is less computationally expensive due to having a fewer samples. Edge optimization is good for screen aligned edges, and image quality is good for a moderate number of multisamples. </p> <h3>Stochastic sample patterns</h3> <p>A stochastic sample pattern is a random distribution of multisamples throughout the pixel. The irregular spacing of samples makes attribute evaluation complicated. The method is cost efficient due to low sample count (compared to regular grid patterns). Edge optimization with this method, although sub-optimal for screen aligned edges. Image quality is excellent for a moderate number of samples. </p> <h2 id="quality">Quality</h2> <p>Compared to supersampling, multisample anti-aliasing can provide similar quality at higher performance, or better quality for the same performance. Further improved results can be achieved by using rotated grid subpixel masks. The additional bandwidth required by multi-sampling is reasonably low if Z and colour compression are available.<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> </p><p>Most modern <a href="/facts/Graphics_processing_unit/PTK1RQVp">GPUs</a> support 2×, 4×, and 8× MSAA samples. Higher values result in better quality, but are slower. </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Alpha_to_coverage/kc25X3g8">Alpha to coverage</a></li> <li><a href="/facts/Morphological_antialiasing/gqRR5M4G">Morphological antialiasing</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"Additions to Chapter 3 of the 1.2.1 specification". <a href="http://www.opengl.org/registry/specs/ARB/multisample.txt" target="_blank">http://www.opengl.org/registry/specs/ARB/multisample.txt</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>"OpenGL 1.5 specification" (PDF). <a href="http://www.opengl.org/documentation/specs/version1.5/glspec15.pdf" target="_blank">http://www.opengl.org/documentation/specs/version1.5/glspec15.pdf</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>"The Meaning of Anti-Aliasing: What is it Used for?". ARVI VR. 2018-09-14. Retrieved 2018-09-14. <a href="https://vr.arvilab.com/blog/anti-aliasing" target="_blank">https://vr.arvilab.com/blog/anti-aliasing</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>"ShaderLab syntax: Alpha testing". Unity3d.com. 2008-04-27. Retrieved 2012-07-31. <a href="http://docs.unity3d.com/Documentation/Components/SL-AlphaTest.html" target="_blank">http://docs.unity3d.com/Documentation/Components/SL-AlphaTest.html</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>"Multisampling Anti-Aliasing: A Closeup View". Alt.3dcenter.org. Retrieved 2012-07-31. <a href="http://alt.3dcenter.org/artikel/multisampling_anti-aliasing/index7_e.php" target="_blank">http://alt.3dcenter.org/artikel/multisampling_anti-aliasing/index7_e.php</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>"Visual comparison of the various Anti-Aliasing modes". Nhancer.com. Archived from the original on 2013-01-28. <a href="https://web.archive.org/web/20130128122928/http://www.nhancer.com/?dat=d_AA" target="_blank">https://web.archive.org/web/20130128122928/http://www.nhancer.com/?dat=d_AA</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>Matt Pettineo (2012-10-25). "A Quick Overview of MSAA". Retrieved 2016-11-24. <a href="https://mynameismjp.wordpress.com/2012/10/24/msaa-overview" target="_blank">https://mynameismjp.wordpress.com/2012/10/24/msaa-overview</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>"Multisampling Anti-Aliasing: A Closeup View". Alt.3dcenter.org. Retrieved 2012-07-31. <a href="http://alt.3dcenter.org/artikel/multisampling_anti-aliasing/index8_e.php" target="_blank">http://alt.3dcenter.org/artikel/multisampling_anti-aliasing/index8_e.php</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> </ol>