DMONEY5th Posted December 19, 2022 Share Posted December 19, 2022 I have been working on a document for months with no issues. Have been able to export as png or jpg for references. Went to export to PDF for final submission for printing, and it causes the program to crash/freeze. All of the text is expanded/outlined, so that shouldn't be an issue. I was able to export this same document to PDF with Designer 1 just a couple of months ago. I attempted to export through Pixel Persona, Export Persona, Photo 2 and Publisher 2, but nothing changed. I tried the preflight check from another forum suggestion and that didn't work. I have also tried to export as PSD and SVG, and it causes the same freezing to occur. And yes, I have waited for the export to "load," but nothing ever happens, and it seems to suck a ton of CPU and cause my other open programs to lag as well. I am running on a Mac OS Monterey 12.6. Nervous to update to Ventura before I can get this file exported for my CUSTOMER. This is now a professional issue. Quote Link to comment Share on other sites More sharing options...
werkform Posted December 27, 2022 Share Posted December 27, 2022 crash_publisher2.mov I can tell you that the mac OS version does not matter. Publisher 2 crashes on several functions, seems to be related with file access. Check out the video, I'm trying to export a book as a PDF. There is a huge bug in publisher2 on mac, hope they will fix it immediately. I need to finish my work also... Harry 69 / 5.000 Quote Link to comment Share on other sites More sharing options...
loukash Posted December 27, 2022 Share Posted December 27, 2022 1 hour ago, werkform said: trying to export a book as a PDF Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
werkform Posted December 28, 2022 Share Posted December 28, 2022 Doing a PDF via the printing-dialog is possible (but not useful). The problem is not in generating pdf's , it's about crashing while trying to access linked files. I had a lot of crashes during the work with documents in the matter of a missing font also. The same with missing libraries for spell-checking. I guess this is a very basic problem inside the V2. Harry Quote Link to comment Share on other sites More sharing options...
loukash Posted December 28, 2022 Share Posted December 28, 2022 3 hours ago, werkform said: crashing while trying to access linked files. If that's known, then you need to fix the linked document first. Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
werkform Posted December 28, 2022 Share Posted December 28, 2022 8 hours ago, loukash said: If that's known, then you need to fix the linked document first. No that could not be the way. Sometimes it's not possible (f.e. missing fonts) to fix this. See other threads, you will find some "crashes publisher 2" more or less with the same thing. There is an issue within the publisher 2 (mac) and this has to been fixed. Using software like skirting cliffs feels like XPress 3.0, more than 20 years ago ... Quote Link to comment Share on other sites More sharing options...
loukash Posted December 28, 2022 Share Posted December 28, 2022 19 minutes ago, werkform said: See other threads, you will find some "crashes publisher 2" more or less with the same thing. Sure. Just recently I have reported one of those export bugs myself. Has been fixed in the final v2.0.3. The thing is that we need to provide as many details to the Serif engineers as possible, so that they can act faster. That also includes analyzing what exactly happens on your part, so that the issue is replicable. Trying to find the culprit – and potentially working around the issue by fixing the cause yourself – is part of the bug report process. Anyway. It's holidays so Serif staff likely won't respond this week, see banner at the top. Meanwhile, you can already run the aforelinked PDFlib logging test to have it handy for them when they get back to us next week or so. 19 minutes ago, werkform said: Using software like skirting cliffs feels like XPress 3.0, more than 20 years ago ... Oh, in the early 1990s – which would be 30 years ago – I was still happily using PageMaker 4.2 which had its limits but was solid otherwise. Switched to QXP at v3.3, I think. Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
DMONEY5th Posted December 28, 2022 Author Share Posted December 28, 2022 As a follow up, I think my file size, for whatever reason, may have been read as "too big to export" to PDF. I didn't figure this out in any specific way, just looked around at other sites and searches and tried to fix it. My solution was: Flatten as many of my layers as possible. I didn't merge them, so I still had layers I could go back to, but they were no longer editable since they were flattened. I did this for as many layers as I could where the flattening process didn't affect the effects of the image. Once I did this, I was able to export to a PDF. I still think it's an issue, but I was relieved to find a work around. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.