![]() $ ocioperf -displayview ACEScg sRGB ‘Show LUT’ -iter 20 -image test.exr Offers an arguably “artist-friendly”, WYSIWYG workflow for creating LUTs Lookup data where standard LUT formats are less feasible. Image containers are occasionally used for encoding and exchanging simple color The ociolutimage tool converts a 3D LUT to or from an image. Also, it does not leverage any of the new OCIO v2 features. NOTE: This program is not a very good example of how to build a UI.įor example, it assumes each display has the same views, which is often May be useful to users to quickly check a color space configuration. Typical viewer controls (scene-linear exposure control and a Uses OpenImageIO or OpenEXR to load images, and displays them using OCIO and ![]() ociodisplay ¶Īn example image viewer demonstrating the OCIO C++ API. Use the –help argument for more information on to the available options. Supported formats will vary depending on the use of OpenImageIO. Uses OpenImageIO or OpenEXR for opening and saving files and modifying May be used to output the shader program used by the GPU renderer. Output color space or a (display,view) pair.īoth CPU (default) and GPU renderers are supported. OCIO transforms can be from an input color space to either an The ocioconvert tool applies either an aribtrary LUT, or a complex OpenColorIO Loads an image, applies a color transform, and saves it to a new file. The ociobakelut command supports many arguments, use the –help argument for Support baking, and see the Baking LUT’s for more information See the Supported LUT Formats section for a list of formats that $ ociobakelut -inputspace lg10 -outputspace srgb8 -format flame flame_lg10_to_srgb.3dl The colorspace used for compositing_log is not incorrect: This is a command-line tool which shows an overview of an OCIO configįor example, the following shows the output of a config with a typo. Ociodisplay: (OpenEXR or OpenImageIO), OpenGL, GLEW, GLUT Note that some tools depend on OpenEXR or OpenImageIO and other libraries: Point to the config file you want to use. Many of the tools require you to first set the OCIO environment variable to Tools use the -v argument for more verbose output. The –help argument may be provided for info about the arguments and most The following command-line tools are provided with OpenColorIO. Implement support for categories (the easiest way is to use the code inĪpphelpers/ColorSpaceHelpers.h). Note that this requires the application developer to Specify the color space categories that the application should show inĬolor space menus. ![]() ![]() The complete list of flags is in OpenColorTypes.h. Overrides the optimization settings being used by an application, for ![]() Logging output is sent to STDERR output by default. Numeric values 0, 1, 2, or 3 can be used) None, warning, info, or debug (or their respective Overrides the inactive_colorspaces list from the config file.Ĭolon-separated list of color spaces, e.g previousColorSpace:tempSpace OCIO_LOGGING_LEVEL ¶Ĭonfigures OCIO’s internal logging level. Overrides the active_views list from the config file and reorders them.Ĭolon-separated list of view names, e.g internal:client:DI OCIO_INACTIVE_COLORSPACES ¶ Overrides the active_displays list from the config file and reorders them.Ĭolon-separated list of displays, e.g sRGB:P3 OCIO_ACTIVE_VIEWS ¶ Provide a way of setting this from the user interface.) OCIO_ACTIVE_DISPLAYS ¶ Necessary for some of the command-line tools but most applications Specifies the file path of the config file to be used. The following environment variables may be used with OpenColorIO: OCIO ¶ ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |