HELIOS ImageServer UB User manual |
||||
This chapter describes some modules of our software that are only accessible when working on the UNIX server. 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 "Script Server").
ImageServer is composed of many individual UNIX-based programs "opisrv", "opitouch", "layout", "oiimginfo", "oictable", "hirespath", etc.. In addition, it also makes use of the modules "papsrv" (see EtherShare manual) and "psresolve" (see Base manual) and different printer interface programs ("papif", "tcpif", and others). Some of the above mentioned programs are described in the following chapters.
You may use them for setting specific parameters manually. This may be useful because some of these parameters were especially designed to deal with application-inherent incompatibilities.
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 web site, section "Support" > "Developer specifications", and is meant for third-party developers only.
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 data base. In case the preference data base does not contain an entry for this parameter, the parameter default will be used. Otherwise, the entry in the preference data base is valid. For changing entries in the preference data base, see 4.2 "ImageServer settings" and 8 "Preferences and notification features".
- Layout file generation (6.2.3 "Layout file generation")
- Image conversion (6.2.7 "Image conversion")
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. Macintosh Finder comments as well as XMP and IPTC meta data are preserved by both generated layouts and converted images.
- Tagging of ICC profiles, path information and XMP meta data (6.2.10 "Tagging ICC profiles, path information, and meta data to images")
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 Specify TRUE or FALSE
Determines additional resources, which will be read by "OpenImage" plug-ins. If the string contains PATH, IPTC or XMP, the named additional resource will be read. If no resources should be preserved, specify none.
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 ProfilePaths <string list: (RGB="ICC-Profiles:Scanner:HELIOS:CCIR-EBU-RGB",CMYK="ICC-Profiles:Printer:HELIOS:Euro 2.6 UCR-370")>
Defines RGB or 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 name>.
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.
When creating output files which are not yet tagged with ICC profiles, this parameter can be set for temporarily attaching a profile to the image while generating the file. Each string has the format <color space>=<Pathname> and defines the ICC-profile path name for the given color space.
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.
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.
If set to TRUE, the "layout" program switches into a fast layout mode. Using this mode will stop ICC color matching and define a fast picking algorithm for downsampling.
Important: ICC color matching will be inactive, even with this option NOT specified, if the OPI preference Fast (see 8.1.2 "Global OPI preferences") is set to TRUE, which corresponds to the HELIOS Admin setting Standard in the Layout Quality pull-down menu!
This option should only be set to TRUE if you print to a PostScript 3 device with in-RIP separation. The PostScript output of PDF original files will be optimized to use the PostScript 3/DeviceN features. 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.
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.
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.
Forces the output image to be compressed the same way the high-resolution file is compressed. This option will only be recognized if the high-resolution file and the output image have the same file format.
Defines mappings from application or localization dependent color names to the names used in "OpenImage". String format is <ColorName>=<ColornameAlias>.
Defines a signature filter configuration file. See "HELIOS OpenImage Software Developer Kit" for details.
Controls resource usage of main memory. The specified value limits the maximum use of main memory in kilobytes. Zero means no limits.
Usually, layout files will be generated automatically by ImageServer, and new layouting parameters must 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 UNIX "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:
If you want the "layout" program to scan permanently for high-resolution files in a special directory, use the call:
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.
In the following, we list the parameters that may be used with "layout" and then - at the end of this chapter - give you some examples that may be used for specific workflows.
Note: Parameters that can also be specified in one of the HELIOS Admin dialogs are described with the note "Compare HELIOS Admin!".
Allows you to specify a comma-separated list of attribute key=value pairs (see 6.2.5 "Attributes for "layout" options").
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.
Do not consider PrintResolution (see below); the layout file will inherit the resolution of the high-resolution image.
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 7 below. Please note that some color spaces cannot be applied to certain file formats.
Defines the compression mode used to generate the printable part of the layout file using a string from Table 8. Please note that some compression modes cannot be applied to certain file formats.
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 7 below. Please note that some color spaces cannot be applied to certain file formats.
Defines the compression quality of layout files using lossy compression methods (e.g. "JPEG") in the range of:
Defines the compression mode used to generate the screen preview of the layout file using a string from Table 8. Note that some compression modes cannot be applied to certain file formats.
Create the best layout quality possible. Otherwise (FALSE), the first part of the high-resolution 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).
Defines Macintosh file creator used for layout creation (The default value "8BIM" defines Adobe Photoshop).
By specifying this parameter, all layout images will be created in raster format (provided that ForceEpsLayout is not specified!), if the original high-resolution image contains a raster image of the quality Print, Proof or Screen.
By specifying this parameter all layout images will be created in EPSF format (provided that ForceRasterLayout is not specified!), if the original high-resolution image contains an EPSF image.
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 in 3 "Before getting started".
Specifies the file type by means of the file extension when generating layouts from raster-based images.
Defines the suffix used for the created layout when the high-resolution file uses raster format and has the registered suffix.
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 in 3 "Before getting started".
Defines the suffix used for layout creation if the high-resolution file uses EPSF format and has a registered suffix.
This parameter controls if a known suffix will be replaced by the type-dependent suffix while creating the layout file name. This parameter is ignored if layouting is done for PCs or on PCShare volumes. For example, a high-resolution TIFF file "Image.tif" normally leads to the layout file name "Image.eps" in case an EPSF layout file is generated. If the option ReplaceSuffix is set to FALSE on the command line of the layout program, the suffix will stay ".tif" even if the layout file type is EPSF.
Defines whether EPSF high-resolution files without color space specification should be processed or skipped.
Important: Please note that the following three options can only be used if the created layout file is an EPSF file.
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 to EPSF layout files only.
If set to FALSE, "layout" creates a screen preview of the image but no printable layout. Applies only to EPSF layout files.
Defines that image data may be stored using 8-bit values (otherwise 7-bit hex is used). Applies to EPSF layout files only.
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.
Defines whether a standard default layout (indicating the error) should be created in case of layout generation failure.
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 may have a resource too when stored in a Macintosh volume. If the high-resolution file does not have a resource, the layout generation depends on the CrossPlatformFiles option described below. In the DOS name space under PCShare, a resource will only be created if the volume "root" directory (mount point) has an underlying ".rsrc" directory.
-o LayoutComment <string:"HELIOS ImageServer 3.0.0 layout of %T file \"%f\", size %k kBytes, created by %C" >
Overrides the default comment field for layout images. The parameter is a string which will be placed in the comment section of a Macintosh 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 characters):
%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.
Sets the label color of a layout file. An integer number between 1 and 8 reflects the Macintosh Finder label colors, 0 turns this option off.
When TRUE, causes an existing clipping path to be ignored when creating a layout image. See 3.3.3 "Image paths and clipping paths" and 5.3 "Defining folder specific OPI settings" for a description.
Specifies whether additional channels (e.g. spot colors) are used when creating a layout image. See 3.3.5 "Additional channels in bitmap images" and 5.3 "Defining folder specific OPI settings" for a description.
Allows upward scaling so that the layout image may have a resolution higher than the resolution of the original image.
With this option set to TRUE generated layout files will have the Macintosh Finder flag Locked turned on. Before setting this flag to TRUE make sure that the DTP application you use can handle locked layout files!
Important: The following five options are only supported for backward compatibility with previous ImageServer versions; please do not use these options for new installations or configurations!
Defines valid DCS suffixes. You may specify any number of characters here. These characters are handled case-insensitive.
Attributes are only applicable to specific file types. They are entered as command line options using the syntax:
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.
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.
Specifies the image quality of a JPEG 2000 image in relation to the uncompressed high-resolution original. The values range from 1-100, or are one of the following named constants:
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 JP2 compression has only 50% the size of an uncompressed image, a Quality value between 50% and 100% produces no visible differences.
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.
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.
This attribute lets you specify a certain page of a PDF, XPV or TIFF document for image conversion or creating layouts.
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.2.8 "Options for image conversion").