|
Matchprint One Bit TIFF Interface - Frequently Asked Questions
Contents
Introduction
General workflow
General OBTi
Installation
Setup
Operation
Troubleshooting
Introduction
What is the Matchprint One Bit TIFF Interface?
The Matchprint One Bit TIFF Interface (or OBTi) is a product that facilitates the printing of one bit TIFF files through the Matchprint Color RIP (or MPCR).
When will OBTi be available?
The Product is available from authorized KPG dealers.
Is this a Kodak Polychrome Graphics solution?
Yes, the One Bit TIFF Interface has been developed by KPG at our Oakdale facility.
Is this a halftone inkjet solution?
No, this is a ROOM solution that provides contone proofing of halftone files. OBTi offers several advantages not found in inkjet halftone solutions such as; superior line and text quality, improved color matching, no false moiré.
What is in the box?
OBTi is packaged in a DVD type case, included in the case is the dongle, CD and printed installation guide (translated into EFIGSJ).
What is on the CD?
The CD includes the OBTi installer, dongle security installer and also the TIFF test application. The CD will auto-run and the installer asks the customer to select their preferred language. Once the language is selected, the application and online documentation will be localized.
What is TIFFtest.exe?
TIFFtest.exe is a free application that can quickly check compatibility of one bit TIFF files with OBTi. TIFFtest.exe is on the OBTi CD and available for download from www.kpgraphics.com/TIFFtest.
What is the difference between a permanent version of OBTi and the trial version?
The trial version includes the same CD and installation guide as the permanent version. However, it contains a trial (yellow) dongle. The trial (yellow) dongle will expire after processing 120 separations (20x6 color jobs or 30x4 color jobs).
I have an expired trial dongle (yellow). Can I have it reactivated?
No, not at this time.
Back to top
General workflow
What are One Bit TIFFs?
A one bit TIFF file is a type of file used by printing industry workflows to create film, proofs, or plates. Saying that a file is one-bit means that all the pixel data in the file is either black or white, on or off. TIFF stands for tagged image file format. It is a typical format for one bit data to be saved in. One bit TIFFs are usually screened files when coming out of a workflow product.
What does RIP mean?
RIP stands for raster image processor. Raster image processor software will read data from a postscript or other image file and convert it into a bitmap. All continuous tone and vector data within the original file is converted to a collection of pixels. This collection of pixels can be in different formats, depending on the workflow product.
What is a ROOM workflow and how does it work?
Workflow products come in different varieties. ROOM (rip once, output many) is one of those varieties. A ROOM workflow is based on the idea of only having to interpret (rip) the original data once, and then being able to output that data to any number of devices. After interpreting the data and creating the bitmaps, the bitmaps can be trapped, imposed, converted to other file formats, or output on an imaging device. A benefit of a ROOM workflow is that because the original data is only interpreted once, there is little risk that proofs or film made from the bitmaps will be different than plates made from the bitmaps. A drawback of a ROOM workflow is that the workflow product (ie. Brisque) may be difficult to interface with other workflows or desktop systems.
Why would someone want to proof their one bit TIFFs?
In a ROOM workflow, it is important that proofs represent as close as possible the final printed piece. By proofing the same screened data that will appear on a plate, data integrity, image artifacts, content, imposition, color separation, color quality, etc. can be determined prior to exposing plates or running a press. The One Bit TIFF Interface provides the capability for the proofing of plate-destined files using an inkjet proofer.
You refer to a ROOM workflow but the data is being processed again isn't it?
No. OBTi does not remove the image screening, but instead manages the file for a lower resolution printer (compared to CTP device). The result being that this masks the original halftone, especially at higher linescreens. Some residual screening may be visible at lower screen rulings. This should not be confused with a true halftone.
What workflows can OBTi be integrated into?
OBTi can be integrated into any workflow that produces a TIFF that meets the standard specifications version 6. Some workflows direct drive their output devices. In this case, the workflow would need to be set up to output a TIFF file, which may or may not be possible. There exists a TIFFtest.exe utility that will read a TIFF file and indicate its compatibility with OBTi. That utility can be found on the install CD or on the KPG website at www.kpgraphics.com/tifftest.
Back to top
General OBTi
Does OBTi work with the Approval Open Front End (OFE)?
Not at this time, we are investigating compatibility with the Approval Open Front End and for possible inclusion it in a future release.
How does OBTi work?
OBTi runs as a Windows system service. It is always running as long as the computer is on. A user defines a series of folders, which OBTi uses to manage file conversion and transfer. The OBTi control panel is where the user configures the folder parameters. The control panel does not need to be opened for OBTi to operate. One bit TIFF files are placed in the input hot folder, OBTi recognizes the files, converts them to a lower-resolution file, combines the lower res files, and places an output file in the contone output folder.
How is the file color managed?
The OBTi allows Matchprint Color RIP to process the one bit TIFF file and apply color management using the KPG CFM and Matchprint Inkjet ICC profiles.
How long does it take to process a file?
Speed is dependant on the system specifications of the computers used, file sizes and software preferences and settings. OBTi offers the user 3 levels of image processing quality that allows the user to select the balance of speed and image quality that is appropriate. OBTi has an additional setting (number of concurrent processes) that allows the user to adjust the amount of system resources used to process files. Increasing the performance setting even just one increment makes OBTi much faster onhigh specification PCs.
Why is the output file of OBTi so much larger than the input one bit TIFFs combined?
One bit TIFFs typically have some sort of compression applied. Because of their nature, one bit TIFFs can be compressed very efficiently, resulting in very small files compared to uncompressed files. When OBTi processes the one bit TIFFs, it converts the files into a single, 32-bit (8-bits x CMYK) file. In a 32-bit color depth, the compression is less efficient. Therefore, the file size of the output file will always be larger than the sum of the sizes of the input files.
Why do files produced with OBTi seem to take longer to RIP in MPCR versus postscript from my desktop application?
The output of OBTi is usually at a higher resolution (600dpi or 720 dpi at contract quality) than the output of your desktop application (around 300dpi for 150lpi work). Doubling the resolution quadruples the file sizes and will increase the RIPping time, and the image quality. Also, the output of OBTi is all image data. Your desktop application’s output is usually some image data and some vector data. Image data generally takes more time to RIP than vector data, so the desktop application output will usually RIP faster than the higher resolution image output of OBTi.
Can OBTi handle spot colors?
Yes. OBTi can handle any number of spot colors. However, if your job will include spot colors, you will need to select the separated PS output file type option. Also, if processing files manually, the names of the spot colors should be added to the color name list. Last, make sure the color names match the names in the MPCR spot color table. If the names are different, MPCR will not recognize them as spot colors and it will convert to process.
Back to top
Installation
Do OBTi and MPCR need to be installed on the same server?
No, it is not essential to co-locate OBTi and MPCR on the same server. Whilst MPCR and OBTi are designed to work together on the same server, it is not essential that they are. A customer installing the applications on 2 different servers may well see an increase in productivity.
Does OBTi work with Windows NT?
No, OBTi is intended for use on Windows 2000. Refer to the system requirements. Microsoft is no longer shipping or supporting Windows NT.
What are the required minimum system specifications for OBTi?
A 1.0 GHz processor, 512 Mb of RAM, 60Gb of hard drive space, and Windows 2000. However, if you plan on running OBTi on the same computer as MPCR or you want to maximize system efficiency, we suggest using a dual 2.0 GHz or faster processor system. See the complete system specifications for more details.
Are there any hardware configurations to avoid?
Yes. Right now, the only known incompatibility is with ATI graphics cards. Depending on the driver you are using for the graphics card or the settings for the card, you may experience crashes of the computer. One option to alleviate the issue is to use driver version 5.0.2184.1 at any color depth or use version 5.0.2195.5012 but set the color depth at 256 colors. Another option is to disable the DirectDraw and Direct3D accellerations as well as all cursor and advanced drawing accellerations. This is a known problem with java code and the ATI drivers and is easy to research on the internet for further details.
Back to top
Setup
What are the hot folders OBTi uses, and who creates them?
The user should create three folders: an input hot folder, a contone output folder, and a processed TIFF folder. In the OBTi control panel, the hot folder specifications are directed to these three folders. OBTi will also automatically create a "b", "c", and an "OBTError" folder within the input hot folder. If a folder gets deleted, OBTi will automatically re-create it. The user should be careful in their hot folder specifications: System folders, desktop folders, network folders, and main drives should not, and in some cases can not be used as OBTi folders. This is because OBTi can be set to delete files in its folders. Choosing a system folder, for example, could cause the contents to be accidentally deleted, rendering the computer useless.
Why can't I use mapped network drives when I specify folder locations?
OBTi runs as a system level service. That means it is always running in the background. Even if you log-off of the desktop, OBTi is still running. Mapped network drives are user dependant and are not accessible when not logged on. So, OBTi would lose network access when you log-off. If you need to have cross-network sharing of files (and most likely you will), you should publish a shared volume from your OBTi computer and map it from the computer providing the one bit TIFFs.
How do I integrate OBTi in my workflow in order to automate file processing and movement?
In order to automate the file processing and movement in your workflow, the front-end workflow output (one bit TIFF files) should be directed to the same folder as an input hot folder of OBTi. The inkjet RIP queue should be directed to the contone output folder of OBTi. The plate or film imaging system input hot folder should be directed to the processed TIFF folder of OBTi. In this way, a set of one bit TIFFs created from the front-end workflow and accepted by OBTi. The output of OBTi is accepted by the inkjet RIP for proofing, and the original one bit TIFFs are sent to the film or plate imager.
How many concurrent processes should I set OBTi to use?
Usually 1 or 2 is sufficient. If you have a single processor computer, you may need to stay at 1. With a dual processor computer, raising the number of concurrent processes to 2 or higher will result in a sizeable processing time decrease.
When I select standard or contract quality, I have to choose a resolution. Would choosing 720dpi yield better output versus 600dpi?
You should choose the OBTi resolution that best matches the resolution of the printer you are using. HP and Canon printers typically run at multiples of 300dpi. For HP or Canon, you would choose the 600dpi option. Epson printers run at multiples of 360dpi, so you should select 720dpi in OBTi. Selecting an OBTi resolution that is different than your printer resolution may result in false moire or patterning.
Back to top
Operation
Does the OBTi control panel need to be open in order to process files?
No. If you set up your hot folders to use a file name pattern to detect files, OBTi will operate automatically. If you set up your hot folders to use an ini file, then you most likely will have to open the control panel to queue files, with one exception: if your workflow can create an ini file that ties the one bit TIFFs together as a job. If your workflow creates an ini, then the ini and the TIFFs should be put into the hot folder and it should operate automatically. OBTi operates as a system service, and therefore runs in the background. The control panel is simply where the parameters are set for OBTi to operate.
What is better, a separated PS output file or a CMYK TIFF?
It depends. Generally, a CMYK TIFF output file will be smaller in size and process slightly faster. However, CMYK TIFF requires that there be data for all four colors. So, if you are doing spot colors or less than all four CMYK colors (duotones, for example), you should select separated PS.
Why doesn't my job log window show the processing progress?
As files process (or error) the log file gets updated. In order for the log window to update, you need to click somewhere other than the job log selection, and then click the job log again. This will refresh the window.
I'm editting my hot folder settings. How do I save the changes?
There is a SAVE button in the toolbar. Whenever you click that button, all settings for all hot folders are saved. The configuraiton log of each hot folder will then show the latest settings. If you make a change, those changes are not in effect until you click SAVE. If there are any changes that haven't been saved when you exit the control panel, a message will pop up that asks if you want to save the changes or discard them. This is the only place where you have the opportunity to cancel unsaved changes or revert to the previously saved values in the hot folders.
Back to top
Troubleshooting
OBTi is not picking up all the files in a job or it creates multiple output files rather than one.
There are two possible causes: File Name Pattern Wizard or number of hot folder cycles. If you are using the File Name Pattern Wizard, it is possible that the pattern you have defined does not allow OBTi to group the files of the job properly. Modify your pattern. The second reason may be due to the amount of time you are allowing for file transfer. In automatic mode, OBTi uses a timeout to determine that all the files of a job are in the hot folder. The time is computed by multiplying the hot folder cycle time by the number of hot folder cycles. It is possible that one of these settings is too low and that the files are taking too long to get to OBTi. OBTi would then see the files as different jobs and act accordingly. Raise one of these settings to increase the wait time. The last option is to queue the files manually.
How do I know OBTi processed my files correctly?
OBTi is intended to run in the background, unseen. There is no progress bar. In order to determine if your files processed correctly, you can look in a couple places. The "view job log" in the control panel will show the status of file processing. As each file is converted, the log will record a conversion. When the converted files are combined into the output file, the log records the combination. If a file errors out, an error will be recorded. Whether files complete successfully or fail, the original one bit TIFFs are moved to the "processed TIFF" folder. If the files complete successfully, the completed output file will be in the "contone output" folder. If they error out, the files will be moved to the "OBTError" folder. Use the TIFFtest.exe utility to troubleshoot the files before calling for support.
My TIFFs are being moved to the processed TIFF folder without any converting being done. Why?
OBTi is designed so that any files that the system does not determine are valid TIFFs get moved to the processed TIFF folder. The TIFFtest.exe utility can be used to determine if a TIFF adheres to the standard specification or not. Any files not adhering to the TIFF spec will not be processed by OBTi. This is so that integration into workflows will not require changing the workflow. For example, Delta workflows produce one bit TIFFs and several other supporting files. The TIFFs would be converted and the originals would get moved, but the supporting files would just get moved, thus preserving the file and folder structure of the workflow.
Back to top
|
