|
|
|
|
|
HELIOS ImageServer User manual |
||||
Fig. 35 again lists all tasks that are related to ImageServer. 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.
ImageServer 2.5 is composed of many individual UNIX-based programs, e.g. "opisrv", "opitouch", "layout", "oiinfo", "oiimginfo", "oictable", "hirespath". In addition,
it also makes use of the EtherShare modules "papsrv" and "psresolve" 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 have especially been 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" or the "psresolve" 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.3 "OPI server settings" and 8 "ImageServer preferences and notification features".
Note: The HELIOS CD-ROM contains the "imageconv" script (in sample-images/template-images%0), as well as various sample images.
Usually, layout files will be generated automatically by the ImageServer and new layouting parameters must be set using the EtherShare Admin program on any Macintosh 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.
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 EtherShare Admin dialogs are described with the note "Compare EtherShare Admin!".
Independent of whether you call the "layout" program for a set of files or use it to poll permanently in the background, you may use the options described below. The type and the default value are shown in angle brackets just before the description. The following types are used:
Lets you specify a comma-separated list of attribute key=value pairs (see also option Attributes below).
Set destination directory for layout file generation. May only be used for manual (not for automatic "polling") mode. This option creates all layouts in the indicated directory. This option is mostly needed when the high-resolution files reside on a read-only medium e.g. a CD-ROM.
When using the -l option, one or more files to convert, as well as a destination file (if converting a single file) or directory (if converting several files) must be specified with an absolute path.
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:
When using the -l option together with the -p option, a destination directory must be specified with an absolute path.
The image type of the destination files is given by specifying the destination as a complete "OpenImage" file specification.
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".
Important: The following six options are supported for backward compatibility with previous ImageServer (then called "EtherShare OPI") versions only; 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.
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 destination layout 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>.
Do not consider PrintResolution option (see below); layout file will inherit the resolution of the high-resolution image.
Defines 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 5 below. Please note that some color spaces cannot be applied to each file format.
Defines color space used for screen preview 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 5 below. Please note that some color spaces cannot be applied to each file format.
Defines compression mode used to generate printable part of layout file using a string from Table 6. Please note that some compression modes cannot be applied to each file format.
Defines compression mode used to generate screen preview of layout file using a string from Table 6. Please note that some compression modes cannot be applied to each file format.
Defines compression quality of layout files using lossy compression methods (e.g. "JPEG") in the range of:
Create the best layouts possible. Otherwise (FALSE), the first part of high-resolution image that matches defined layout resolution is used (high quality setting uses a bilinear resolution converter, low quality setting uses the "nearest neighbor" algorithm).
Defines Macintosh file creator used to create layout (only applicable to EtherShare volumes; 8BIM defines Adobe Photoshop).
By specifying this parameter all layout images will be TIFF files even if there is no need to create a TIFF file from a raster-based high-resolution original image.
By specifying this parameter all layout images will be EPSF files even if there is no need to create an EPSF file from a raster-based high-resolution original image.
Usually, if the high-resolution file uses raster format and does not include any mask, the resulting layout file will use a raster format too, otherwise - if the high-resolution image is an EPSF file - EPSF will also be used for the layout file. The used layout file format can be overridden using this option. You may use any string defined for the file type member (e.g. "JPEG").
Specifies the file type by means of the file extension when generating layouts from raster-based images.
Defines suffix used for created layout when the high-resolution file uses raster format and has the registered suffix.
Defines file type which is used to select the manager that creates layout files. You may use any string defined for the file type member here.
Defines suffix used for created layouts when the high-resolution file uses EPSF format and has the 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.
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 four 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 whether the layout process may use PostScript level 2 features (e.g. whether EPSF may include JPEG compressed data). Applies to EPSF layout files only.
Defines that image data may be stored using 8bit values (otherwise 7bit 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 the created layouts have to be usable on all supported platforms (e.g. all relevant data are stored in the data fork). If the high-resolution file has a resource, the layout file may have a resource too, when stored on 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.
Defines whether a resource fork should be created or not (see also CrossPlatformLayout option above).
Include profile in layout as value (copy) instead of a reference. Only applicable if UseProfile option is set.
A generated layout/picture will not contain any profile even if a profile was specified for the generation of the layout/picture. This option is useful if the generated layout/picture is small while the specified profile was large.
When creating layout 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 layout. Each string has the format <color space>=<Pathname> and defines the ICC-profile path name for the given color space.
Causes the creation of EPSF layout images if a high-resolution raster image contains extra colors like spot colors. This allows placement of the layout file in most DTP applications.
Lets the program generate DCS1 or DCS2 EPSF layout images if the raster-based high-resolution images include colors other than Black&White or Grayscale.
Lets EPSF layout images of DCS1 or DCS2 high-resolution images keep the DCS structure. Changing the option to FALSE will lead to simple EPSF layout files.
Forces layout images to always contain only the default inks of the layout color space. Spot colors defined in a high-resolution image will be converted into the appropriate values of the layout color space.
Defines the names and order of the color components when using Multichannel ICC profiles (5 or more channels). This option has to be specified if converting to the "Multi" color space. 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.
Forces ICC color matching while creating layout images even if no color matching would be applied by the "layout" default behavior.
Forces the layout 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 layout image have the same file format.
Switches the "layout" program into a fast layout mode. Using this mode will stop ICC color matching and define a fast picking algorithm for downsampling.
LayoutComment <string:"HELIOS ImageServer 2.5.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.
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.
Causes that an existing clipping path is used to provide transparency when creating a layout image. See 3.3.3 "Clipping paths" and 5.3 "Defining folder specific OPI settings" for a description.
Causes that 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 the user to define the size of their layouts in pixels either in x or y direction. The layouts always maintain their ratio. Layout guarantees that the resulting layouts will always be smaller or equal these sizes. If the use of xPix would mean that a given yPix value cannot be maintained, yPix will control the layout image dimensions and vice-versa.
Allows upward scaling so that the layout image may have a resolution greater 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!
Note: The following 9 options can only be used with the -l option (convert mode):
Note: A number between 0.0 and 1.0 specifies a per cent value. A number > 1.0 specifies a pixel value.
The attributes are entered as command line options using the layout -o Attributes=<attributes>=<value> syntax. Additional attributes are delimited by comma characters.
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.
Normally 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.
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.
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.
If you want to induce the generation of layouts for a specific folder (e.g. "testimgs") manually without changing any preferences or defaults you may just call the "layout" program as shown below:
You do not need the -o statement as long as you do not want to change any parameters, -v may be used to display the progress of layout generation.
If you want to create from a TIFF-CMYK high-resolution image without a clipping path a JPEG-RGB layout 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 have to change the PrintColor parameter because the default for PrintColor is CMYK. Furthermore, you have to use the RasterImageType option to create a JPEG layout file. The complete command line is given below:
# /usr/local/helios/bin/layout -v
-o PrintColor=RGB -o RasterImageType=JPEG
/opitest/images/testimgs/cmyktif.tif
The "imageconv" script which uses many of the layout conversion features can be found on the HELIOS CD-ROM in the sample-images/template-images%0 folder.
The "template-images%0" directory contains about 70 MB of sample images and the "imageconv" shell 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 GB of hard disk space.
Note: The "imageconv" script will run - depending on the used server - about 30 minutes or longer.
The "opitouch" command can be used to create OPI-layout files from high-resolution images which can be done with the "layout" command, as well. The benefit of "opitouch" is that jobs are processed by "opisrv" and that it uses the global OPI-parameters and OPI folder options for layout generation. This is the same as saving images from a Macintosh or Windows client using EtherShare and PCShare.
"opitouch" is the UNIX version of the Macintosh program "touch" allowing virtual touching of image files without modifying the high-resolution file date or time, while causing automatic OPI layout generation. This program is a stand-alone utility which is not bound to an EtherShare license or installation, and therefore can be used on any system of the architectures supported by HELIOS ImageServer. It allows touching single files, all files of a directory, or even a complete directory tree on the local or remote system. Since "opitouch" does not recognize the types of the files specified, touching a non-image file may cause system error messages and failure info layout files.
Allows you to select a remote host by name or its dotted decimal internet address. You may only gain access to ImageServer systems with appropriate IP access control setup done with the EtherShare Admin program using the IP Access dialog.
Allows you to select the OPI event service port of the "opisrv" by name or numeric port number. Specifying a service port that is served by anything other than "opisrv", may cause "opitouch" to hang.
Unless otherwise specified, "opitouch" assumes that the path name arguments refer to plain files. In this case directories will be ignored by the contacted "opisrv".
Requires all path names to be directories. In this case, all plain files contained in the specified directories will be touched. Subdirectories will be skipped.
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.
Important: All files and directories have to be specified with their absolute path names beginning with a "/" character. The path names must NOT end with a "/" character!
The "hirespath" program resolves an OPI layout file name to the appropriate high-resolution UNIX path name. It also maps client (UNIX, Mac or PC) file names to UNIX path names. "hirespath" receives the low-resolution file name or reference as a command line argument or on "stdin". It prints the file name or reference of the high-resolution image on "stdout". It recognizes all known OPI printer interface parameters. "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.
The name of a specific printer queue. "hirespath" will then access the OPI parameters for that printer queue.
A UNIX directory path name which precedes the
<clientName>. If this parameter is supplied, <clientName> has to be a file name without directory specification. <pathprefix> must NOT end with a "/" character!
File name or reference of the low-resolution image. This name is taken from the OPI comment without any modification. It can be in the format of the client's file system (i.e. Mac, PC, UNIX, etc.). The file name is quoted to allow for spaces. If <loResRef> is omitted, "hirespath" will read <loResRef> from "stdin".
File name of a UNIX, Mac, or PC file. If <clientName> is omitted, "hirespath" will read <clientName> from "stdin".
"hirespath" returns the name or reference on "stdout", and returns an integer to indicate the result of the operation:
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.
<code> is one of the codes listed below, <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.
0 Success; <loResRef> was successfully resolved into <hiResRef>, and the high-resolution file is accessible. <hiResRef> is printed on "stdout".
1 Error; an (UNIX) 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".
If the option -j is specified, "hirespath" instead will 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 list of <opiRef>.
1 Error; an (UNIX) error occurred. An explanatory error message is printed on "stderr". Nothing is printed on "stdout".
If the option -m is specified, "hirespath" instead will map a client file name <clientName> to a UNIX path name
<UNIXPath> without OPI resolving. This works for UNIX, Mac, and PC client file names. There are a few restrictions:
0 Success; <clientName> was successful mapped into <UNIXPath>, and the file is accessible. <UNIXPath> is printed on "stdout".
1 Error; An (UNIX) error occurred. An explanatory error message is printed on "stderr". Nothing is printed on "stdout".
2 Error; <clientName> cannot be mapped into
<UNIXPath> or <UNIXPath> is not accessible. If the theoretical <UNIXPath> is reasonable, it is printed on "stdout".
The following example shows the command you have to enter if you want the program to return the UNIX path name of a high-resolution image for a given layout image in a particular print job:
The "oiinfo" program allows you to view a list of all "OpenImage" plug-ins that are installed and available with ImageServer 2.5. The program, by default, searches the directory "HELIOSDIR/lib/OpenImage/Plug-ins". Every file in this directory will be checked to find out whether it is a correct plug-in and - if so - what type of plug-in it is.
Found Plugin at /usr/local/helios/lib/OpenImage
/Plug-ins/opibase.so:
Magic is HeliosOpenImage.
Version is 1.0.
Module is HeliosBase
Module description is
"HELIOS ImageServer base functionality".
Module version is 2.8.
Furthermore, for every correct plug-in, the "oiinfo" program lists all included "OpenImage" managers.
Modtoc:
Sectiontype 1: HeliosUnixFs (Helios Unix Fs mgrs)
Sectiontype 1: HeliosNativeFspec (Helios Native
Fspec mgrs)
Sectiontype 1: HeliosESFspec (Helios EtherShare
Fspec mgrs)
Sectiontype 1: HeliosPCSFspec (Helios PCShare
Fspec mgrs)
Sectiontype 1: HeliosAdjust (Helios Adjust
mgrs)
Sectiontype 1: HeliosTiff (Helios TIFF mgrs)
Sectiontype 1: HeliosJPEG (Helios JPEG mgrs)
Sectiontype 1: HeliosEPSF (Helios EPSF mgrs)
Sectiontype 1: HeliosScitexCT (Helios Scitex CT
mgrs)
Sectiontype 1: HeliosAdobePhotoShop (Helios
Adobe PhotoShop mgrs)
Sectiontype 1: HeliosPICT (Helios PICT mgrs)
Sectiontype 1: HeliosMacintoshIcons (Helios
Macintosh Icon mgrs)
Sectiontype 1: HeliosAdobePath (Helios Adobe
Path mgrs)
Sectiontype 1: HeliosColor (Helios simple
Color mgrs)
After that, you will get a list of "OpenImage"-registered managers. This specific list provides information about which managers are available for use.
Manager type : Color
Predicate : 17530
Version : 1
Quality : 127
Registered key is
Scope : (00269) HeliosColorAll
Filesystem : (00000) *
Filespec : (00000) *
Filecreator : (00000) *
Filetype : (00000) *
Filetype Extension : (00271) RGB
Manager supports raster images.
Manager supports the following capabilities:
Capability 1:
Supports colorspace mapping:
Maps colorspace from RGB to Bilevel.
Supports image valuating.
Supports inkset change:
Accepts imagedata with any inkset.
Produces imagedata with any inkset.
Supports bpc change:
Accepts imagedata with 8 bpc.
Produces imagedata with 1 bpc.
...
Capability 4:
Supports colorspace mapping:
Maps colorspace from RGB to CMYK.
Supports image valuating.
Supports inkset change:
Accepts imagedata with any inkset.
Produces imagedata with any inkset.
Supports bpc change:
Accepts imagedata with 8 bpc.
Produces imagedata with 8 bpc.
There are three different possible parameters, they are optional:
oiimginfo [-v VerboseLevel] [-e]
[-o prefix_for_export] files
The higher the verbose level, the more detailed the information you will receive. Default is 0. With level 9 you request all available image data. This level should only be used after careful consideration.
With this option, all objects that can be found in an image file are exported to files. Raster data are exported "as is". The names of the export files are created using the prefix that is entered with the -o option, followed by the object ID, the numeric object type, quality, and access method.
If you want to check a specific image file (e.g. "test.tif") to find out whether this image is already tagged with an image profile, you may proceed as follows:
Verbose Level: 1 Info for test.tif:
Creator: 8BIM
File type: TIFF (Tagged Image File
Format)
Extension: 3.0
Reference ID: (None)
Fstype: (None)
Fspec: (None)
Creator: 8BIM
Type: TIFF
Extension: 3.0
File contains 4 objects:
Object 1:
Id: 1
Type: Image
Quality: Print
Main access method: Raster
Image type: TIFF
Type extension: 3.0
Reference ID: (None)
Object may be handled by any image manager
by using binary access of region 1 from L-File 1 (see below) Image manager 'HeliosTiff' used with registered key:
Fstype: unix
Fspec: native
Creator: (None)
Type: (None)
Extension: (None)
GFX information of this object:
Colorspace: CMYK
Colorspace dependent info:
Dot range: [255 0]
Compression: None
Minimum is low color value
Image data is organized interleaved
Image data must be accessed with all channels
simultaneously
Image data may be accessed in any order
Image data must be accessed as
complete scanlines or
tiles Rows: 394
Columns: 394
Depth: 1
X resolution: 200.000000 dpi
Y resolution: 200.000000 dpi
Size per unit: 1576 bytes
Bits per channel: 8
Number of channels: 4
There are 4 inks defined:
Ink 0:
Name: Process `Cyan'
Opacity: 100.00 percent
Reference ID: (None)
Ink 1:
Name: Process `Magenta'
Opacity: 100.00 percent
Reference ID: (None)
Ink 2:
Name: Process `Yellow'
Opacity: 100.00 percent
Reference ID: (None)
Ink 3:
Name: Process `Black'
Opacity: 100.00 percent
Reference ID: (None)
There is one ICC profile connected:
ICC profile 1:
Profile pathname: ICC-Profiles:Printer:HELIOS:
Euro 2.6 UCR-370
Profile creation: 19960627111511
Object 2:
Id: 1
Type: Mask
Quality: Print
Main access method: AdobeMask
Image type: TIFF
Type extension: (None)
Reference ID: (None)
.
.
.
| © 2002 HELIOS Software GmbH |
|
|
|
|
|
