toggle quoted messageShow quoted text
as far as I know, no.
'allocation' too cannot be deduced.
The only solution i can think of is having a file attached to the LUT specifying these parameters.
On 11/07/2013 02:55 AM, robin...@... wrote:
I'm new to OCIO and this forum, and I have what I think is probably a pretty common issue, although after searching for a solution for a couple days, I haven't come up with anything.
My problem is that I am receiving pre-generated LUTs from vendors, mostly in the form of .cube and .spi1d files, and I would like to integrate them into our custom config.ocio.
Is there an established way to extract the required information from these files so I can populate the colorspace definitions in my config?
Most of the fields can be determined, but bitdepth and interpolation are often not defined. Is there a way to figure this out from the information in the LUT?
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@....
For more options, visit https://groups.google.com/groups/opt_out.