Image Tool ("it") is a robust framebuffer/render view window, offering complete floating point support and a powerful and flexible catalog, as well as a fast and powerful imaging tool that is capable of production-qualilty image manipulation and compositing usually found only in high-end standalone products.
The "it" window can be customized by selecting options in the first two sections on the "Window" menu These optional windows and toolbars can be shown or hidden from the menu, or toggled on or off with their associated hot key as displayed in the menu. They can also be docked into the main window or left as floating windows. Double-clicking on the title bar of one of these sub-windows will toggle it from docked to undocked. Toolbars, such as the "Pixel Readout" toolbar, don't have a title area since they are so small and instead have a grab handle at the end or top that is used to place them. The grab handle can also be double-clicked to toggle the docking.
The remap menu shows the color space that your image is in. Typically this would be linear for rendered images and sRGB for 8 bit image files. By default "it" chooses the image space of the image and when it does this the image space is preceded by a *. You can use the menu to override "it"'s choice (the * indicator will go away)
"it" supports view mapping output images to accommodate your workflow of choice using the OpenColorIO system (http://opencolorio.org). Your view mapping defaults can be set for images rendered to "it" as your framebuffer (regardless of bit depth) or for imported images (with different mapping for different types, if necessary).
There are several important things to remember about remapping:
Remapping is applied only for viewing files. It is not burned in. There is a prefence for controlling whether the mapping is applied when images are saved. This option is controlled on a per-Catalog basis so it is important to note that when changing this preference it will only affect new Catalogs. Each Catalog can also be individually set to burn in on save or not.
Images rendered via RenderMan are, by default, in linear space, unless an exposure is applied to the output (which can be done in RfM via the Output Settings tab of the RenderMan controls).
If you do apply an exposure to your output, be sure to make the proper adjustment to the default image mapping for rendered images.
The OpenColorIO setup can be changed via your it.ini, though, as always, we strongly recommend making the changes in a site-specific surrogate ini file, referenced via RMS_SCRIPT_PATHS. "it" will also use the environment variable OCIO if it is set to find the OpenColorIO config file.
A special entry on the remap menu is the Shadow Map option, which is useful for viewing shadow map files. These files can have huge ranges that are well beyond zero to one, so the traditional way to display these has been to rescale the min and max values to zero and about 0.9, and then invert them with (1 - val).
If you have used sho to view shadow maps, this is what you have been looking at. The actual script that performs this operation is:
element = it.GetCurrentElement() image = element.GetImage() offset = ice.Card([1.0/16.0]) minusone = ice.Card([-1.0]) (min,max) = ice.GetMinMax(image, returnCards=True) result = minusone.Multiply(image.Subtract(max).Divide(max.Subtract(min))).Add(offset)
Sequences are for when you've rendered a shot or perhaps a wedge of parameters to a shader and now you would like to see them all played as a sequence. The Sequence toobar has the controls for starting and stopping playback and the frame range controls. "it" will either play the whole catelog or you can open a set of images on disks as one element (called a "sequence"). There is also a "scrub" mouse tool which when activated lets you move through a sequence by dragging with the left mouse button in a horizontal direction.
An image sequence can be created by opening multiple files on disk in a directory, use File->Open Sequence instead of File->Open Image. "it" will discern which files belong to the sequence; and the frame range will appear in the Sequence toolbar.
Sequences are low tech in that they don't provide a way to save or load movies, and the entire "movie" is held in RAM. "it" places a cap on the number of images it will hold in RAM so for smooth playback you will need to set that cap (Image Cache Size) to at least the number of frames in your sequence.