Page History

...

New features and enhancements

Preps 9.5.x features new logic as a solution to many reported Page and Page Bleed Mark Anchor issues found in Preps 9.0.x. (See 9.0.3 New Features, Fixed Bugs, and Known limitations v9.0)

FAQs:

1. Who will benefit from the new logic?

   1. Answer: Preps customers actively using SmartMarks anchored to Page or Page Bleed within Preps layouts.

2. What is the procedure for applying Preps 9.5 new logic?

   1. Answer: Launch Preps 9.5. Open or create a layout with SmartMarks anchored to Page or Page Bleed. If the mark is located in an unexpected position, recreate the mark in Preps 9.5. Save the new mark.

   2. Tip: Take a screen shot of the existing SmartMark properties.

3. Are mark anchors other than Page and Page Bleed affected?

   1. Answer: No, the new logic is currently only intended to address Page and Page Bleed Mark Anchor issues.

4. When does the new logic get applied?

   1. Answer: When the new mark is created, we have added a flag that will instruct Preps to use the new logic.

5. What if I currently have “-RETAINLEGACYANCHORMARK:YES” added to my Preps profile?

   1. Answer: Preps 9.5 ignores “-RETAINLEGACYANCHORMARK:YES” within the Preps profile. It is no longer valid and is not necessary to remove.

6. What can I expect if I do not create a new SmartMark with the new logic?

   1. Answer: Marks will retain the positioning from the version in which they were created. If created in Preps 9.0.x you may encounter unexpected results in Preps or on output.

M1 Chip Support*

Fixed bugs 

...

Additional Known limitations

*The M1

...

processor has been tested on OS 12 for Preps 9.5. OS 12.1 has not been fully tested at this time.

We recommend deploying any OS 12 Intel and M1 Macs with caution. Consider first creating a dual boot environment or Time Machine backup.

...

Please also see the Prinergy, ColorFlow, VPS+, Pandora and PLA Release notes for supported client workstations and known limitations.

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 ++).
~Important Note~
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 early 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.
Workaround: Add t: before the Range keyword. For example, t:odd or t:even.

...

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.

...