Cache EXR to DWAB

I agree, it will be great if flame could use the color space tagging mechanism to know the compression mode.

F

yea also with arnold and vray etc you can have different compression per layer in a EXR…

different bitdepth as well.

I would really hope that flame uses EXR to its full potential, the amount of metadata you can throw in there and use somewhere else is insane, so unrealized potential, you can put 3D transform / camera data in there and all kinds of other shenanigans, its great, its free , its opensource and used everywhere.

Perhaps a feature request for an additional cache option for 32bit?

Splitting the float config into full and half and different formats per bit depth. Seems like this would cover most use cases or?

2 Likes

so simple yet so genius.

Would cover pretty much all usecase apart from one:

32bit float dwab is a pretty OK format for log encoded data as well :joy::joy::face_with_peeking_eye::face_with_peeking_eye:

1 Like

I have quite a robust set of input rules for my colour management. Although I would like it expanded beyond just GLOB (the naming of the file) to perhaps allow me to scan folder names as well.

FI-03192

Although I haven’t looked at Flame 2025 yet I am very excited by the lens distortion. I noticed that data and display window still needs to be manually set during import.

I could imagine us setting up rules that would ensure the compression was PIZ and data window was used for all passes marked UV.

I already have colourspace tagging these as data/uv.