Gianni Becattini

Yes, it depends on the developer opinion. For me any way is good...

I tested with 2.6.3 (production); the problem is identical.

??? for what I can understand I should revert to 2.5, not 2.6. Wrong?

Thanks for your contribution. Sorry, I was a bit unclear earlier: Bug AF-6599 was my immediate concern. Serif has promised to fix it in the next release, and I want to trust they will. However, the issue with oversized PDFs during export will likely remain, blocking, from my side, on-demand printing services. Given this, having better control over the export process to eliminate the problem would be ideal — a perfect long-term solution. The workaround I proposed… is indeed just a workaround. It still places some burden on the user, but it could probably be implemented in just an hour of development time. It would offer a practical interim solution while waiting for a more comprehensive improvement.

I learned the hard way that Publisher technically supports the inclusion of .afphoto images, but this approach is neither well supported nor recommended. Nevertheless, in my case, it’s essential—converting each image to TIFF every time would be extremely time-consuming. Using .afphoto files also has a major drawback: the resulting PDF files are 5 to 7 times larger than those generated with TIFF images. This makes it impossible to use certain on-demand printing services, such as Lulu. So here’s a small suggestion that could greatly simplify things: when loading linked .afphoto resources, the software could first check for a .TIFF file with the same name. If it exists, load the TIFF instead; if not, fall back to the .afphotofile. As a software developer, I believe this would be a simple and quick change to implement. Any other solution that allows for an easy switch between .afphoto and TIFF—without requiring manual relinking—would however be greatly appreciated. Thanks

Thanks for answering. I hope they really do.

I think I’ve found a workaround — not very practical, but potentially viable. I’d appreciate any criticism in case I’ve overlooked something. Exporting a single page always works. Exporting a list of pages also works, as long as the list includes only even or only odd pages. So, instead of exporting the entire book in one go, I export each chapter twice: First, using the odd-numbered pages (e.g. 1, 3, 5, 7, …) Then, using the even-numbered pages (e.g. 2, 4, 6, 8, …) This gives me two PDFs: one with odd pages, one with even. Then I merge them using PDFSam Basic (free), using the “Alternate Mix” function to interleave the pages properly. Clearly, it’s a cumbersome process — but still far better than manually converting and managing 2,000 TIFF images. And since this would only be done as the final step before printing, it’s tolerable. I’m still not sure whether I might be missing some hidden issue — for example, how to verify the correctness of the bleed in this two-pass export process. In any case, Serif really should fix this bug. Am I the only person in the universe who links .afphoto files as sources, instead of converting everything to TIFF? For me, there’s simply no alternative. I’m a one-person operation managing over 4,000 pages and 6,000 photos — I can’t afford duplication. It’s like programming: I need pointers, not data copies. Thanks PDFsam_alternatemix.pdf

Sorry for having disappeared, I am back again, and sorry also for the "typography" - probably a "false friend" with Italian "tipografia" which means, as you said, a commercial printer. I discovered something but not too useful: a picture "that works" (see the attached files, and afpub and the linked afphoto). It is exported correctly, but even the minimal modification returns back to the error condition. Test.zip

Thanks Rat! The problem is that when I EXPORT the pdf as PAGES (as all typographies want), many image placed on the right pages I mean: if i want to export also the bleed in the first pdf, I just thought "I can increase the page size". But when I change it in Document Setup, nothing changes. .... I finish this evening ... I am dragged away

Thanks for the Idea, Rat, but how to add the bleed to the first pdf?

One of the problems is to export also the bleeds. If I buy a Windows PC and buy Acrobat or something like that, can I Print with the bleeds etc. (color profile, printer marks etc.)?

But how can make Publisher to add the bleed to the produced file? Is there a better printer driver than the native one by Apple? Years ago, Acrobat could operate also as a printer driver, but this possibility was removed in the later versions.

Thanks also for your willing to give me a solution, but it cannot work. I have a lot of pictures across the spread (see the example below). If I unset the "Facing pages", the picture remains only on one page but doesn't appear on the other (or there is some way that I didn't understand?)

I mean that the typography asked me a lot of things, like the bleed, the color profile, the crop marks etc. As you know, I am not an expert and worked a lot, under their guide, to tune the export to obtain a file suitable for the production. All this lacks in the normal pdf driver, or at least I think so... Am I wrong? For the last book I worked a lot, a complete week long, to replace the afphoto files with TIFF files. I am totally scared thinking that I must do it again for other two books... about 2,000 images... I think that, if you are allowed to insert the afphoto files, Publisher should not block the export as it happens now.

Well, but how to have all the controls offered by the Export command? You cannot go to the typography with that... or am I missing something?

Hi Walt and thanks. 1 and 3 require about one week of intensive work in my case. Can you tell me something more about n.2?

I can't find enough words to express my indignation for not having solved after more than two months the AF-6599 bug, which is totally blocking my business. I used always to be a loving supporter of Affinity, not a detractor, and I sincerely appreciate your work, but in this case your behaviour is truly indecent. Is it possible that you care so little about the work of your customers? Is this your respect for us? Ban me, if you like, but please do something. This is a victim's cry of desperation, and it certainly isn't meant to be disrespectful.

Any news? I need to send to print a new book but I am stuck on this!!!!! Is it possible that I am alone with this problem which seems colossal and totally blocking? How can the others go to print? Is there a workaround? Thanks

I wish to confirm this problem, almost on every file and both on Intel and M2. It is practically systematic and every day I forgot it two or three times and I am forced to kill APub. Not a big problem, but a bit annoying and very easy to replicate. Just wait five-seven second after opening and the problem does not appear and APub remain very stable since on (congratulations!).

Wow! I succeeded! I modified the original file getting rid of the smart objects but leaving the other elements like the lights. I did as suggested by the video and this is my first result. It can be better, but for me is already much. THANKS! (may I modify the thread title or a moderator is required?)

Thanks for the suggestion, but I was not able to make it work. It "seems" to work, but the smartobjects are not curved and remains flat like a salted cod... (see below)

I ask a suggestion. Until I had Photoshop, I used to create books mockups like the one below, using one of the many templates I could find. My skill is limited, and I am not able to do the same with Affinity (with Photoshop is straightforward, just insert the image of the pages). This is the only thing that I really miss. Have you any suggestion? Thanks

MacOS 15.5 - Apub beta 3322 (but the problem is from earlier versions). I quit using Cmd-Q and launch the app from the finder. I don't rule it out that the problem may be related to iCloud Drive - anyway all my files have the setting "Save downloaded" (Conserva Scaricato in Italian), so are non messed up by iCloud. If I wait a few seconds before doing anything, none of the two problems appear. The same happens with books; just wait and everything is OK. My documents are large, with many images. All of them are AP photos (not TIFF or JPEG), rather heavy and complex, with several layers, so, if the app does some pre-processing at startup, it can last more than expected (and some process could be messed up?)

Sorry! May I fix it in some way?

I already bothered you on this point but I cannot fix it - it is not a big problem but very annoying. The problem is that the pen assumes a white fill and black stroke even if I set and synchroniza defaults, then save. For a while it works then starts again. Grateful for help