Asset Processor modules enable Cumulus to perform processes on cataloged assets, e.g. to convert them.
DCS File Support
The DCS File Support module enables Cumulus to recognize CMYK Desktop Color Separation files so that it can effectively catalog and manage multiple-file DCS assets. This module supports DCS version 1.0. These DCS assets consist of one main file (which may contain a preview image) and the four standard color separation files.
When cataloging a DCS asset, this module creates a record for the main file only. It is important to be aware of this when viewing the Asset Information window, as the information such as file size, etc. only pertain to the main file. Although only one file is cataloged, Cumulus still manages all five. For example, if you move or copy the cataloged DCS asset with Cumulus, all five DCS files will be moved or copied. (No properties to be defined.)
Generic Asset Processor (optional)
Provided by the Cumulus External Tool Connector Option. Enables Cumulus to call external applications from within Asset Actions. It can be used for processing, packaging, and delivering tasks.
For each platform you specify the commands to be executed. (The same parameters have to be defined for the External Application used by the Generic Filter for thumbnail generation.)
External Tool Parameters for the Generic Asset Processor
The following variables have to be used in the command line for the input and output files: $INPUT and $OUTPUT. They will be replaced by Cumulus before executing the command line depending on the module task in the following manner:
Asset Processor Task
$INPUT
$OUTPUT
Processing
Quoted path of source asset.
Quoted path of destination asset.
Packaging
Space separated list of quoted paths of source assets.
Quoted path of destination asset.
Delivering
Quoted path of source asset.
- (will be deleted)
In case the application to be called expects a special file extension, you can specify the extension directly behind the variable:
$OUTPUT.jpg "C:\Temp\CumulusTemporary.jpg"
In the same manner you can specify suffixes to append at the destination name:
Generate compressed tar file with specified destination file name:
tar -czf $OUTPUT=FromProcessor.tgz $INPUT
MS PowerPoint Asset Processor
The MS PowerPoint Asset Processor enables the user to create PowerPoint presentations in PowerPoint 97-2003 format from selected PowerPoint assets (slides, presentations), image assets and previews of other asset formats within Cumulus. For more information on how to use the processor, see “Creating Presentations” .
Office Open XML Presentation Asset Processor
The Office Open XML Presentation Asset Processor enables the user to create presentations in Office PowerPoint 2007 format from selected presentations (slides, presentations), image assets and previews of other asset formats within Cumulus. For more information on how to use the processor, see “Creating Presentations” .
OPI System Support
The OPI System Support module enables Cumulus to be OPI-aware. The Open Prepress Interface (OPI) is a technology that allows placing low resolution versions of image files into page layouts and letting an OPI print spooler automatically replace them with the high resolution versions of the files for printing. If the OPI System Support module is activated, Cumulus will be able to recognize OPI files and carry through the correct handling of high and low resolution versions of OPI files.
The module is able to read path name information and lets Cumulus manage both high resolution and low resolution files from OPI systems like Imation Color Central™, Nine Bits PrintDesk, 4-Sight OPI™ , HELIOS EtherShare OPI, and HELIOS Image Server.
Cumulus is also OPI-compatible with many other OPI systems that use EPSF or TIFF format files as their low resolution file, like Scitex® APR. With these OPI systems, low resolution files are handled as expected, but the path to the high resolution file might not be automatically recognized.
The OPI System Support module is used for asset access in two different ways:
• If used with a Cumulus Action, it provides access to OPI assets as set in the module’s properties within the Cumulus Action. There you can define whether the action will access the high resolution or the low resolution file when being performed - regardless of how the module is set up for the Asset Handling Set used with the action.
• If used along with an Asset Handling Set (e.g. for cataloging, previewing or copying OPI assets), it provides access to OPI assets as set in the module’s properties for the Asset Handling Set. How to set up these properties is described below.
The module offers special support for the following versions of HELIOS and Imation OPI systems
• HELIOS EtherShare OPI version 1.0 up to 2.1
• HELIOS ImageServer 2.5
• HELIOS ImageServer UB
• Imation Color Central 2.1 up to 2.5
For both OPI systems you can define additional properties.
If you select the OPI Support entry in the list of Asset Processor modules and then select the Properties button, the OPI Support Setup window opens.
The OPI System Support Setup window has three sections:
• General
• HELIOS
• Imation
In the section General you can set up the module:
• to run in silent mode when accessing an OPI asset or not. If Silent OPI File Access is not activated, you will be prompted to choose a version when accessing an OPI asset. If Silent OPI File Access is activated, Cumulus uses the version chosen below when accessing an OPI asset (e.g. for previewing or copying).
• to use either the low resolution file or the high resolution file when in silent mode or when dragging and dropping an OPI asset.
Normally you choose to use the low resolution file. The chosen file version is also used in silent mode. If silent mode is not activated, you will be prompted to choose a version when accessing an OPI asset. Regardless of whether silent mode is activated or not, when you drag and drop assets you will never be prompted to choose the version – with one exception which refers to OS X only . Under OS X special functions for dragging and dropping OPI files are provided. These are as follows:
• Under OS X, if Silent OPI File Access is activated, you must use the ALT key when dragging to have the version dropped that is defined for silent mode.
• The exception to the rule that you will never be prompted to choose the version when you drag and drop assets: Under OS X, if Silent OPI File Access is not activated and you did not use the ALT key for dragging, you will be prompted to choose the version when dropping the asset into the Finder. If you have selected multiple assets, you will be prompted once and the chosen version will be taken for all.
• Under OS X you have an additional option to choose between high and low resolution files when dragging and dropping assets into other applications: keyboard shortcuts. To place the high resolution file press ALT+H and then start dragging. To place the low resolution file press ALT+L and then start dragging.
TIP: Drag& Drop of High Resolution Files If you have chosen to use the low resolution files but in contrary to your normal workflow you want to drag & drop the high resolution files, you can proceed as follows: Select the records representing the assets and select the Show Location menu command ( Apple / CTRL + R). This command locates the selected records’ assets and displays them in OS X Finder or Windows Explorer. Now you can select the desired asset version in OS X Finder or Windows Explorer and drag and drop it from there.
For HELIOS OPI system it is recommended to catalog the high resolution file as the information on this file will then be available with the catalog.
For all OPI systems (except HELIOS) it is recommended to catalog the low resolution file as only the low resolution file leads to the high resolution file – and not vice versa. If you have cataloged the low resolution files, do not enable Silent OPI File Access along with the option High Resolution File for these OPI systems since this combination will not work.
In the section HELIOS you can set up special properties for HELIOS EtherShare OPI and HELIOS Image Server. Only if the option HELIOS EtherShare OPI Aware is activated will Cumulus catalog either the low resolution layout file or the high resolution file. Although the module recognizes layout files generated in the layouts folder it also supports a name extension for layout files. In the field Layout file name extension (default: .lay) you specify the name extension to identify OPI layout files. You should always specify the same name extension that is used by the HELIOS EtherShare OPI system. A file in the same folder as the high resolution file that has this name extension will be treated as the layout file for this high resolution file. The following two options are important to avoid duplication when cataloging a whole folder. They can be used to create only one record for a pair of high- and low resolution files when cataloging. The option Catalog High Resolution Files Only (default) allows you to catalog only high resolution files. This is useful to get the information (size, resolution) about those files into the Cumulus catalog. By choosing the option Catalog Layout Files Only you can build a catalog of only the layout files.
In the section Imation you can set up special properties for Imation Color Central. Only if the option Imation Color Central Aware is activated, will Cumulus read the IPTC information from the high resolution file while cataloging the sample file.
NOTE: This option can only work properly when the high resolution file and the sample file reside in the same folder.
If the option Add Category for Sample Files is activated, Cumulus will assign every ColorCentral sample file to a special category while cataloging. The category name can be specified in the field below this option (default: Imation Color Central). This option is useful when you catalog both the high resolution and the sample file of an image and you want to distinguish between the corresponding records.
PDF Page Merge AssetProcessor
The PDF Page Merge Asset Processor enables the user to create PDF documents from selected PDF page assets and image assets within Cumulus. (No properties to be defined.)
Pixel Image Converter
The Pixel Image Converter enables Cumulus to convert any cataloged pixel image into the different formats on the fly: e.g. JPEG, TIFF, BMP, GIF, ScitexCT, PNG, PCX, and PDF. (No properties to be defined.) For more information on how to use the Pixel Image Converter, see “Converting Image Assets” .
Pixel Image Crop Processor
The Pixel Image Crop Processor enables Cumulus to crop any cataloged pixel image on the fly, e.g. JPEG, TIFF, BMP, GIF, PNG, etc., and to resize the final output of the cropped section. The resulting image will be saved as a new file. For more information on how to use the Pixel Image Crop Processor, see “Cropping Image Assets” .
Pixel Image Crop Template Processor
The Pixel Image Crop Template Processor enables Cumulus to crop any cataloged pixel image, e.g. JPEG, TIFF, BMP, GIF, PNG, etc., and to resize the final output, by means of predefined templates. The resulting image will be saved as a new file. For more information on how to use the Pixel Image Crop Template Processor, see “Cropping Image Assets with Templates” .
QXP Server AssetProcessor (optional)
The QXP Server Asset Processor converts QXP documents, layouts or pages to PDF using a QXP Server installed in the network. (No properties to be defined.) For more information on the parameters available for the conversion, see the QXP Server documentation.
Rename AssetProcessor
The Rename AssetProcessor renames assets according to a predefined rule within a Cumulus Action. It requires that at least one rule has been defined and saved as a renaming set using the Rename Asset dialog (Menu Asset > Rename To > Batch; for more information on how to configure a renaming set see The Rename Assets Dialog. The desired set must be selected in the module’s properties.
Thumbnail Provider
The Thumbnail Provider is used with Cumulus Actions only. It provides the thumbnail stored in the asset’s record for a Cumulus Action. Using the thumbnail that is stored in the record might be faster than having the asset converted, e.g with the Pixel Image Converter. (No properties to be defined.)
Watermark AssetProcessor
The Watermark AssetProcessor enables you to embed digital watermarks into the following pixel image formats: JPEG, TIFF, BMP, GIF, PNG, and PCX. You can embed visible text and image watermarks. For more information on the processor and on how to use it, see “Watermarking Assets” .
XSL Metadata Processor
The XSL Metadata Processor enables Cumulus to create metadata files based on XSL transformations. The XSL transformation is applied to a file that contains all metadata from the catalog for a processed record. Any XSLT style sheet can be chosen for the transformation. The output file is named the same as the asset with a chosen extension added and is saved at a chosen target location. (No properties to be defined.)
NOTE: Sequence of AssetProcessors in Asset Actions The XML Metadata Processor should be at the end of the list of processors for processing in the Asset Action – otherwise no output will be written.
NOTE: Style Sheet Saved With Asset Actions The XSLT style sheet is saved with an Asset Action. If you update such a style sheet, you need to update the Asset Action configuration as well by choosing the updated style sheet again.
ZIP AssetProcessor
The ZIP AssetProcessor enables Cumulus to compress cataloged assets into Zip archives. (No properties to be defined.) For more information on how to use the ZIP AssetProcessor, see “Creating ZIP Archives” .