6 ImageServer utility programs

This chapter describes some modules of our software that are only accessible when working on a command line. It is meant for those who want to change or check specific OPI settings manually or to set up automated workflows, e.g. with Script Server (see 7 “HELIOS Script Server”).

ImageServer programs

ImageServer is composed of many individual programs e.g. “opisrv”, “opitouch”, “layout”, “oiimginfo”, and “hirespath”. In addition, it also makes use of the modules “papsrv” (see EtherShare manual), “psresolve” and different printer interface programs (“tcpif”, “smbif” and others). Some of the above mentioned programs are described in the following chapters.

The HELIOS utility programs described in this chapter are located in the “HELIOSDIR/bin” directory.

You may use them for setting specific parameters manually. This may be useful because some of these parameters were especially designed to max out application specific features.

For programs that are not described in this manual and for instructions on how to integrate plug-ins, please refer to the “HELIOS OpenImage Software Developer Kit”. This documentation can be found on the HELIOS website, section Support > Developer Specifications, and is meant for third-party developers only.

About defaults

Please note that parameters you set, using e.g. the “layout” program, override the settings in the preference data base. If you do not specify a specific parameter, ImageServer will check the entry in the preference database. In case the preference data base does not contain an entry for this parameter, the default will be used. For changing entries in the preference data base, see 4.1 “ImageServer settings” and 9 “Preferences and notification features”.

6.1 layout

The “layout” program has three purposes:

Layout file generation (6.1.3 “Layout file generation”)
Image conversion (6.1.7 “Image conversion”)
Tagging of ICC profiles, path information and XMP metadata (6.1.11 “Tagging ICC profiles, path information, and metadata to images”)

The files processed by “layout” differ in some respects; layout files that have been generated from high-resolution files include embedded OPI references to the original images, whereas converted image files do not. XMP and IPTC metadata are preserved by both generated layouts and converted images.

6.1.1 Syntax conventions

Irrespective of whether you call the “layout” program for a set of files or use it to poll permanently in the background, use the options described below. Type and default values are shown in angle brackets just before the description. The following types are used:

`uint32`	32-bit integer value (e.g. `72`)
`double`	Floating point value (e.g. `72.6`)
`string`	Any string enclosed in quotation marks (e.g. `"RGB"`)
`string list`	Comma-separated strings (e.g. `"RGB","CMYK"` – no spaces!)
`boolean`	`TRUE` or `FALSE`

6.1.2 General “layout” options

These options can be used for either layout file generation, or image conversion.

Note:: Options that can also be specified in one of the HELIOS Admin dialogs are described with the note “Compare HELIOS Admin!”.

-h

Display help file.

-v

Display progress on “stdout”.

-H

Ignore all user home directories as HELIOS volumes.

-o PreserveResources <string list:IPTC,PATH,XMP>

Determines additional resources, which will be preserved by “OpenImage” plug-ins. If the string contains PATH, IPTC or XMP, the named additional resource will be preserved. If no resources should be preserved, specify none.

-o OmitProfile <boolean:FALSE>

Specifies whether to tag a profile to the resulting output file. This option is useful if the generated layout/original is small while the specified profile was large.

-o DcsSuffixes <string list:"C","M","Y","K">

Suffixes of DCS plates that need to be processed.

-o DcsCodings <string list:"MacRoman",”PC850”>

The generation of EPS files requires an internal character encoding. This option allows specifying the desired encoding.

-o ProfileRepository <string:"ICC-Profiles">

This preference specifies the volume name containing the ICC profiles. You may also specify the absolute path to the repository or the path relative to the “HELIOSDIR” directory.

Compare HELIOS Admin!

-o ProfileSearchPaths <string list:None>

Additional directories to search for ICC profiles.

-o ProfilePaths <string list: (RGB="ICC-Profiles:Scanner:HELIOS:sRGB_IEC61966-2-1_noBPC.icc", CMYK="ICC-Profiles:Printer:ECI_Offset_2007:ISOcoated_v2_eci.icc")>

Defines RGB/CMYK profiles used if the color space for the output file and the color space of the high-resolution file are different. These profiles are used to match between color spaces properly. Each string has the format <color space>=<path>.

-o RenderingQuality <uint32:2>

Defines ICC rendering quality. You may choose one of the values listed below:

0 (normal quality)
1 (draft quality)
2 (best quality)

-o MissingIccProfileIsError <boolean:TRUE>

Defines missing profile as error when creating output file.

-o LogMissingIccProfile <boolean:TRUE>

Logs missing profile in “syslog” file.

-o UseProfile <boolean:TRUE>

Process color matching for output files, if the high-resolution files have tagged ICC profiles.

-o IncludeProfile <boolean:FALSE>

This option embedds the entire profile in the output file as a value (copy) instead of a reference (-o OmitProfile). Only applicable if UseProfile option is set.

-o ImageProfilePaths <string list:None>

If PDF input files are not yet tagged with ICC profiles, this parameter can be set for attaching a profile to RGB, CMYK or Grayscale objects within the document. Each string has the format <color space>=<Pathname> and defines the ICC profile path name for the given color space. This setting overrides the default profiles in the HELIOS Admin PDF HandShake Settings.

-o DcsCompatible <boolean:FALSE>

Lets the program generate DCS 1 or DCS 2 EPSF layout images if the raster-based high-resolution images include colors other than Black&White or Grayscale.

-o KeepDcs <boolean:TRUE>

Lets EPSF layout images of DCS 1 or DCS 2 high-resolution images keep the DCS structure. Changing the option to FALSE will lead to simple EPSF layout files.

-o Fast <boolean:FALSE>

If set to TRUE, the used image generation algorithm will be slightly less precise but faster, while consuming less resources. However, the rendering quality should be sufficient for smaller images.

-o PreserveDeviceN <boolean:FALSE>

This option optimizes the PostScript output of PDF original files to use PostScript 3/DeviceN features. It should only be set to TRUE if you print to a PostScript 3 device with in-RIP separation. This applies for Hexachrome printing, colorized images (Duotone), etc. When printing host-based separations with applications like QuarkXPress, this feature must be turned off, otherwise the output will lead to unexpected results.

-o PDFTransparency <boolean:TRUE>

If a PDF document that contains transparencies is processed with this option, PostScript with “pdfmark” constructs is generated.

-o PDFPageBox <str:”CropBox”>

Specifies the page box of PDF documents that should be used for output. PDF page objects always contain a MediaBox entry and may specify boxes within the MediaBox as CropBox, BleedBox, TrimBox and ArtBox. Valid values of this option are: "MediaBox", "CropBox", "BleedBox", "TrimBox", "ArtBox".

-o SpotToEps <boolean:TRUE>

Causes the creation of EPSF layout images if a high-resolution raster image contains extra colors like spot colors.

-o MaskToEps <boolean:TRUE>

Causes the creation of EPSF layout images if a high-resolution raster image contains a clipping path.

-o FilterInks <string:<None>

This option can be used to omit specific channels from the target image. The argument is a comma-separated list of each separation color (Inks) as displayed in “oiimginfo”. Thus, the first color has the index 0, the second 1, etc. All colors that are not listed are removed from the target image. For a CMYK image, to filter Cyan and Magenta only, this option must be set to 0,1.

-o KeepPhysicalSize <boolean:FALSE>

If set to TRUE, this option preserves the physical size of an image when the image size is changed via the resolution.

-o BitsPerComponent <uint32:0>

Enforces the color depth of the target image. Valid values are 8 and 16.

-o SpotToProcess <boolean:FALSE>

Forces output images to always contain only the default inks of the output image color space. Spot colors defined in a high-resolution image will be converted into the appropriate values of the output image color space.

-o ForceMatch <boolean:FALSE>

Forces ICC color matching while creating layout images or converting images, even if no color matching would be applied by the “layout” default behavior.

Note:: Do not apply this option when converting images to grayscale or when having grayscale layouts created.

-o Compression <boolean:FALSE>

Forces the output image to be compressed the same way the high-resolution file is compressed. This option will only be used if the high-resolution file and the output image have the same file format.

-o ColorAliases <string list:None>

Defines mappings from application or localization dependent color names to the names used in “OpenImage”. String format is <ColorName>=<ColornameAlias>.

-o Signature <string:None>

Defines a signature filter configuration file. See “HELIOS OpenImage Software Developer Kit” for details.

-o RssLimit <uint32:0>

Controls resource usage of main memory that is used from the “layout” application. The specified value limits the maximum use of main memory in kilobytes. Zero means no limits.

-o ConvertRenderingIntents

Allows setting an ICC rendering intent. This may be one of:

Perceptual (0)
Relative colorimetric (1)
Saturation (2)
Absolute colorimetric (3)
Perceptual with BPC (Black Point Compensation) (4)
Relative colorimetric with BPC (5)
Saturation with BPC (6)
Perceptual with Black Plane Compensation (7)
Relative Colorimetric with Black Plane Compensation (8)
Saturation with Black Plane Compensation (9)

The following matrix displays the default ICC rendering intents that are used if not otherwise specified:

               To: S R G H H C C M Y C C C C Y
