Re: Lut format chart
Jeremy Selan <jeremy...@...>
Exactly. Clients apps will automatically have support for all luttoggle quoted messageShow quoted text
formats. (It's about time!)
To an end user, this should feel pretty automated. Apps shouldn't
need ebd user options / dialogs, all of the lut-location mojo is
internal to the ColorConfiguration file.
Specifying which configuration to use is controlled via a single
environment variable (which points at an ocs file). (Explicit
initialization is also allowed, but this will probably be less
The internals of the .ocs file are still in flux, but the rough idea
is that there will be two flavors. One flavor will be a human-
readable xml file, of which one element lut dir. The alternative will
be a binary ocs 'package', where the lut dir is self contained in the
file. (Think tgz of a config / lut dir).
In the super common newbie-case, downloading a single .ocs binary
file, and pointing to it with OCS_CONFIG will be all that's needed.
On May 25, 3:09 pm, Larry Gritz <l....@imageworks.com> wrote:
Neat. So just to clarify, the big idea is that any app that uses your color library properly will, by extension, understand ALL of these luts (whichever happens to be available/used at the facility using the app)?