Hangman

This is the most minor of issues and I almost feel bad for raising it but I'm finding it mildly annoying from a presentation point of view... Double-click a page in the Pages panel and the page is centred within the viewport Use any of the Document Page Navigation options, First Page, Previous Page, Next Page, Last Page or Go to Page... and the page is displayed slightly off-centre within the viewport

Hi @DoctorBe, ExifTool correlates with the JPEG Quality Settings in Affinity Photo... Exiftool -JPEGQualityEstimate filename.jpg Processed RAW file exported as JPEG from Affinity Photo using Quality Settings of 100, 80 and 50

Hi @jarcon, This is a known bug logged as AFB-8231 which happens when the Fields panel is open and docked. You should find that if you either undock the Fields panel or close the Fields panel the delete key will resort to deleting individual characters again...

Hi @legolas, I don’t think there’s anything wrong with your file and likewise I’ve seen several reports of slow export times with 2.2.0… Hopefully, someone from the Serif moderation team can provide some further insight as to why this is happening… Could you confirm which version of macOS you’re using, Ventura or Sonoma?

No problem, hopefully, someone from the Serif team can provide a few more answers than I've been able to... I'm glad you've at least been able to retrieve 95% of what you'd lost in the meantime and I hope recreating the missing 5% doesn't prove to be too onerous... Technically it shouldn't be necessary to make backups every minute though I do understand the concern with regards to what's happened...

I'm really not sure... Do you happen to have any Time Machine backups?

Hi @terbald18, Thanks for confirming which version and thanks for the file... Unfortunately I'm seeing the same error message with both Publisher v1.10.6 and v2.2.0... So the team at Serif can investigate further can you confirm whether the file in question resides on an internal hard drive or whether it has been stored on an external or cloud based drive prior to failing to open?

Hi @terbald18 and welcome to the forums, Are you using Publisher 1.10.6 or v2.2.0? Would you be happy to upload your Publisher file so we can take a look to see if we experience the same issue with your file? If that's not an option you can request a private Dropbox link by replying to this post so someone from the Serif team can look at your file to try and determine what may be causing the issue...

Hi @legolas and welcome to the forums, FWIW, I ran a test on an Intel MacBook Pro, AMD Radeon R9 M370X 2 GB, 2.8 GHz Quad-Core Intel Core i7, 16 GB 1600 MHz DDR3 and to export all 1,240 pages (620 spreads) using the PDF (digital - high quality) preset took 34 mins 30 secs... I'm unsure what to conclude from that but is your export time with other apps open or just with Publisher open when exporting? (I had several other apps open during the export test) I'm also assuming you're running Publisher v2.2.0?

Hi @Lesslemming and welcome to the forums, I've been running V1 with Monterey for several months without any issues so personally I would say it is safe to upgrade to Monterey if your Mac supports it, which I'm assuming from your question it does.

Hi @DianeF, One thing you could try if you are happy to do so would be the following, assuming you are able to open your file without it crashing. Steps Create a duplicate of your Publisher file in the Finder, give it a slightly different name (e.g., add a v2 suffix) and then open the duplicate file Delete Master B from the Master Pages panel, Save and Close the file Create a new single facing page Letter document using the same settings as your original document using the Default Master From the Document menu select 'Add Pages from File...' and select your newly saved duplicate file Select the following settings and then click OK... This should add all pages and Master Pages from your new file You will likely have to reapply what was your Master C page which should now be renamed Master B because you deleted the original Master B to the relevant pages Save the file See whether that makes any difference at all or whether in doing the above you still experience the same crash when changing the font size or in any other situations where you were experiencing the crash. Note: This may make no difference at all but equally if there is an element of corruption in your original file it may work. Let us know how you get on or if anything above doesn't make sense.

Hi @Dan C, This may be totally unrelated but based on your screengrab above I recreated Master B including the duplicate text frame mentioned by @DianeF and the very first time I attempted to link to it Publisher crashed, however, since that point I've not been able to get it to crash hence why this may be a pure coincidence but I've attached the crash report just in case it is related and points towards anything. Affinity Publisher 2 Affinity Store-2023-09-29-094758.ips

Hi @martenf, I can see nothing wrong with your PDF file at all in terms of quality. The Page numbers are vector, the images 300 dpi sRGB2014 and the image quality looks absolutely fine. The only slightly odd thing I spotted when re-opening the PDF in Publisher and viewing it in a PDF viewer is that the two images at the top of Page 40 appear as rectangles rather than image layers in Publisher and are subsequently missing as images in the PDF viewer despite appearing on the page itself but I can't see that this would be the cause for darker images or fuzzy text. The Page numbers themselves are not K100 but rather a CMYK split so the only thing I can think here in terms of any fuzziness is that there is a slight misregistration at the printer's end which would potentially account for the fuzzy text. Is all the text throughout the magazine a CMYK split rather than K100? In terms of the images appearing dark, does the print company use or request a specific colour profile to be embedded in the supplied PDF file? The PDF uses a Generic CMYK profile and it sounds as though the print company has likely converted the file to whichever profile they use for their press which does have the potential to change the appearance of the images and subsequently could result in darker images depending on the profile used... Based on the checks you've detailed it doesn't sound as though anything has changed between the Publisher setup used in v2.1 and that in v2.2. What is the print company saying in terms of why the images appear too dark and why the text is fuzzy? Finally, could you provide a link to the print company's website so we can see if they show any particular specs they require when providing print-ready PDF files?

Hi @martenf, From your initial description, this sounds more like an issue with your print company but without seeing a sample PDF it's going to be difficult to track down. Are you able to either upload the PDF exported from Affinity Publisher v2.2 or at least a sample page that represents the issues you're seeing when printed, i.e., the fuzzy text and dark images so we can take a look to determine whether or not there is an issue with the PDF itself or whether this is indeed an issue with how the print company is processing your file?

Hi @Dan C, The sRGB v4 ICC preference profile is simply a v4 replacement for commonly used v2 sRGB profiles. According to the ICC website, "it gives better results in workflows that implement the ICC v4 specification. It is intended to be used in combination with other ICC v4 profiles." I have it installed on my system.