From:   Spot       1 1 1 1 1 0 0 1 1 1 1 1 1 1
        RGB        1 1 1 1 1 0 0 1 1 1 1 1 1 1
        Grayscale  1 1 1 1 1 0 0 1 1 1 1 1 1 1
        HSV        1 1 1 1 1 0 0 1 1 1 1 1 1 1
        HLS        1 1 1 1 1 0 0 1 1 1 1 1 1 1
        CMY        1 1 1 1 1 1 1 1 1 1 1 1 1 1
        CMYK       1 1 1 1 1 1 1 1 1 1 1 1 1 1
        Multitone  1 1 1 1 1 0 0 1 1 1 1 1 1 1
        YCbCr      1 1 1 1 1 0 0 1 1 1 1 1 1 1
        CIELab     1 1 1 1 1 0 0 1 1 1 1 1 1 1
        CIEXYZ     1 1 1 1 1 0 0 1 1 1 1 1 1 1
        CIELuv     1 1 1 1 1 0 0 1 1 1 1 1 1 1
        CIEYxy     1 1 1 1 1 0 0 1 1 1 1 1 1 1
        YCC        1 1 1 1 1 0 0 1 1 1 1 1 1 1

Example:

-o ConvertRenderingIntents="RGB:CMYK:2,CMYK:CMYK:0"

Converts RGB to CMYK with the intent “Saturation”, and also CMYK to CMYK with the intent “Perceptual”.

-o RenderColor <string:CMYK>

Sets the color space for rendered image objects. It is important that for PDF files this option is set to CMYK, to show proper overprints.

6.1.3 Layout file generation

Usually, layout files will be generated automatically by ImageServer, and new layouting parameters can be set using the HELIOS Admin program on any client. If you want to create a layout manually or if you want to use a special set of parameters for the creation, you may call the “layout” program directly. This procedure may optionally be automated by means of Script Server.

There are two main possibilities of calling the “layout” program. If you want to create layout files for a single file or a set of known files, you can use the following call:

layout [options] files... or
layout [options] -L dir file(s)

If you want the “layout” program to scan permanently for high-resolution files in a special directory, use the call:

layout [options] -p polltime directory or
layout [options] -p polltime -L dir <polled directory>

Now, the layout process will go into the background and scan the given directory constantly with the given interval polltime in seconds for a new or changed high-resolution file to create a layout file from. This feature should only be used for small directories because it is not as fast and efficient as automatic layout generation.

Instead, we recommend to use Script Server, which is described in 7 “HELIOS Script Server”.

6.1.4 Options for the layout file generation

Note:: Options that can also be specified in one of the HELIOS Admin dialogs are described with the note “Compare HELIOS Admin!”.

-E

Return the path to the generated layout.

-G

Send notify event for generated file.

-p <int: (see text)>

Check the directory regularly for new image files (“polling”). The default is 0 = never.

-L dir <string:None>

Set destination directory for layout file generation. It is sufficient to state the relative path for manual (NOT for automatic “polling”!) mode. This option creates all layouts in a “layouts” subdirectory of the indicated directory. This option is mostly needed when the high-resolution files reside on a read-only medium e.g. a CD-ROM.

Note:: If the source directory is located in a HELIOS volume, but the destination directory is not, first copy the high-res original into the destination directory using the “dt” tools (see the Base manual). Then perform a regular “layout” call without specifying -L.

-o MinLayoutSize <uint32:0>

Defines minimum size in bytes needed to start layout process (0 = any size).

-o KeepImageResolution <boolean:FALSE>

Do not consider PrintResolution (see below); the layout file will inherit the resolution of the high-resolution image.

-o PrintResolution <double:72.0>

Defines the resolution used for the printable part of the layout (0 = omit printable part).

Compare HELIOS Admin!

-o ScreenResolution <double:72.0>

Defines the resolution used for the screen preview part of the layout (0 = omit screen preview).

Compare HELIOS Admin!

-o PrintColor <string:"CMYK">

Defines the color space used for printable part of layout file. If the string is set to None, the color space of the high-resolution file is used. For valid color spaces, see Table 6.1 below. Please note that some color spaces cannot be applied to certain file formats.

Compare HELIOS Admin!

Note:: This option is ignored for Bilevel and Grayscale images if the target format is specified as EPS.

-o ScreenColor <string:"RGB">

Defines the color space used for the screen preview part of the layout file. If the string is set to None, the color space of the high-resolution file is used. For valid color spaces, see Table 6.1 below. Note that some color spaces cannot be applied to certain file formats.

Name of color space
None	HSV	YCbCr
Spot	HLS	CIELab
Bilevel	CMY	CIEXYZ
Grayscale	CMYK	CIELuv
Indexed	Multi	CIEYxy
RGB	Duotone	YCC

Table 6.1: List of layout color spaces

-o CompressPrint <string:None>

Defines the compression mode used to generate the printable part of the layout file using a string from Table 6.2. Please note that some compression modes cannot be applied to certain file formats.

Compare HELIOS Admin! (HELIOS Admin provides less options.)

-o CompressScreen <string:None>

Defines the compression mode used to generate the screen preview of the layout file using a string from Table 6.2. Note that some compression modes cannot be applied to certain file formats.

Name of compression mode
None	JPEG	Berthold Lineart
Compress	JPEG 2000	Pixar
CCITTRLE	PackBits	Flate
CCITTG3	NextRLE	RLE
CCITTG4	Thunder

Table 6.2: List of layout compression modes

-o CompressQuality

Defines the compression quality of layout files or image components:

For JPEG:
-o CompressQuality <uint32:75>
Creates poor…high quality JPEG image (1…100).

For JPEG 2000:
-o CompressQuality <uint32:0>
Specifies the image quality of a JPEG 2000 image in relation to the uncompressed high-resolution original. The values range from 1…100. Specifying “0” means lossless.

Note:: CompressQuality specifies the percentage size of the JPEG 2000 image data compared to the size of the uncompressed image, which the JPEG 2000 should not exceed. For example, if an image with lossless compression has only 50% the size of an uncompressed image, a CompressQuality value between 50% and 100% produces no visible differences.

-o LayoutHighQuality <boolean:TRUE>

Create the best layout quality possible. Otherwise (FALSE), the smallest version of the image that matches the defined layout resolution is used. The high quality setting uses a bilinear resolution converter, low quality setting uses the “nearest neighbor” algorithm.

-o LayoutCreator <string:"8BIM">

Defines Mac file creator used for layout creation (The default value "8BIM" defines Adobe Photoshop).

-o LayoutEpsCreator <string:None>

Some application programs, e.g. Adobe InDesign, parse Photoshop resources only if they find a suitable creator in the file header. This option allows specifying a creator for creating OPI layouts.

-o LayoutAlpha <boolean:FALSE>

Most layout programs do not support OPI for transparent images, so transparency channels are stripped from layout images by default. If Alpha support is active (UseAlpha = TRUE) and LayoutAlpha=TRUE, layout images will not be stripped of transparency channels. Using this option can make sense in a PDF-native OPI workflow.

-o ForceRasterLayout <boolean:FALSE>

By specifying this option, all layout images will be created in raster format (provided that ForceEpsLayout is not specified!). However, the original image should contain a raster image.

-o ForceEpsLayout <boolean:FALSE>

By specifying this option all layout images will be created in EPSF format (provided that ForceRasterLayout is not specified!).

-o PDFNativeWorkflow <boolean:FALSE>

This preference enforces the generation of PDF-native workflow compatible layout images from vector-based EPS images, even if TIFF layout images are supposed to be generated (e.g. via the “%t” folder syntax).

Note:: This option must be set to FALSE if RasterImageType and RasterImageExt are used. Otherwise no raster layout can be enforced.

-o SingleEpsPath <boolean:TRUE>

For most images, ImageServer supports handing over different paths. However, most application programs cannot cope with different paths when it comes to EPS images. So only the clipping path is currently evaluated by default, which is controlled by this option.

-o UseAlpha <boolean:TRUE>

If set to FALSE, ImageServer ignores alpha channels in image files.

-o RasterImageType <string:"TIFF">

If the high-resolution file uses raster format and does not include any mask, the resulting layout file will inherit the raster format. The used layout file format can be overridden using this option. You may use any string defined for the file type (e.g. “JPEG”). See valid file types in Table 3.3 in 3 “Before getting started”.

-o RasterImageExt <string:None>

Specifies the file type by means of the file’s subformat when generating layouts from raster-based images.

-o EpsImageType <string:"EPSF">

Defines the file type which is used to select the manager which creates layout files. You may use any string defined for the file type. See valid file types in Table 3.3 in 3 “Before getting started”.

-o EpsImageExt <string:None>

Specifies the file type by means of the file’s subformat when generating layouts from EPSF images.

Please note that the following four options can only be used if the created layout file is an EPSF file.

-o EpsKeepSize <double:10.0>

Defines the allowed difference in size between the layout file and the high-resolution file (in percent). 20.0, e.g., specifies that the layout file must be smaller than 120% of the high-resolution file or else only a copy of the high-resolution file will be used as layout file. You may also specify negative values here. Valid values range from -99 to any positive value. Applies only to EPSF layout files.

-o EpsPrintablePreview <boolean:TRUE>

If set to FALSE, “layout” creates a screen preview of the image but no printable layout. Applies only to EPSF layout files.

-o EPSPreviewPSLevel<int:1>

Determines the preview PostScript level for EPSF files. By default, this is PostScript level 1, optionally PostScript level 2 can be specified. Applies only to EPSF layout files.

-o EpsBinaryEncoding <boolean:TRUE>

Defines that image data is stored using 8-bit values (otherwise 7-bit hex is used). Applies only to EPSF layout files.

-o PreviewFromPict <boolean:TRUE>

Mac PICT may be used as source for layout generation.

-o OmitScreenPreviewTypes <string list:"TIFF","JPEG","PNGf","BMP ","PDF ">

