ACESCG and SRGB Questions - Texture Asset Creation

[ChrisBrejon (Christophe Brejon)]

@Thomas_Mansencal

Mmmh this doesn’t really make much sense because upon being decompressed an 8-bit jpeg will consume the same memory than any other 8-bit image container. A renderer might support direct access on the compressed data but it is certainly not the norm AFAIK, and given the type of random access required, it seems far fetched to even implement. Where you can get some net gain is on IO because the smaller file size means it is sometimes faster to read it from network storage. A notable exception to what I just said is GPU texture compression, the algorithms, in that case, are specifically optimised for random texel access, unlike jpeg.

Thanks for your insight. I did not do these tests myself at our studio but from what I have been told, the exr texture workflow was less heavy than our previous texture workflow based on png/tga/tiff. The exr files’ size are smaller in our tests (which surprised me). Hence my deduction about memory usage. Unfortunately, I do not have access or could share to the data test.
Chris