Re: Previous comments (for posterity sake)
Jeremy Selan <jeremy...@...>
... from an anonymous commenter, some excellent questions. (I'll be
adding these to the FAQ). This system is complementary to Truelight / Cinespace. AlthoughOne question I think would be good for the faq: how does this system Truelight comes with a bunch of plugins, its core functionality is to generate the 3D luts for things like print emulation, device mapping, etc, and I don't see this role changing. (Our library does not attempt to fill these roles). It will be very straightforward to implement a reader for unencrypted truelight luts. Note that supporting Truelight *encrypted* luts is probably not simple due to legal considerations. I am unsure if Cinespace has the capability to export un-encrypted LUTs. Sorry for being confusing. ALL of the Cg / GLSL generation stuffAlso, I didn't totally get this line in the faq: "GPU Acceleration is we've developed at SPI (related to color processing) is being included in this release. This entry was intended to clarify issues relating to integration; that even though this library generates cg / glsl code, we don't link to Cg/ GL directly. Instead, the library returns "simple" data types, a std::string with the shader text, and a float* with the lookup table. It is left to the client app to make the appropriate GL calls accordingly. (which in our experience is not much of a burden, and actually makes everyones lives simpler). A bit of extra information (such as cacheIDs for the 3d luts) are also included to allow for additional client-side optimizations. (In the 3dlut cacheid case, to prevent reloading the 3d texture every time something changes). On Apr 21, 6:07 pm, Jeremy Selan <jeremy...@...> wrote: I'll be posting (anonymously) the previous comments on ver 0.1 so that
|
|