By default, all provided managers create a screen preview in addition to the print preview. Thus, TIFF layouts may contain an additional PICT element. With this option you can define a list of layout file types for which the screen preview should not be included in the layout file, e.g.: "TIFF","JPEG"

-o MaxScreenSize <int:800>

Defines the maximum allowed image size in pixels for screen previews.

-o MaxThumbnailSize <int:200>

Defines the maximum allowed image size in pixels for thumbnails.

-o FailureInfoLayouts <boolean:TRUE>

Defines whether a standard default layout (indicating the error) should be created in case of layout generation failure.

-o CrossPlatformLayout <boolean:FALSE> (see also -P -M options below)

Defines whether created layouts are usable on all supported platforms (e.g. all relevant data is stored in the data fork). If the high-resolution file has a resource, the layout file contains a resource when stored in a HELIOS volume. This option can be used to specify the preview image format of the generated layout file; in a cross-platform layout the preview is TIFF, otherwise a Mac PICT preview is used.

-o CrossplatformFiles <boolean:FALSE>

Defines whether a resource fork is created (see also the CrossPlatformLayout option above).

-o Thumbnail <boolean:TRUE>

Include Mac icon in layout file (not applicable to cross-platform files).

-o LayoutComment <string:"HELIOS ImageServer 5.0.0 layout of %T file \"%f\", size %k kBytes, created by %C">

Overrides the default comment field for layout images. The option is a string which is placed in the comment section of a Mac file and can be viewed in the Finder using the Get Info dialog box. This string may include the following symbols (the comment may contain up to 199 bytes):

`%f`	File name of the original image
`%b`	Size (bytes) of the original image
`%k`	Size (kilobytes) of the original image
`%m`	Size (megabytes) of the original image
`%t`	File type of the original image printed as 4 byte signature
`%c`	File creator of the original image printed as 4 byte signature
`%T`	File type of the original image printed as clear text
	if possible (otherwise printed as with %t)
`%C`	File creator of the original image printed as application
	name if possible (otherwise printed as with %c)

-o LayoutLabel <uint32:0>

Sets the label color of a layout file. An integer number between 1 and 8 reflects the Mac Finder label colors, 0 turns this option off.

-o FailureComment <string:"Failed HELIOS ImageServer 5.0.0 layout file of \"%f\"">

Defines the comment string for a failed layout image (see also LayoutComment).

-o FailureLabel <uint32:0>

Specifies the label color of a failed layout image (see also LayoutLabel).

-o IgnoreMasks <boolean:FALSE>

If TRUE, this option causes an existing clipping path to be ignored when creating a layout image. See “Image paths and clipping paths” and 5.2 “Define folder specific OPI settings” for a description.

-o IgnoreSpots <boolean:FALSE>

If TRUE, this option specifies that additional channels (e.g. spot colors) are ignored when creating a layout image, printing the resolved high-resolution image or converting an image. See 3.3.4 “Additional channels in bitmap images” and 5.2 “Define folder specific OPI settings” for a description.

-o upscale <boolean:FALSE>

Allows upward scaling so that the layout image may have a resolution higher than the resolution of the original image.

-o ProtectLayouts <boolean:FALSE>

With this option set to TRUE generated layout files will have the Mac Finder flag Locked turned on. Before setting this flag to TRUE make sure that the DTP application you use can handle locked layout files!

The following options are only supported for backward compatibility with previous ImageServer versions; please do not use these options for new installations or configurations!

-r dpi <double:72.0>: Set resolution (in dpi) used for creating layout files. Use PrintResolution and ScreenResolution instead.
-M <boolean:TRUE> (opposite to -P): Produce layout files for the Mac platform only. Use CrossPlatformLayout instead.
-P <boolean:FALSE> (opposite to -M): Generate cross-platform layouts. Use CrossPlatformLayout instead.
-n <boolean:TRUE> (opposite to -N): Limit the size of EPSF layout files on generation. Use EpsKeepSize instead.
-N <boolean:FALSE> (opposite to -n): Do not limit the size of EPSF layout files on generation. Use EpsKeepSize instead.
-c <boolean:FALSE>: Compress screen previews. Use CompressScreen instead.
-d dcsSuffixes <string:"CMYK">: Defines valid DCS suffixes. You may specify any number of characters. These characters are handled case-insensitive. Use DcsSuffixes instead.
-C [rgb|cmyk] <string:"CMYK">: Defines the color space used for raster-based layouts (e.g. TIFF layouts). Use PrintColor instead.
-e [rgb|cmyk|bw] <string:"CMYK">: Defines the color space used for EPSF printable previews. Use PrintColor instead.
-t [rgb|cmyk|bw] <string:"CMYK">: Defines the color space used for EPSF screen previews. Use ScreenColor instead.
-a attributes: Allows you to specify a comma-separated list of attributes. Use -o Attributes instead.

6.1.5 Attributes for “layout” options

Attributes are only applicable to specific file types. They are entered as command line options using the syntax:

layout -o Attributes=<attributes>=<value>

Additional attributes are delimited by commas.

Attributes <string list:"key=value">: Consists of key=value pairs, delimited by comma characters. These attributes are passed to the image managers of OPI. The keys and possible values recognized depend on the image managers.
Baseline (JPEG only) <boolean:FALSE>: Saves JPEG layout images per default in progressive method. If this option is set to TRUE, JPEG layout images are saved as baseline JPEGs instead.
DctMethod (JPEG only) <uint32:0>: Use slow, fast or precise DCT (0, 1, 2).
DCT = Discrete Cosinus Transformation
PDFLayer <string:"">: Select or deselect layers in PDF documents. See also the appendix “PDF layers” in the PDF HandShake manual.

The following two attributes are only supported for backward compatibility with previous ImageServer versions; please do not use these options for new installations or configurations. Use the option -o CompressQuality instead!

Quality (JPEG only!) <uint32:75>

Create poor…high quality JPEG image (1…100).

Quality (JPEG 2000 only!) <uint32:0>

Specifies the image quality of a JPEG 2000 image in relation to the uncompressed high-resolution original. The values range from 1…100. Specifying “0" means lossless.

Note:: Quality specifies the percentage size of the JPEG 2000 image data compared to the size of the uncompressed image, which the JPEG 2000 should not exceed. For example, if an image with lossless compression has only 50% the size of an uncompressed image, a Quality value between 50% and 100% produces no visible differences.

TileWidth (JPEG 2000 only!) <uint32:256>

Specifies the horizontal size of JPEG 2000 tiles. A JPEG 2000 image file consists of juxtaposed tiles. If the value specified is 0, the whole image merely consists of one tile.

TileHeight (JPEG 2000 only!) <uint32:256>

Specifies the vertical size of JPEG 2000 tiles. A JPEG 2000 image file consists of juxtaposed tiles. If the value specified is 0, the whole image merely consists of one tile.

Note:: The subdivision of a JPEG 2000 image in tiles accelerates the coding and decoding process significantly, and minimizes the memory requirement during the operational time. The best value, which meets operational time as well as memory requirement, is 256.

AntiAlias (PDF only) <boolean:TRUE>

This attribute determines whether the image is smoothed.

PageNumber <uint32:1>

This attribute lets you specify a certain page of a multi-page PDF, XPV or TIFF document for image conversion or creating layouts.

Password <string:"None">

This attribute allows image conversion from a password protected PDF file. Note that this attribute requires that “layout” is used in the image conversion mode (see 6.1.8 “Image conversion options”).

SaveUnseenColor (PNG only) <boolean:FALSE>

Usually, transparent points become white. This attribute leaves them in their original color if this option is set to TRUE. Does not work with indexed images.

ColorMasking (PNG only) <string:"None">

This attribute allows the definition of a transparency color. This color is set in the form <r>:<rd>,<g>:<gd>,<b>:<bd>. Each of these variables is a positive integer with values between 0 and 255. “r”, “g” and “b” are the red, green and blue values of the color that shall be transparent, while “rd”, “gd” and “bd” stand for the distance that a color can have to the transparent color and still be transparent. So ColorMasking=255:1,255:1,255:1 would mean: Every white pixel with RGB values between 255,255,255 to 254,254,254 shall be transparent.

Note:: This attribute only works with True Color or Indexed Color images.

WebOptimize (PNG only) <boolean:TRUE>

By default, all PNG-layouts are interlaced, so a web browser can show an impression of this picture while the image is still loading. If you want to turn this feature off you will have to use this option, e.g.:
layout -o Attributes "WebOptimize=FALSE"

6.1.6 Layout generation example

If you wish to create a JPEG-RGB layout from a TIFF-CMYK high-resolution image without a clipping path you have to induce the “layout ” program to convert CMYK color data into RGB and the TIFF file format into JPEG. In that case you use the PrintColor option to specify RGB. Furthermore, use the RasterImageType option to create a JPEG layout file. The complete command line is given below:

layout -v -o PrintColor=RGB -o RasterImageType=JPEG /images/cmyktif.tif

6.1.7 Image conversion

ImageServer can only convert raster images. If you wish to convert other image formats, you may create a PDF file from the vector image and convert it, or use the utility program psrip.

Note:: The HELIOS CD contains the “imageconv” script (in “sample-images/template-images%0”) as well as various sample images. “imageconv” can be used as an excellent source of “layout” command image conversion examples.

6.1.8 Image conversion options

-l file(s) destination

The -l option specifies that instead of generating a layout file, image conversion should occur. Highest quality converted images are then produced according to options which specify the output file format, color space, resolution, and compression. Image conversion can be executed from the command line, but more commonly is scripted in Script Server to enable interactive image conversion via hot folders and fully automated background image conversion.

