-
-
Notifications
You must be signed in to change notification settings - Fork 268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linear color space (16bit, from 0.0... to 1.0...) #819
Comments
And saving in 16bit format (e.g PNG supports 16bit). |
Currently, no. While we do store images as float32 numbers, numerous operations convert to uint8. So we could add support for saving an image as 16bit, but it wouldn't achieve much. However, I think that we should support this. Last time I brought this up, I believe that the consensus was that it's a niche use case that isn't a priority. I also want to point out that many upscaling architectures use uint8 in their APIs, so there is nothing we can do about that. |
@RunDevelopment okay. |
Also there is another case of "LDR to HDR" models. |
Do you know which ones support floating point? |
All the ones we support in PyTorch use floating point I think. But yeah, many of the nodes in chaiNNer force us to convert to uint8 (thanks to opencv), so this isn't realistic unless we replace those with different functions. Also, saving at different bit depths will theoretically be possible once we add encoding settings to the image save node. |
Is it possible to process in a 16bit linear color space?
The text was updated successfully, but these errors were encountered: