Problem: Lucid Trapping plug-in does not start and writes a message into the Rip window “Lucid dongle is absent or expired. Lucid license is absent or expired”.
The cause (1) can be that license manager service was not started and/or dongle driver was not installed. Generally trial version of I-Trap™ is protected by Lucid license and the full version is protected by the dongle.
Solution: run the program from the shortcut in your computer Start menu
/Lucid Dream Software/Support tools/Create report about Lucid Dreams’ common files. The text file is created where you can read the information about the license manager service and the dongle driver installed on your machine. In case they are missing you can install them manually using the shortcuts in the Start menu
/Lucid Dream Software/License Manager/Install license server
/Lucid Dream Software/Dongle Manager/Install sentinel dongle driver.
If the license service is running the cause (2) can be missing license file.
Solution: first you have to create Locking codes for your computer using the shortcut in the Start menu /Lucid Dream Software/License Manager/Create locking codes.
Send this file to Lucid support team. You will get the license file back and have to install it.
You can install the license file generated by Lucid using the shortcut in the Start menu
/Lucid Dream Software/License Manager/Install license.
Problem: occurs on the first pass; the rip does not process the job with some kind of PS error message logged into the Rip window.
The cause (1) can be the old Rip version (see warning 9).
Solution: update the Rip.
The cause (2) can be that the option “Recombine pre-separated jobs” is Off in the Trapping plug-in setup for Color style configuration.
Solution: switch the option On.
If neither helps: run this job through the default page setup in your Rip. Make sure that the “Recombine pre-separated jobs” option is On in the color management settings dialog for the default page setup.
If the job fails in the default page setup you need to rebuild the job, the Rip is unreliable on pre-separated jobs, see Warnings 7-10.
If the job processes through the default setup, then complete the incident report as required in the section below.
Problem: occurs on the second pass, the Rip does not process the job in final output device queue, there is a rip VM error or PS error logged into the Rip window.
The cause is insufficient memory for the second pass.
Solution: (1) switch the option “Recombine pre-separated jobs” Off in the setup for Color style configuration in your output device setup.
Solution: (2) if the (1) does not help. Add memory for the Rip in the dialog /ScriptWorks/ConfigureRIP../Options/. See Warning 6.
Problem: You trap the job in the I-Trap™ Viewer and see fine looking traps (or you trap the job in the automated workflow), send the job to the Rip for final output and no traps are present.
The cause of the problem is that traps raster file is not interpreted by the Rip.
Solution: (1) if the job was pre-separated. See the section 2, and try to apply one of the suggested solutions. If neither helps, prepare an incident report as required in the section below.
Solution: (2) if the job was composite check the used page setups and make sure that they comply with the requirements explained in the Step-by-step configuration of trapping queues guide. Pay attention to the issues concerned with the color styles configurations ( User Manual , chapter 6, Configuring the trapping queues). Make sure that Trapping plug-in page setup configuration of the color styles allows other colors in job and requires Not blank separations.
If neither helps, then complete the incident report as required in the section below.
Problem: You trap the job in the I-Trap™ Viewer and see fine looking traps (or you trap the job in the automated workflow), send the job to the Rip for final output where traps are misplaced, or there is a hairline outside trapped line, or traps look like a fringe.
The cause of the problem is that in the page setups for trapping and final output resolutions do not match.
Solution: read the Appendix and follow the instructions as described in the example 1 workflow configuration.
Problem: You trap the job in the I-Trap™ Viewer and see fine looking traps (or you trap the job in the automated workflow), send the job to the Rip for final output where traps are white instead of real color.
The cause of the problem is that in the page setups for trapping and final output color styles’ settings do not match.
Solution: read the Appendix and follow the instructions as described in the example 2 workflow configuration.
Problem: When you process the job with tuned screen angles (dot shape, frequency) only through the rip, the screen angles (dot shape, frequency) are correct. When it is processed through I-Trap, the screen angles (dot shape, frequency) are not preserved.
The cause of the problem is that the requirements to not override your application settings should be placed in both page setups for trapping and final output color styles.
Solution: open the Page Setup for “LucidTrap” device and uncheck the “Override angles in job” (“Override dot shape in job”, or “Override frequency in job”) in edit style for “CMYK Composite” which is the only possible style for this device. Do exactly the same changes to the Page Setup style for your final output device. Remember, that these settings should always coincide in the LucidTrap and the final output device Page setups.
Problem: PS jobs created on the Mac in PageMaker and printed to the Apple Talk channel to the Rip pass through the automated Lucid trapping plug-in setup and are not picked up by the final output channel. Or a job stays unprocessed by the second pass until other job is printed to the same trapping setup queue.
The cause is that Mac PageMaker adds some PS wrapper to the source file that impacts the rip runtime environment and the trapping plug-in cannot access necessary data to create the control file.
Solution: it is recommended to create PDF files instead.
If you have a problem with I-Trap™ that falls out of the listed above it is necessary to collect the information presented in Table 1 and/or 2 and supply it with the problem report to the trapping support team. The Table 1 should be filled in if the problem occurs with the rip trapping first or second passes. All version numbers should be taken not from the installer history file but from the actual directories.
A support program is installed with the I-Trap™ as the shortcut in your computer Start menu
/Lucid Dream Software/Support tools/Create report about Lucid Dreams’ common files. The text file is created where most of the required information is present.
Table 1
1. Computer OS (NT 4, W2K, XP), version
2. Computer RAM size
3. Rip name
4. Rip version number (if it is OEM rip what HQ version this number corresponds to)
Memory allowed in the rip
5. Problem job type (PS / PDF)
6. Preseparated (Yes / No)
7. Creator of the job (Mac/PC, what application)
8. How the job is sent to the rip (Apple print, NT print, hot folder, directly)
9. Zip archive of the following files from the folder <rip dir>/SW/Config/:<Inputs>; <ConfigureRIP>; <PageSetupManager> and the whole subfolder <PageSetups>The names of required files and folder are in angle braces.
10. What is the used workflow (Automated / Interactive). Give details if any.
11. Rip Trapping plug-in version number (take from the rip log window at startup)
12. Itrap.dll version number (take from the OS Properties window clicking on the file in /<I-Trap™ viewer directory>/plugins/itrap.dll)
13. Description of the problem in step by step fashion
(Lucid will shortly create a support tool program that would archive the rip’s configuration files, and install it with the software.)The support team would not be able to help you solve the problem effectively if your problem report doesn’t contain such information.
If the information in the table above is not sufficient to figure out how to solve the problem then next step would be to upload the source file.
Make a zip archive of your source PS or PDF file. Optionally you can include screen shots that illustrate the problem. Consolidate everything in a shareable folder.
Point your browser to the URL
https://luciddream.biz/contact/
Share the link to the shareable folder.
Support team receives the upload message automatically.
If the problem is in I-Trap™ Viewer the information we need should contain
Table 2
1. Computer OS (NT 4, W2K, XP), version
2. Computer RAM size
3. I-Trap™ Viewer version number (take from the about box)
4. I-Trap™ plugins names/versions (take from the /Options/PluginsInfo menu)
5. Itrap.dll version number (take from the OS Properties window clicking on the file in /<I-Trap™ Viewer directory>/plugins/itrap.dll)
6. The problem job TIO file (take full path from the Page manager info and collect the file)
7. Description of the problem in step by step fashion