When using the -l option, specify one or more files to convert as well as a destination file (if converting a single file) or directory (if converting several files).

Usage:

layout [options] -l file(s) destination

Example:

$ layout -o PrintColor=RGB -T TIFF -l file1.jpg file2.jpg
  /tmp/images

will convert “file1.jpg” and “file2.jpg” to RGB TIFF images and store them in “/tmp/images”.

The -l option may be combined with the -p option:

layout [options] -p polltime -l directory destination

When using the -l option together with the -p (polling) option, a destination directory must be specified with its absolute path.

Example:

$ layout -o PrintColor=RGB -p 45 -l /user/dir
  "{unix,native,,TIFF}/tmp/images"

Now, the layout process will go into the background, scan the given directory every 45 seconds for a new or changed image file, and then converts this file into a TIFF-RGB image which will be stored in the directory “/tmp/images”.

Note:: Script Server provides a faster, more efficient automation method, and is therefore recommended instead of polling. See 7 “HELIOS Script Server”.

-T (Format)

Set the target file format (JPEG, PNGf, TIFF, etc.) for an image conversion.

-o MultiInkSeparationColors <string list:None>

Defines the names and order of the color components when using Multichannel ICC profiles (5-8 channels). This option can be used if converting to the “Multi” color space. Usage of the “Multi” color space requires the use of ICC profiles. Future ICC profiles that include the names of the color components, will dispense with this option.

-o xPix || yPix <uint32:None>

Allows the user to define the size of the output file in pixels either in x or y direction. The layouts always maintain their aspect ratio. “layout” guarantees that the resulting output files will always be smaller than or equal to these sizes. If the use of xPix would mean that a given yPix value cannot be maintained, yPix will control the output file dimensions and vice-versa.

Example:

$ layout -o xPix=150 -o yPix=150 -l image.tif new.tif

This will create an output file named “new.tif” which is equal to or smaller than 150 by 150 pixels.

Note:: Due to the fixed aspect ratio, the image resolution may not be identical for x- and y-direction. When such an image is opened, e.g. using Adobe Photoshop, a pixel aspect ratio warning is shown. The automatic resolution can be overridden additionally using the PrintResolution (see 6.1.4 “Options for the layout file generation”) option which defines a fixed resolution in each direction. However, this may break the exact aspect ratio of the converted image.

-o ExifRotate <boolean:TRUE>

If the original image contains an Exif parameter specifying an orientation, the image is rotated so that the target image has the correct orientation.

-o ShowIncomplete <boolean:FALSE>

By default “layout” generates an error if an image was not written completely. If this option is set to TRUE there is no error if at least 5 lines were written. Instead, missing image lines will be filled with the content of the last read image line.

-o ApplyClippath <boolean:FALSE>

If the source image contains a clipping path, areas outside of this path will become white. If the target format supports transparencies the target image will get a new transparency channel, which makes areas outside of the clipping path transparent.

-o ChangeClippath <string:None>

If an image is converted into a different format that does not support multiple paths, this option can be used to generate a picture with the specified path as a mask object. It contains the name of the path object that shall be the new clipping path.

-o PureBlack <boolean:FALSE>

Exclude black colored raster objects in PDF files from color transformation, so that they remain black even if color matching is done. Black raster objects in Gray/RGB/CIELab/Indexed color spaces are detected and converted to Black only for CMYK output. This option can be used to override the default PureBlack preference described in 9 “Preferences and notification features”.

-o PureWhite <boolean:FALSE>

Exclude white colored raster objects in PDF files from color transformation, so that they remain white even if color matching is done. CMYK values will be zero, i.e. no ink is applied to the plates. This option can be used to override the default PureWhite preference described in 9 “Preferences and notification features”.

-o PureGrays <boolean:FALSE>

Exclude gray colored raster objects in PDF files from color transformation, so that they remain gray even if color matching is done. Gray raster objects in Gray/RGB/CIELab/Indexed color spaces are detected and converted to Gray only for CMYK output. This option can be used to override the default PureGrays preference described in 9 “Preferences and notification features”.

-o PureCMY <boolean:FALSE>

Applies to CMYK to CMYK conversions of pixels of raster images, and preserves the input color if, and only if, black is 0% and exactly one CMY primary color is 100% and all other primary colors are 0%. This option can be used to override the default PureCMY preference described in 9 “Preferences and notification features”.

-o PureVectorBlack <boolean:FALSE>

Exclude black colored vector objects in PDF files from color transformation, so that they remain black even if color matching is done. Black text and vectors in Gray/RGB/CIELab/Indexed color spaces are detected and converted to Black only for CMYK output.

-o PureVectorWhite <boolean:FALSE>

Exclude white colored vector objects in PDF files from color transformation, so that they remain white even if color matching is done. CMYK values will be zero, i.e. no ink is applied to the plates.

-o PureVectorGrays <boolean:FALSE>

Exclude gray colored vector objects in PDF files from color transformation, so that they remain gray even if color matching is done. Gray text and vectors in Gray/RGB/CIELab/Indexed color spaces are detected and converted to Gray only for CMYK output.

-o PureVectorCMY <boolean:FALSE>

Applies to CMYK to CMYK conversions of text and vector objects, and preserves the input color if, and only if, black is 0% and exactly one CMY primary color is 100% and all other primary colors are 0%.

-o ImportMask <string:None>

This option allows importing a clipping path from a different image into the target picture. The main reason for this feature is the ability to add a different or more precise clipping path into an image. Its parameter is the name of the picture that contains the clipping path that shall be imported (both pictures must be of the same size!).

Note:: For image formats with a lossy compression we recommend to tag the original image with the new path information instead of saving it anew. See 6.1.11 “Tagging ICC profiles, path information, and metadata to images”.

-o ConvertEpsCreator <string:None>

Some application programs, e.g. some Adobe InDesign versions, parse Photoshop resources only if they find a suitable creator in the file header. This option allows specifying a creator for converting images.

-o OutputProfile <string:None>

This option receives the path or file name of a suitable output profile, which is mapped to the target. In doing so, ICC color matching is enforced and the appropriate color space is defined for the profile. This option overrides the PrintColor option.

-o DevLinkProfile <string:none>

This option receives the path or file name of a Device Link profile as a parameter. In doing so, the standard ICC handling is overridden, and the target color space is internally set to the profile target color space. Then the source image is converted according to the DeviceLink profile directions and saved in the target format.

Note:: For easier identification, the target image metadata obtains the attribute Used DevLinkProfile with the path or file name as a parameter. The attribute can be displayed with “oiimginfo” (see 6.4 “oiimginfo”).

For the following 4 options, a number between 0.0 and 1.0 specifies a per cent value. A number > 1.0 specifies a pixel value.

-o cropLeft <double:0.000000>: Applies left margin cropping to the output image.
-o cropRight <double:0.000000>: Applies right margin cropping to the output image.
-o cropTop <double:0.000000>: Applies top margin cropping to the output image.
-o cropBottom <double:0.000000>: Applies bottom margin cropping to the output image.

The next three options only work for the generation of non-EPS images. They do not work if the specified target image format is EPS.

-o rotate <double:0.000000>: Rotates the generated output image clockwise a certain number of degrees (0, 90, 180, 270 are permitted).
-o flipVertical <boolean:FALSE>: Causes the generated output image to be flipped around the vertical centerline (swap right and left).
-o flipHorizontal <boolean:FALSE>: Causes the generated output image to be flipped around the horizontal centerline (swap top and bottom).
-o RemoveAfterConvert <boolean:FALSE>: If set to TRUE, original files which have been converted will be removed after a successful conversion.
-o SkipLikeLayout <boolean:FALSE>: If set to TRUE, layout -l will skip files that are not image files, just as “layout” in standard mode would.
-o IncludeRef <boolean:FALSE>: If set to TRUE, a converted file will contain a reference to the original file. This is similar to a generated layout file, which contains a reference to the original high-resolution file.

6.1.9 Image conversion examples

Example 1:

If you want to create a JPEG-RGB image from a TIFF-CMYK high-resolution image without a clipping path, you have to induce the “layout” program to convert CMYK color data into RGB and the TIFF file format into JPEG. In that case you use the PrintColor option to specify RGB. Furthermore, you must use the file format option to create a JPEG file. The complete command line is given below:

$ layout -v -o PrintColor=RGB -T JPEG -l cmyktif.tif rgb.jpg

Example 2:

The “imageconv” script which uses many of the image conversion features can be found on the HELIOS CD in the sample-images/template-images%0 folder.

The “template-images%0” directory contains about 90 MB of sample images and the “imageconv” Perl script. This script uses the “layout” command with several options to convert the original images to any supported image type with different color spaces. After the conversion is finished all images will take about 1.8 GB of hard disk space.

Note:: The “imageconv” script will run – depending on the used server – in as little as 4 minutes on a fast server, or over 30 minutes on a slower server. “imageconv” converts images sequentially. Therefore only one CPU is used.

6.1.10 “OpenImage” file specification

Though the classic “OpenImage” file specification is still supported by HELIOS, we recommend to use the -T option instead (see 6.1.8 “Image conversion options”).

If used, the “OpenImage” file specification is included as part of the -l option.

Usage:

layout [options] -l file(s) destination

Example:

$ layout -o PrintColor=RGB -l file1.jpg file2.jpg
"{unix,native,,TIFF}/tmp/images"

will convert “file1.jpg” and “file2.jpg” to RGB TIFF images and store them as plain UNIX files in “/tmp/images”.

