KMS performance improvements for slow networks for Marks and Templates - See Preps Best Practices and Limitations - KMS
|PREPS-16636||[Mac11.4]A warning box will pop up when printing PDF/PS/JDF/PJTF/PPF|
Known limitations new to Preps 9
|PREPS-16594||Preps Migration Utility does not run on a 64 bit MAC|
|PREPS-16591||JDF from Multipress not interpreted properly|
|PREPS-136||Output jdf/pjtf with ps mark flats if you add customized media ,the jdf/pjtf and their ps mark flats clockwise rotation 90 degree unexpectedly|
Additional Info and Known limitations
The M1 processor has been tested on OS 11 and 12.0.1 for Preps 9.0.3.
OS 12.1 has not been fully tested at this time. Please see Requirements.
We recommend deploying any OS 12 Intel and M1 Macs with caution. Consider first creating a dual boot environment or Time Machine backup.
Allow some time to ensure all software works well in your specific environment, before rolling out on a larger scale.
Please also see the Prinergy, ColorFlow, VPS+, Pandora and PLA Release notes for supported client workstations and known limitations.
Preps 9.0.3 and newer installs Profiles folder in a new location - Win Workstation ONLY
When Preps is launched from Workshop (integrated), a copy of the "PrepsPrinergy.cfg.template" profile is pushed to the local workstation and overwrites the "PrepsPrinergy.cfg" Profile. In previous versions of Preps, it was copied to the local installation folder of Preps.
As of Prinergy 9.0.2/Preps 9.0.3 the following is true:
- Profiles folder is now located in C:\Users\<user name>\AppData\Roaming\Kodak\Preps
- Previous versions of Preps are not compatible with Prinergy 9.0.2 (Win ONLY)
- All local custom profiles are accessed from this location.
- Mac = Profile path did not change.
Preps Page and Page Bleed Marks may incorrectly appear within live content
Customers who use Preps Page and Page Bleed marks, should consider NOT upgrading to Prinergy 9.0.2 / Preps 9.0.3 at this time, without first understanding the risks.
See Important Note about Page Marks below.
Page Mark properties are not retained when saved with legacy anchor positions.
This is a Preps 9.0.2 and Preps 9.0.3 limitation for impositions using some Page Marks created/edited in previous versions of Preps.
Workaround: To retain legacy mark positions, add “-RETAINLEGACYANCHORMARK:YES” to the "PrepsPrinergy.cfg.template" profile located on the Prinergy server.
Instructions: Setting Integrated Preps preferences - We recommend updating with a Windows text editor (eg. Notepad ++).
In most cases, “-RETAINLEGACYANCHORMARK:YES” is a viable solution. But, it has been reported that some Page Marks are shifted in Preps 9.0.2 and Preps 9.0.3, as well as, on VPS Output.
For example, in one known case, Page Marks anchored to the Binding Edge on the back of the Signature with “-RETAINLEGACYANCHORMARK:YES” can inadvertently move the mark into the content area and cause spoilage. Please check your VPS carefully. We are addressing these issues in Preps 9.5 (scheduled for Summer 2022 release).
When you use "Odd" or "Even" keywords in the SmartMark Range field, the mark will be applied only for the first press run.
This happens for all marks when the mark anchor is anything except Gutter. See Common settings for SmartMarks.
t: before the Range keyword. For example,
If you add a new sheet while in template editing mode, you will no longer be in template editing mode.
You can still save as template. If you duplicate an existing press run you will remain in template editing mode.
When adding press runs to a job from a template, you cannot rename a signature after it has been edited.
Once you save the job for the first time you will be able to edit the name of a signature.
Preps mark preview limitation.
Textmarks placed too close to an adjacent page may get clipped on output. The mark will not appear clipped in Preps because Preps sandbox must preview the entire image.