Lines Matching refs:sRGB
83 The sRGB color space is based on typical (non-linear) monitor
86 as IEC 61966-2-1. The sRGB color space roughly corresponds to 2.2
89 This extension adds a framebuffer capability for sRGB framebuffer
90 update and blending. When blending is disabled but the new sRGB
93 green, and blue generated by fragment coloring are encoded for sRGB
95 along with the new sRGB update mode, red, green, and blue framebuffer
96 color components are treated as sRGB values that are converted to
99 for sRGB just prior to being written into the framebuffer.
103 configured to assume framebuffer color values are sRGB encoded.
145 it is moved to the new "sRGB Conversion" section:
153 because this behavior is moved to the new "sRGB Conversion" section.
186 to floating-point) are considered to be encoded for the sRGB color
204 ADD new section 4.1.X "sRGB Conversion" after section 4.1.8 (Blending)
207 (Blending) to now be "sRGB Conversion" (instead of "Dithering").
213 sRGB color space by some approximation of the following:
221 (effectively converted into an sRGB color space).
269 encouraged to allow sRGB update and blending when rendering to sRGB
272 whether or not sRGB update and blending is supported.
279 capable, sRGB update and blending only apply to the color buffers
280 that are actually sRGB-capable.
301 FRAMEBUFFER_SRGB B IsEnabled False sRGB update and 4.1.X color-buffer/enable
315 the framebuffer domain and "sRGB" indicates the extension is
316 adding a set of sRGB formats. This mimics the naming of the
317 EXT_texture_sRGB extension that adds sRGB texture formats.
319 The mixed-case spelling of sRGB is the established usage so
326 2) Should alpha be sRGB encoded?
334 3) Should the ability to support sRGB framebuffer update and blending
338 (mostly likely just RGB8 and RGBA8) that says sRGB blending can
342 and RGBA8 pixel formats as supporting sRGB blending and then
343 just provide the functionality for sRGB update and blending for
346 sRGB support for floating-point formats makes little sense
352 Requiring sRGB support for all fixed-point buffers means that
354 components would require special sRGB conversion hardware.
355 Typically sRGB is well-suited for 8-bit fixed-point components
358 Implementations could support sRGB conversion for any color
360 (honestly nor are implementations like to support sRGB on anything
363 4) Should there be an enable for sRGB update and blending?
367 of sRGB update and blending. Otherwise, the enable is silently
371 5) How is sRGB blending done?
374 on values in linear spaces. sRGB-encoded values are in a
375 non-linear space so sRGB blending should convert sRGB-encoded
377 sRGB-encode the result to store it in the framebuffer.
380 from sRGB to a linear value. Blending is then performed.
383 is converted to an sRGB encoding and stored in the framebuffer.
390 color) is converted to an sRGB encoding and stored in the
395 RESOLVED: Render targets that are not sRGB-capable ignore the
396 state of the GL_FRAMEBUFFER_SRGB enable for sRGB update and
398 sRGB-capable query may be performed on a per-color-attachment
401 8) Should sRGB framebuffer support affect the pixel path?
405 sRGB conversion only applies to color reads for blending and
407 or glAccum have no sRGB conversion applied.
410 or color tables to perform an sRGB-to-linear conversion with
414 support sRGB blending?
417 a format and set the sRGB attribute for the format too.
421 10) Should all component sizes be supported for sRGB components or
425 the implementation decides what pixel formats such support sRGB
428 It likely implementations will only provide sRGB-capable
433 sRGB and linear RGB color spaces?
436 linear RGB to sRGB conversion (see section 4.9.X above).
438 The sRGB to linear RGB conversion is documented in the
441 For completeness, the accepted linear RGB to sRGB conversion
445 Given a linear RGB component, cl, convert it to an sRGB component,
464 sRGB components are typically stored as unsigned 8-bit
471 12) Does this extension guarantee images rendered with sRGB textures
472 will "look good" when output to a device supporting an sRGB
478 faithfully reproduces the sRGB color space is beyond the scope
486 if the color texture image is capable of sRGB rendering.
489 other than sRGB internal formats such as those introduced by
491 to support sRGB update and blending of sRGB textures.
493 14) How is the constant blend color handled for sRGB framebuffers?
500 15) How does glCopyTex[Sub]Image work with sRGB? Suppose we're
503 to sRGB during the copy?
506 converted to the sRGB encoding during the copy. If such a
509 linear-to-sRGB encoding translation.
512 sRGB-to-linear and linear-to-sRGB conversions it uses?
522 if the color samples for multisampling are sRGB encoded, the
524 and then recoverted to sRGB if the output device expects sRGB
533 sRGB-correct multisample resolve. Whether this occurs or not
537 18) Why is the sRGB framebuffer GL_FRAMEBUFFER_SRGB enable
541 sRGB-versus-non-sRGB pixel format configuration mode that
542 determined whether or not sRGB framebuffer update and blending
544 pixel formation configurations because sRGB and non-sRGB versions
546 applicaitons unaware of sRGB might unknowingly select an sRGB
549 It seems more appropriate to have a capability for sRGB
552 to be marked as sRGB capable (so no additional configurations
553 need be enumerated). Applications that desire sRGB rendering
554 should identify an sRGB-capable framebuffer configuration and
555 then enable sRGB rendering.
557 This is different from how EXT_texture_sRGB handles sRGB support
559 are either sRGB or non-sRGB and there is no texture parameter
561 EXT_texture_sRGB because it allows implementations to fake sRGB
563 sRGB-encoded texels to sufficiently precise linear RGB values.
567 upon an sRGB-capable pixel format. sRGB textures require
571 19) How does sRGB and this extension interact with digital video
579 sRGB color space just like analog monitors.
601 are sRGB-capable in the fairly obvious way, but this language
611 sRGB-capable queries, rather then the