The image type of the destination file(s) is given by specifying the destination as a complete “OpenImage” file specification.

The “OpenImage” file specification precedes the file or directory name and is put in braces. It is structured as follows:

{File System Type, FileRepresentation, Creator, ImageType, ImageTypeExtension}

FileSystem Type must be unix.

FileRepresentation may be either native, ES or PCS.

Creator is a Mac file creator signature (if left blank, 8BIM for Adobe Photoshop is used).

ImageType is a file type signature (as e.g. TIFF or EPSF; see Table 3.3 in 3.2.3 “Supported file formats”).

If the target image file format (ImageType) is omitted, the file format of the source image is used, e.g.:

$ layout -l image.eps "{unix,native,,}TARGETIMAGE"

creates an EPS image and

$ layout -l image.tif "{unix,native,,}TARGETIMAGE"

creates a TIFF image.

ImageTypeExtension is an optional extension to the file type and may be empty.

6.1.11 Tagging ICC profiles, path information, and metadata to images

The “layout” program can also be used to tag ICC profiles to image files. In addition, path information and image metadata can be added, deleted or modified. To do so, the -f option must be specified with appropriate substrings, which are described below. This method has the advantage (over the -o ImportMask method; see 6.1.8 “Image conversion options”), that it does not save the image data completely anew, but only the tagging information, and thus does not deteriorate the image quality when processing lossy files.

6.1.12 Tagging options

-f <string list:None>

This option sets “layout” into a tag only mode, so only the specified file is modified (irrespective of an existing “!iccinfo.oic” file for ICC tagging). The -f option gets a string with up to three substrings, that are concatenated by a colon (“:”). You can issue multiple tag orders in one layout command by specifying multiple -f options.

Note:: Exporting metadata (paths, ICC profiles, etc.) is done via the “oiimginfo” utility (see 6.4.3 “Export”).

Object defining substring

The first substring contains an object type; valid object types are:

ICC: Add or delete a named ICC profile.
PATH: An image mask or path.
CLIP: Modify the clipping path parameter. It can either be deleted or will define a named path as the clipping path.
IPTC: Delete the IPTC information of this image or import IPTC information of another image.
XMP: Delete XMP information or import XMP information of another image or special XMP file.
RESO: Change image resolution (implemented for TIFF, JPEG, PNG and Photoshop images).

Action defining substring

The second substring defines an action; valid actions are:

ADD: Add ICC profiles, a clipping path or metadata to a file. For ICC profiles this will only work if the substring also contains an “EMB” or “REF” to define how a profile will be added. To “ADD” paths, clipping path information or IPTC information, that were exported by “oiimginfo”, use the substring “ADDRES” (short for add resource). Note that “ADD” will not override an existing resource, for this, use “OVER”.
DEL: Delete the specified object.
OVER: Almost the same functionality as “ADD”, with the difference that “OVER” overrides existing ICC profiles.

Parameter defining substring

The third parameter will either contain the name of a profile, a color space name, the name of an image, a path name, the name of a special file, or resolution or size values. The following table summarizes possible combinations:

Object	Action	Parameter
ICC	ADDEMB/OVEREMB ADDREF/OVERREF DEL	<profile_name> <profile_name> (<color_space>)
PATH	ADD ADDRESS DEL	<image_name> <path_name> (<path_name>)
CLIP	ADD DEL	<path_name> (<path_name>)
IPTC	ADD DEL	<path_name> <path_name>
XMP	ADD DEL	<path_name> <path_name>
RESO	INCH CM SIZE SIZECM	<xRES>,<yRES> <xRES>,<yRES> <xSIZE>,<ySIZE> <xSIZE>,<ySIZE>

Examples:

$ layout -f "ICC:ADDEMB:Testprofile" test.jpg

tags the image “test.jpg” with the embedded ICC profile “Testprofile”.

$ layout -f "ICC:DEL" test.jpg

deletes all embedded or referenced ICC profiles from the image “test.jpg”.

$ layout -f "ICC:DEL:RGB" test.pdf

deletes only the RGB profile from the PDF file “test.pdf”.

$ layout -f "PATH:ADD:Import.jpg" test.jpg

imports the clipping path from the image “Import.jpg” and adds this to “test.jpg” as a path, but not as the clipping path. If the imported path should also be designated as the clipping path, then the “CLIP” tag order must be specified as well.

$ layout -f 'PATH:ADDRES:Sky.path" test.tif

adds the path “Sky”, that was exported by “oiimginfo” to the file “Sky.path”, to the image “test.jpg”. If “test.jpg” already contains a path named “Sky”, the new path will be renamed to “Sky-1”. If there is already a “Sky-1”, it will be renamed to “Sky-2” and so on.

$ layout -f "PATH:DEL:Pfad 1" test.jpg

deletes the path “Pfad 1” from “test.jpg”. The clipping path resource will not be changed by this order. So you should delete or change the clipping path resource also if “Pfad 1” is the clipping path.

$ layout -f "CLIP:ADD:exactMask" test.jpg

sets the path “exactMask” as the clipping path for the image “test.jpg”.

$ layout -f "CLIP:DEL" test.jpg

deletes the clipping path definition from “test.jpg”.

$ layout -f "XMP:ADD:test.xmp" image.jpg

adds the content of the special XMP file “test.xmp” to the file “image.jpg”, replacing all existing XMP metadata. Such an XMP file can be generated either by Photoshop or you can get the XMP information of an image as an XMP file by use of the command oiimginfo -E xmp -f <exportfile.xmp> file. The tagging option recognizes special XMP files by their “.xmp” suffix. If the named file would have a suffix other than “.xmp” it will try to open this file as an image, and retrieve the XMP resources of the given image.

$ layout -f "RESO:INCH:237,237" test.jpg

sets the resolution of the file “test.jpg” to 237 dpi.

$ layout -f "RESO:SIZE:10,8" test.jpg

defines the image dimensions to 10x8 inches.

$ layout -f "RESO:SIZECM:1,2" test.jpg

defines the image dimensions to 1x2 cm.

Note:: The “oiimginfo” program can be used to list path and ICC profile information. For further details, see 6.4 “oiimginfo”. The PDF HandShake tool “pdfinfo” can also be used to list ICC profiles in a PDF document.

Examples:

$ oiimginfo -E path Cafeteria.tif 
Path PSID=2000 , Name: Sky , size: 6396
Path PSID=2001 , Name: House , size: 3068
Path PSID=2002 , Name: Table , size: 338
	
$ oiimginfo -E clip Cafeteria.tif
Table

$ oiimginfo -E icc Cafeteria.tif
1: embedded profile , colorspace: RGB , size: 201892 bytes ,
   Id: (C) Linotype-Hell TOPAZ Fuji Transparent

The PDF HandShake “pdfinfo” program can also be used to list tagged ICC profiles:

$ pdfinfo -o Profile Duo2.pdf 
# pdfinfo 5.0.0
Profile: ColorSpace=DeviceCMYK,
   Path="ICC-Profiles:Printer:HELIOS:Euro 2.6 UCR-370", Reference
Profile: ColorSpace=DeviceRGB,
   Path=ICC-Profiles:Scanner:HELIOS:CCIR-EBU-RGB, Reference

Limitations

Layouting or converting in a non-HELIOS volume does work. However, file events are not reported to the HELIOS notification server because the HELIOS file events only notify about events in HELIOS volumes.

In addition, Mac resources like icons, file comments, etc. are not supported in non-HELIOS volumes.

6.2 opitouch

The “opitouch” command allows triggering the generation of low-resolution OPI layout files. Although this could also be done with the “layout” command, the benefit of “opitouch” is that jobs are processed by “opisrv”, which uses the global OPI parameters and OPI folder options for layout generation.

Usage:

opitouch [-h host][-s service][-dr] files ... 
opitouch [-h host][-s service] -e event ...

Important:: Make sure that you specify files with their absolute path name!

“opitouch” is the command line version of the program “Touch”, allowing virtual touching of image files without modifying the file date or time of the high-resolution files, while causing automatic OPI layout generation. Of course, if “opitouch” is used to trigger a “Tagger” ICC info file to tag ICC profiles to images, then their file date would be changed as a result. “opitouch” allows touching single files, all files of a directory or even a complete directory tree on the local or remote system.

Important:: “opitouch” does not recognize the types of the files specified. So touching whole directories containing a non-image file does not produce any error, even if no layout image is generated! However, when touching a single non-image file, “opisrv” issues a syslog error message.

Unless otherwise specified, “opitouch” touches files on the local host.

-h

Allows you to select a remote host by name or its IP address. You may only gain access to ImageServer systems with appropriate IP access control setup. This can be done with HELIOS Admin, using the IP Access dialog. The remote host must have the OPI server preference RemoteAccess set to TRUE.

-s

Allows you to select the OPI event service port of the “opisrv” by name or port number. Specifying a service port that is served by anything other than “opisrv”, may cause “opitouch” to hang. The default service used is OPIEvent, or its default port number 2002.

Unless otherwise specified (see -d and -r below), “opitouch” assumes that the path name arguments refer to plain files. In this case, directories will be ignored by the contacted “opisrv”.

-d

Requires all path names to be directories. In this case, all plain files within the specified directories will be touched. Subdirectories will be skipped.

-r

Requires all path names to be directories. In this case, all plain files and subdirectories contained in the specified directory path names will be touched recursively.

Note:: Be aware that the usage of this option may cause heavy system load on the OPI server system.

-e

This option sends events to the “opisrv”:

sendlayout "file name" 
sendclose "file name" [file type] 
sendrename "file name old" "file name new" [file type] 
senddelete "file name" [file type] 
sendcreatedir "directory name" 
sendrenamedir "directory name old" "directory name new" 
senddeletedir "directory name"

Example:

$ opitouch -e sendclose "/data/images/cover.tif"

The optional file type is the Mac four character type code. If the file type is not specified it is determined from the file’s resource fork. For the delete event (senddelete) a file type should be specified because it is not possible to determine the type of a file that is already deleted. The file and directory names are distributed to the registered listeners “as is”, the existence of the objects is not verified.

Note:: All files and directories must be specified with their absolute path names beginning with a “/” character. The path names must NOT end with a “/” character!

6.3 hirespath

The “hirespath” program can be used for three purposes. In the first mode, it can resolve an OPI layout file name to the appropriate high-resolution path name. It receives the low-resolution file name as a command line argument or on “stdin” and prints the file name of the high-resolution image on “stdout”. In doing so, it recognizes certain OPI printer interface parameters (see -o below):

hirespath [-P <printer>] [-d <pathprefix>] [<loResRef>]

<printer>

The name of a printer queue. “hirespath” will then access the OPI parameters for that printer queue.

<pathprefix>

A HELIOS server directory path name which precedes <loResRef> or <clientName>. If this parameter is supplied, <loResRef> or <clientName> has to be a file name without directory specification. <pathprefix> must NOT end with a “/” character!

<loResRef>

File name or reference of the low-resolution image. It can be in the format of the client’s file system (Mac, PC). The file name is quoted to allow for spaces. If <loResRef> is omitted, “hirespath” will read <loResRef> from “stdin”.

Result: <hiResRef>

File name and path of the high-resolution image. Nothing is printed on “stdout” if the program cannot resolve <loResRef>. The high-resolution file location has the format of the native file system on which “hirespath” is running.

The return code can be any of the following:

0
Success; <loResRef> was successfully resolved into <hiResRef>, the high-resolution file is accessible. <hiResRef> is printed on “stdout”.

1
Error; An error occurred. An explanatory error message is printed on “stderr”. Nothing is printed on “stdout”.

2
Error; <loResRef> cannot be resolved into <hiResFile>. If the theoretical <hiResFile> is reasonable, it is printed on “stdout”.

3
Error; <loResRef> can be accessed but is a <hiResRef> and the parameter resolveall is not set. If the theoretical <hiResFile> is reasonable, it is printed on “stdout”.

4
Error; <loResRef> can be accessed but is not a valid layout file. Nothing is printed on “stdout”.

“hirespath” may also check a complete PostScript job for OPI references and give a detailed report on “stdout”. If checking a PostScript job, “hirespath” receives a file name of the job to check as a command line argument or uses “stdin” as source:

hirespath -j [-P <printer>] [<PostScriptFileName>]

-j

When the -j option is specified, the argument to “hirespath” is a <PostScriptFileName>. “hirespath” will then check the PostScript job for all OPI references and check each reference as described above. On exit a report will be printed on “stdout” as a list of <opiRef> references, each on a single line.

The return code can be any of the following:

0
Success. All OPI references could be resolved.

1
Error; an (UNIX) error occurred. An explanatory error message is printed on “stderr”. Nothing is printed on “stdout”.

2
Error; one of the OPI references could not be resolved.

<PostScriptFileName>

Name of a file containing a PostScript print job.

“hirespath ” returns the name or reference on “stdout”, and returns an integer to indicate the result of the operation:

Result: <opiRef>

<code>\t(<reference>)\t(<resolvedName>)

<code> is one of the return codes listed above, <reference> is the OPI reference found in the PostScript file and <resolvedName> is the name of the replaced image. <resolvedName> may be empty. The names are quoted in (), using the ADSC quoting conventions.

In a third mode, “hirespath” can map client (Mac or PC) file names to host path names:

hirespath -m [-d <pathprefix>] [<clientName>]

-m

When this option is specified, “hirespath” is a <clientName> and the result will be a <hostPath>. In this case, “hirespath” will map a client file name <clientName> to a host system path name <hostPath> without OPI resolving. This works for Mac and PC client file names. There are a few restrictions:

Mac client file names must begin with an AFP volume name as specified in the volume preferences
PC client file names must refer to existing files or directories on a PCShare volume

The return code can be any of the following:

0
Success; <clientName> was successfully mapped into <hostPath>, and the file is accessible. <hostPath> is printed on “stdout”.

1
Error; An error occurred. An explanatory error message is printed on “stderr”. Nothing is printed on “stdout”.

2
Error; <clientName> cannot be mapped into <hostPath> or <hostPath> is not accessible. If the theoretical <hostPath> is reasonable, it is printed on “stdout”.

A file that resides on a HELIOS host system may have its name presented in a different syntax when viewed from a client system. The “hirespath” -m option will accept any <clientName> file name, in a client system syntax. The output will be the corresponding path and file name of <clientName>, in the native file naming syntax of the HELIOS host. This is a name mapping function, and does not require that the file be a layout file or PostScript job. Even if the <clientName> file does include OPI references, they will be ignored, and only the <clientName> file name will be mapped to a host system file name.

<clientName>

File name of a Mac or PC file. If <clientName> is omitted, “hirespath” will read <clientName> from “stdin”.

Result: <hostPath>

Mapped UNIX path name of <clientName>.

In this case, “hirespath” will map a client file name <clientName> to a host system path name <hostPath> without OPI resolving.

6.3.1 Additional “hirespath” arguments

“hirespath” always understands the arguments:

-e: Enable explanatory error messages of unresolved references.
-o: Set an option using the -o Parameter=Value syntax. ImageSearchPaths, ImageSearchVolumes, and ImageIDSearch (see 9.1.5 “OPI-related printer queue preferences”) can be specified.

6.3.2 Example

The example shows the command you have to enter if you want the program to return the path name of a high-resolution image for a given layout image in a print job:

$ hirespath -P lw /Volumes/OPI-Test/layouts/Band.tif

The server returns the following statement:

/Volumes/OPI-Test/Band.tif

6.4 oiimginfo

“oiimginfo” prints information about a given image file. The -v option can be used to restrict the amount of output. The default is to print all OpenImage-related information.

If the -E option (export mode) is set, only special information is printed to “stdout” or to a file.

Usage:

oiimginfo [-v] [-a] [-E [-I] [-f]] [-p] [-h] file

6.4.1 Options

-v <VerboseLevel>

Restrict the “oiimginfo” output to the given levels. See 6.4.2 “Verbose/Filter levels” below.

-a <Attributes>

Comma-separated list of attributes for the image manager. See 6.4.4 “Attributes for “oiimginfo”” below.

Example:

oiimginfo -aPageNumber=28

-E <ExportType>

Print the selected type of information to standard output or to a file. See 6.4.3 “Export” below.

-I <ExportId>

Select a particular object of the given <ExportType>, used e.g. with text boxes.

-f <ExportFile>

Print the export information to <ExportFile> instead of standard output.

-p

Provides basic information (e.g. path, class and colorspace) on the ICC profile, identified by the string.

-h

Display help file.

6.4.2 Verbose/Filter levels

-v <VerboseLevel> is a comma-separated list of keywords.

Keywords are case-insensitive and can be abbreviated as long as the abbreviation is unique.

Filter keywords

Filter keywords can be used to specify which objects in the image are described in detail, depending on the image type, quality or access method.

Type filter keywords:	`Image,Plate,OtherTypes`
Quality filter keywords:	`Print,Proof,Screen`
Access filter keywords:	`Raster,PostScript,Unspec`

If a filter keyword is given for one of these categories, only the corresponding objects in the image are described in detail.

Selector keywords

Selector keywords can be used to specify the amount of information printed.

Generic selector keywords:	`ObjBase,LFile,RFile,Manager`

Default:	`ObjBase`

GFX selector keywords:	`GFXBase,GFXInk,GFXICC,GFXAttributes,`
	`GFXResources,GFXVerboseResources`

Default:	`GFXBase,GFXInk,GFXICC,GFXAttributes,`
	`GFXResources`

NoGFX can be used to suppress all GFX output.

Shortcuts:

`GFXContent`	`= GFXBase,GFXVerboseResources,GFXAttributes`
`IInfo`	`= Image,GFXContent`
`RImage`	`= Image,Print,Raster`
`PImage`	`= Image,Print,Postscript`
`XPVInfo`	`= Image,Print,GFXVerboseResources,GFXAttributes`

6.4.3 Export

With the -E <ExportType> option, special types of information can be extracted from the image file and printed to “stdout” or to the file given by -f <ExportFile>.

<ExportType> can be one of: XMP, Text, Attributes, Base, Clip, IPTC, Path, ICC.

<ExportType> is case-insensitive and can be abbreviated, as long as the abbreviation is unique.

The -v option can be used with filter keywords to select an object. If there is more than one object containing the wanted export type, the content of the best object is selected.

Export types in detail:

XMP: Dumps the XMP information of a file. You can set an empty file name to generate an <ImageFileName>.xmp in the directory of the image file.
Text: Dumps the contents of all text boxes or of the text box specified by -I <ExportId>. You can set an empty file name to generate the file <ImageFileName>.txt[number] in the directory of the image file.
Attributes: Dumps the attributes of an image.
Base: Dumps the basic image information of an image.
Clip: Dumps the name of the clipping path.
IPTC: Dumps the binary content of the IPTC objects.
Path: Without -I you get an overview of all included paths. -I <PathName> dumps the binary path.
ICC: Without -I you get an overview of all included profiles. -I <ProfileNumber> dumps the binary profile.

