You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are working on adding support for color spaces beyond sRGB, but for the best support of these spaces, we'd like to use 10- or 12-bit fixed point video card output whenever possible. This is important to prevent banding and other color degradation when using another color space beyond sRGB.
I believe the intermediate framebuffers for shader passes currently support 32-bit float framebuffers, so this is not an issue. The only concern is if the final framebuffer for display can support 10-bit or 12-bit fixed point already or is fixed to 8-bit.
If it's the latter, please keep this open and if possible perhaps point me to where I can find the current framebuffer code to see feasibility of updating for 10- or 12-bit support.
The text was updated successfully, but these errors were encountered:
RetroArch supports HDR shaders, so I believe the final framebuffer supports at least 10-bit. You can take a look into the hdr folder on this repository.
These are only supported on Windows for now. But now that Linux also supports HDR, I'm hopeful they'll add support for them on the Linux version of RetroArch.
I'm the lead developer of the Scanline Classic shader.
We are working on adding support for color spaces beyond sRGB, but for the best support of these spaces, we'd like to use 10- or 12-bit fixed point video card output whenever possible. This is important to prevent banding and other color degradation when using another color space beyond sRGB.
I believe the intermediate framebuffers for shader passes currently support 32-bit float framebuffers, so this is not an issue. The only concern is if the final framebuffer for display can support 10-bit or 12-bit fixed point already or is fixed to 8-bit.
If it's the latter, please keep this open and if possible perhaps point me to where I can find the current framebuffer code to see feasibility of updating for 10- or 12-bit support.
The text was updated successfully, but these errors were encountered: