FAQs:
Who will benefit from the new logic?
Answer: Preps customers actively using SmartMarks anchored to Page or Page Bleed within Preps layouts.
What is the procedure for applying Preps 9.5 new logic?
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.
Tip: Take a screen shot of the existing SmartMark properties.
Are mark anchors other than Page and Page Bleed affected?
Answer: No, the new logic is currently only intended to address Page and Page Bleed Mark Anchor issues.
When does the new logic get applied?
Answer: When the new mark is created, we have added a flag that will instruct Preps to use the new logic.
What if I currently have “-RETAINLEGACYANCHORMARK:YES” added to my Preps profile?
Answer: Preps 9.5 ignores “-RETAINLEGACYANCHORMARK:YES” within the Preps profile. It is no longer valid and is not necessary to remove.
What can I expect if I do not create a new SmartMark with the new logic?
Answer: Marks may not 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.
Referenced PR | Description |
|---|---|
| PREPS-16652 | Import imposition failed mostly if job home is Azure file storage. |
| PREPS-16665 | Preps 9.0.2 - “-RETAINLEGACYANCHORMARK:YES” causes unexpected results on "Back" in VPS Output when Page Marks anchored to the Face |
| PREPS-16666 | Preps 9.0.2 - Page Marks anchored to Face are incorrect. |
| PREPS-16667 | Preps 9.0.2 - Unexpected results on VPS Output when Page Marks anchored to the Binding Edge |
| PREPS-16670 | Text Marks anchored to Page Head are shifted vertically towards Head on output with -RETAINLEGACYANCHORMARK:YES and cropped if -RETAINLEGACYANCHORMARK:NO |
| PREPS-16680 | Preps 9.0.2 - Page Marks anchored to Face are incorrect. [For rectangle/custom mark] |
| PREPS-16681 | Preps 9.0.2 - Page Marks anchored to Face are incorrect. [For Page Bleed] |
| PREPS-16685 | Preps 9.5 - Rectangle Marks anchored to Page foot positions in Preps preview do not match output. |
| PREPS-16687 | Text mark shifts into content (visible within VPS) when anchored to Page Bleed Foot |
| PREPS-16693 | Preps 9.5 - Some issues with the Marks anchored to Page/Page Bleed Binding Edge |
Referenced PR | Description |
|---|---|
| PREPS-16682 | Preps 9.0.2 - Unexpected results on VPS Output when Page Marks anchored to the Binding Edge [line mark issue only] |
| PREPS-16696 | Preps 9.5 -The issue of the Line Mark anchor to the page/page bleed face position |
| PREPS-16694 | Preps 9.5 - The positioning of the Text Mark after the rotation angle is incorrect (Page Face/Page Bleed Face Anchor) |
| PREPS-16737 | Preps 9.5 - Text Mark anchored to the Binding Edge is incorrect when rotated |
| 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 |
*The M1 processor has been tested on OS 12.x for Preps 9.5. OS 12.3 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.
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:
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.