Example:

$ oiimginfo -E PATH -I Sky -f Sky.path export.tif

Export the path “Sky” from “export.tif” into the file “Sky.path”, that can later be added by the “layout” program to another image, see 6.1.12 “Tagging options”.

6.4.4 Attributes for “oiimginfo”

PageNumber <uint32:1>: This attribute allows you to specify a certain page of a document for which image information is provided.

Example:

$ oiimginfo -a PageNumber=3 test.xpv

6.5 psresolve

Note:: Technically speaking, “psresolve” is a HELIOS Base utility program. However, most of the options are set in an ImageServer environment. Therefore, “psresolve” is described in this manual.

The “psresolve” program acts like a printer driver, e.g. “smbif”. Instead of sending the PostScript output to the network, “psresolve” passes all PostScript data to “stdout” which can be redirected into a file or piped to an application.

The “psresolve” program lets you set printer interface OPI options manually on the server for one single print job. These options override the settings in the preference database for the specific spooler:

psresolve [options] [SpoolerName]

In the following, we list the parameters that may be set with “psresolve” and then – at the end of this chapter – give you an example that may be used for a specific workflow.

6.5.1 Options

Printer interface related parameters are entered as command line options using the -o Preference=Value syntax.

OpiEnabled <boolean:FALSE>

This option turns OPI functionality on or off. If it is set to TRUE, OPI image replacement is enabled.

ImageSearchPaths <string list:None>

Specifies a list of path names where to search high-resolution images during image replacement, in case they cannot be found in the standard locations.

ImageIDsearch <boolean:TRUE>

This parameter enables the use of the HELIOS desktop database to locate moved image files.

PrintDraft <boolean:FALSE>

If set to TRUE, the printouts from the specific printer queue will only contain layout images. The copies of the images – which you have used for layouting your document – will be sent to the OPI server and then be replaced by the layout files instead of the high-resolution originals.

CheckFonts <boolean:TRUE>

This parameter ensures that all fonts used in the document will be checked before printing. Every missing font will be reported and this will stop the print job.

CheckImages <boolean:TRUE>

This parameter ensures that all images placed in the document will be checked before printing. Every missing image will be reported and this will stop the print job.

CheckICCProfiles <boolean:TRUE>

Specifies whether existence of ICC image profiles has to be verified before printing. The server will automatically stop the print job if a single profile is missing and issue a corresponding error message.

CompatCheck <boolean:TRUE>

Specifies whether special PostScript setup has to be included to avoid application specific problems during printout. This is necessary for FreeHand 3.1, PageMaker 5 and QuarkXPress 3.0.

ResolveAll <boolean:FALSE>

If this parameter is set to TRUE, all images will be replaced during printout. Otherwise only layout images are resolved.

PureBlack <bool:FALSE>

Determines whether black pixels are excluded from color matching.

PureWhite <bool:FALSE>

Determines whether white pixels are excluded from color matching.

PureGrays <bool:FALSE>

Determines whether gray pixels are excluded from color matching.

PureCMY <bool:FALSE>

This option determines whether pure Cyan, Magenta or Yellow pixels are excluded from color matching in CMYK to CMYK conversions. Pure Cyan pixels have 100 percent Cyan and 0 percent for other colors. Pure Magenta pixels and pure Yellow pixels are defined similarly.

KeepInfo <boolean:TRUE>

Specifies whether in case of resolving an already resolved PostScript job, the use of fonts and other resources should still be accounted.

DefaultPrinterProfile <string:None>

This parameter specifies the path name of the default ICC profile describing the printing device.

DefaultProofProfile <string:None>

This parameter specifies the path name of the default ICC profile describing the proof device. The string will only be recognized if a default printer profile is set.

DownSampling <boolean:FALSE>

This option – if it is set to TRUE – allows downsampling of images to a given output resolution. The value that has to be used for printing is specified by the Resolution parameter below.

FixedSampling <boolean:FALSE>

This option allows fixing the downsampling resolution (see the Resolution parameter below) to the given value. Usually, if this parameter is set to FALSE, the output resolution is adjusted to the image resolution if the image resolution is smaller. When setting this parameter to TRUE the printer interfaces will use the given Resolution as is for downsampling. This may cause upsampling of images with resolutions smaller than the given one. This parameter makes only sense when setting the DownSampling parameter to TRUE.

FastDownSampling <boolean:FALSE>

This option controls the downsampling algorithm. By default, a bilinear algorithm is used. If you set this option to TRUE you switch to a fast picking algorithm. This parameter is only meaningful when setting the DownSampling parameter to TRUE.

Resolution <double:0.0>

This option controls the resolution of downsampled images. Zero induces the software to use the default resolution of the printing device as specified in the queue's PPD file. This parameter is only meaningful when setting the DownSampling parameter to TRUE.

ProcessColorspace <string:”CMYK”>

This option sets the color space used while printing separations. The default is CMYK for a four color print process. Spot colors are not affected by this parameter. Valid color spaces are "CMYK" and "Multi". If you set the string to "Multi" you have to define the names and order of the color components. Furthermore, the usage of the "Multi" color space requires the use of ICC profiles. For (future) ICC profiles that include the names of the color components, this option will become obsolete. Please note that the value you choose for this option can be overridden by the printer profile you have selected using the DefaultPrinterProfile option.

ProcessInks <string list:”Cyan”,”Magenta”,”Yellow”,”Black”>

This option controls, together with the ProcessColorspace option, the names of the process inks used for separations. Spot colors are not affected by this parameter.

CompositeColorspace <string:”CMYK”>

This option sets the color space used while printing composite. The default is CMYK. Setting this option to None causes all color images in a print job to be kept and printed in their original color space. This applies to CMYK, CIELab and RGB images only. Valid strings are CMYK, RGB, and CIELab. Please note that the value you choose for this option can be overridden by the printer profile you have selected using the DefaultPrinterProfile option.

CompressPostScript <string:None>

This option selects a compression mode for images while being printed. CCITT Group 4, JPEG (Low to Max.), ZIP, and Compress are currently supported.

MaxLowResolution <double:72.0>

When printing layout images, ImageServer is able to scale down a high-resolution image to layout quality on the fly if the layout image cannot be found. This parameter controls the maximum resolution used for printing these transformed images.

IgnoreMissingLowRes <boolean:TRUE>

Use this parameter to specify whether non-existing layout images should be ignored when printing layout quality. If set to FALSE, and any layout images are missing, then the print job will be passed to the error queue.

TemporaryTagging <boolean:TRUE>

This parameter enables the use of the ICC info files while printing images. If it is set to TRUE, every non-tagged image will be temporarily tagged during printing provided that the ICC info file specifies tagging for that kind of image.

IgnoreUntagged <boolean:TRUE>

This parameter controls whether non-tagged images should be ignored when printing to an ICC color matched queue.

ScitexApr <boolean:FALSE>

This parameter – if it is set to TRUE – tells ImageServer not to resolve OPI comments if printing a PSImage file to an APR-aware RIP.

Note:: The parameters which are described in the following two paragraphs will usually be specified when setting up EtherShare. They may, however, be relevant to ImageServer as well and can therefore be set as preferences, too.

IgnoreResolveOpts, IgnoreProcsetResolveOpt, IgnoreFontResolveOpt, IgnoreIncludeResolveOpt and IgnoreOpiResolveOpt <boolean:FALSE>

When printing from a HELIOS spooler to a second HELIOS spooler, print jobs will usually not be resolved a second time. Specifying one or more of these options for the second spooler re-enables resolving of fonts, procsets, included files or OPI comments.

ExtendedInfo <boolean:TRUE>

Enables explanatory accounting. The accounting file will e.g. include the OPI image replacement list.

6.5.2 Example

Imagine you want to print a document using the CompressPostScript option. For that purpose you have to change the default setting for this particular print job using the “psresolve” program. The complete procedure is described below:

: First of all, set up two different printer queues using HELIOS Admin. One queue (e.g. “real_printing”) is to be used for printing to an output device and the other one (e.g. “print_to_disk”) is to be used for printing to a PostScript file (spool only).

: Make sure that Spool only has been activated for the “print_to_disk” queue (Printer menu) and then print to this queue from your layout application.

Then, on your server, change to the spool directory that now contains your print job (e.g. “/usr2/spool/print_to_disk”):

$ cd /usr2/spool/print_to_disk

Start the “psresolve” program, enter the parameters you want to use, and specify the queue name, the input file name (e.g. “your_print_job”) and the output file name:

/usr/local/helios/bin/psresolve -o 
CompressPostScript=Compress print_to_disk 
<your_print_job >your_print_job_output

Finally, you may send the file “your_print_job_output” to your Spool & Print printer queue for output:

/usr/local/helios/bin/ 
lpr -Preal_printing your_print_job_output

Please note that the “real_printing” printer queue will not resolve your print job again. The job will be printed according to the settings that had been specified for the “print_to_disk” queue using HELIOS Admin and/or according to the parameters set by the psresolve command line.

6.6 psrip

The “psrip” utility is a command line PostScript RIP application which is suitable for creating previews of vector EPS and PostScript files.

Usage:

psrip [-v] [-o Option] [-m] [-T] [-A] [-l <level>] [-V version]
      [-e <xpixel,ypixel>] [-p <width,height>] [-s <xshift,yshift>]
      [-N <serialno>] [-i <InputFileName>]
      <OutputFilenameBase>

The following options are supported:

-v

Display progress.

-o PrintResolution=<resolution> or <XResolution,YResolution>

Device resolution in dpi (default is 72.0). Ignored, if page dimension in inch (-p) or page dimension in device pixels (-e) is set.

-o PrintColor=<color space>

Select device color space CMYK, RGB or Grayscale (default is CMYK). For best color space conversion of EPS images, specify the image's current color space for PrintColor, and then use “layout” to perform an ICC color space transform on the output file.

-o inripseparation

Enable in-RIP separation. One image file per each colorant is written, unless you want to produce a multichannel image file (-m).

-o TransparencyMask=<flag>

<flag> can be “on” or “force”. “on” induces “psrip” to generate a transparency mask, as long as the PostScript file contains transparencies. “Force” enforces the generation of a transparency mask even though there are no transparencies in the document and hence the mask is empty. In doing so, a consistent paging within the output file(s) is guaranteed.

The transparency mask is saved into a separate grayscale file by “psrip”, unless a multichannel image file is generated (see -m option below). In such a case, the transparency mask appears as a separate channel in the output file.

-o KeepAspectRatio

This flag is an addition to the -e option. The page dimension in device pixels of the raster image has the same aspect ratio as specified by width and height (-p). The -e option then specifies maxima:
The raster image is smaller than or equal to these values.
This option has no result if the device resolution is set (-o PrintResolution).

-o SeparationOrder=<separation order list>

List of colorants, written as output. This option does only work with the inripseparation option. The value is a list of colorant names, separated by commas.

If a colorant name contains spaces, the whole list must be surrounded by quotes. The colorant names must be defined either implicitly by color space (Cyan, Magenta, Yellow, Black, Red, Green, Blue or Gray) or by SeparationColorNames. If SeparationColorNames is not used, each unknown colorant (not implicitly defined by color space) is supposed to be a spot color.

-o TextQuality=<str:"high">

Determines the text rendering quality. There are two values available, “high”, which is the default, and “low”. “high” means that a font-specific algorithm is utilized for rendering the glyphs more accurately. “low” has the advantage of faster rendering.

-o ImageQuality=<str:"high">

Determines the image rendering quality. There are two values available, “high”, which is the default, and “low”. If an image has a higher resolution than the output device, and is therefore downscaled, a better image rendering algorithm is used. This needs some time, so this option is primarily meant to switch this algorithm off.

-o SeparationColorNames=<spot color list>

List of available spot colors. This option does only work with SeparationOrder and the inripseparation option. The value is a list of colorant names, separated by commas.

If a colorant name contains spaces, the whole list must be surrounded by quotes. If this option is specified, only colorant names defined here can be used in SeparationOrder as spot colors. If a PostScript job uses a separation or DeviceN color space, the color space tint transform is not used, if the according (spot) color(s) are known (and thus listed for this option).

-o RasterImageType=<image format>

The default raster image format is TIFF. If ImageServer is not installed, this option is not available and images are written as raw files. Supported output file formats are listed in 6.6.1 “Output file formats”.

Image format specific settings, e.g. quality, can be specified via attributes (see -o Attributes=<attributes> below).

-o RasterImageSuffix=<output file suffix>

Suffix of the raster image output file. The default is derived from the image format, e.g. .tif for TIFF.

-o CompressQuality

Defines the compression quality of output image files or image components:

For JPEG:
-o CompressQuality <uint32:75>
Creates poor…high quality JPEG image (1…100).

Note:: CompressQuality specifies the percentage size of the JPEG2000 image data compared to the size of the uncompressed image, which the JPEG 2000 should not exceed. For example, if an image with lossless compression has only 50% the size of an uncompressed image, a CompressQuality value between 50% and 100% produces no visible differences.

-o CompressPrint=<compression>

Compression used by the raster image file. Some raster image file formats support several compressions (e.g. Zip compression in TIFF files).

By default, there is no compression method set. To use a compression method, specify this option with one of the following supported methods:

`Flate`	Zip compression format
`JPEG`	JPEG compression format

-o vmsize=<VM size>

Size of the local VM in bytes (default is 60 MB). If vmsize ends with the suffix “K” or “M”, kB or MB are specified, e.g.: -o vmsize=75M.

-o gvmsize=<global VM size>

Size of the global VM in bytes (default is 10 MB). If gvmsize ends with the suffix “M” and “K”, kB or MB are specified, e.g.: -o gvmsize=15M.

-m

Use this option and enable in-RIP separation (-o inripseparation) to create multichannel image files instead of one file per separation. The following image formats support multichannel image files:

TIFF
Adobe Photoshop
JPEG 2000

Note:: Photoshop displays spot colors in multichannel images as process colors during the presentation. “psrip” does the calculation by use of spot color tables (see “Proof printing files with spot colors” in the HELIOS PrintPreview manual).

-T

Create an image with a transparent background. This option is only available for TIFF and PNG images (see -o RasterImageType=<image format>).

-A

Do antialiasing (four-times oversampling).

-l (level)

PostScript language level (1, 2 or 3). Default is 2.

-V <version>

Set the PostScript interpreter version (e.g. 3015.102).

-e <xpixel,ypixel)>

Page dimension specified in device pixels. xpixel and ypixel must be separated by a comma. The default values are 595 (xpixel) by 842 (ypixel).

-p <width,height> or -p <paper format>

Page dimension specified in inches. width and height must be separated by a comma. The default is 8.26 (width) by 11.69 (height). Alternatively, the paper format can be specified. The default is <A4>.

Supported page sizes:

Letter, Legal, Executive, Ledger, A0, A1, A2, A3, A4, A5, B0, B1, B2, B3, B4, B5, B6

-s <xshift,yshift>

Shift coordinate system in inches. Positive is direction upper/right. xshift and yshift must be separated by a comma. The default values are 0 (xshift) by 0 (yshift).

-N <serial number>

PostScript RIP serial number.

-i <input file name>

File name of the PostScript or vector EPS file. If no file name is specified, PostScript is read from “stdin” (reading from “stdin”, “psrip” cannot handle binary EPS headers).

If PostScript is read from a file (instead of “stdin”), “psrip” can handle files containing a binary EPS header.

OutputFilenameBase

Output files will be named:

<OutputFilenameBase>.<PageNumber>.<OutputFileSuffix>

or if in-RIP Separation is enabled (-o inripseparation) and one image file per colorant is written:

<OutputFilenameBase>.<PageNumber>.<ColorantName>.
<OutputFileSuffix>

Multichannel image files are named in the standard manner of output files.

-o Attributes=<attributes>

Attributes specifying details of the used image format. This option is only available, if ImageServer is installed. <Attributes> is a comma-separated list of key=value pairs. For a list of available attributes see 6.6.2 “Attributes for “psrip” options”.

-h

Display help file.

6.6.1 Output file formats

The default raster image format is TIFF. To use a different format specify the -o RasterImageType option with one of the following supported formats:

`TIFF`	for TIFF image format
`JPEG`	for JPEG image format
`JP2`	(4 chars!) for JPEG 2000 image format
`8BPS`	for Adobe Photoshop format
`PNGf`	for PNG image format (RGB and Grayscale only)
`PICT`	for Apple PICT image format (RGB and Grayscale only)
`..CT`	for Scitex CT format

6.6.2 Attributes for “psrip” options

Attributes specify details of the used image format. Attributes are entered as command line options using the syntax (additional attributes are delimited by commas):

psrip -o Attributes=<attributes>=<value>
(deprecated but possible for compatibility reasons): psrip -a <key>=<value>

Baseline <boolean:FALSE>

(JPEG only) Saves JPEG images per default in progressive method. If this option is set to TRUE, JPEG images are saved as baseline JPEGs instead.

DctMethod <uint32:0>

(JPEG only) Use slow, fast or precise DCT (Discrete Cosine Transformation). Values are 0, 1 or 2. The default is 0.

TileWidth <uint32:256>

(JPEG 2000 only) Specifies the horizontal size of JPEG 2000 tiles. A JPEG 2000 image file consists of juxtaposed tiles. If the value specified is 0, the whole image merely consists of one tile.

TileHeight <uint32:256>

(JPEG 2000 only) Specifies the vertical size of JPEG 2000 tiles. A JPEG 2000 image file consists of juxtaposed tiles. If the value specified is 0, the whole image merely consists of one tile.

Note:: Partitioning a JPEG 2000 in tiles accelerates encoding and decoding significantly and minimizes the amount of required memory during this time. The default value 256 makes a good compromise between speed and memory requirement.

Quality (JPEG only!) <uint32:75>: Create poor … high quality JPEG image (1 … 100).
Quality (JPEG 2000 only!) <uint32:0>: Specifies the image quality of a JPEG 2000 image in relation to the uncompressed high-resolution original. The values range from 1…100. Specifying “0" means lossless.

6.6.3 Examples

Example:

(Convert a PostScript page)

psrip -o PrintColor=Grayscale -p 10,15 -o RasterImageType="JP2 "
      -i example.ps example

Prints a PostScript job onto a 10x15 inch Grayscale page and writes the result into a JPEG 2000 file (“example.1.jp2”).

Example:

(Convert a vector EPS image to the bounding box size)

psrip -o RasterImagetype=JPEG -i example.eps example

Converts a vector EPS file to a JPEG file. Since no page formats or sizes are specified, the image is converted to the bounding box size.

6.7 pdfresolve

The “pdfresolve” program allows replacing OPI images in PDF documents. In addition, “pdfresolve” preserves transparencies, that have been applied to layout images, in the OPI image replacement process. A complete description can be found in the HELIOS PDF HandShake manual.

HELIOS Manuals October 14, 2021