Jump to content


  • Content Count

  • Joined

  • Last visited

About Rabari

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Helsinki, Finland

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ok, thanks! Strange combination indeed, for files coming out of Affinity Photo Sorry, untouched photos. Why do people scan B/W photos in RGB? Could problematic files like these be flagged in Pre-flight, perhaps?
  2. Ok, uploaded now. Maybe a contributing factor to problems: this is a file which has been "re-used" a couple of years, where I open up the file from last year, empty out old stuff to put in the new. Could there be some old cruft left? If I remember correctly this project has had similar problems earlier, but they resolved with a new version of the app. Might even be that the original file was made with one of the pre-release betas…
  3. Having big problems exporting to pdf; the dreaded and very unhelpful "An error occurred while exporting to:…” Version 1.8.6. MacOS 10.15.7 File is normal A3, 20 pages, jpegs, tiffs, pngs – nothing unusual. Tried normal troubleshooting: restarting, giving more memory, software rendering, looking for bad links, strange graphics, old broken fonts, etc but no luck. No pdf preset works, built-in or own. Strange anomaly: Export window never finishes calculating Estimated File Size. Beta version opens file, but crashes on trying to choose any pdf export preset. Now a deadline is looming. Cannot afford to loose this gig.
  4. I''m not trying to paint rosy pictures of Adobe, or ”stylize” Adobe as a desirable standard. I'm simplysaying that a robust file format is a desirable standard. Granted, I have not myself encountered unopenable Publisher files. And with paying customers breathing down my neck almost every day, i sure hope I never will.
  5. Gabe, How would you define "overprint black"? Shouldn't the choice (in pdf export settings) apply to all 100 & K elements? Even the manual states that ”You don't need to explicitly make an overprint for black, for black text or black graphics, as this is set by default. On PDF publishing, you can control black overprinting using the Overprint black option in the Export Settings dialog (File>Export>PDF>More).. But now when I place a black greyscale tiff over a color background (raster graphics or Publisher graphic), it knocks out in the pdf x-4. Native text does not knock out, and instead overprints correctly.
  6. Thanks thomaso for pointing out the "K" button. But i seems, at least in my setup, to work only with raster files. It does not show up when activating vector files like eps or svg. Go figure
  7. I've said this before, but it's worth repeating: It's of course very nice that Affinity can fix files that go corrupt. But in a professional setting, a file should never, ever become unopenable in the first place. With hard deadlines, and angry, paying customers waiting, or printers waiting for materials, these kinds of mistakes cost not only money, but reputations. I really, really like Publisher, and i'ts now my main layout app in my own, small graphics company, where I'm going totally ”Adobe-free”. But back at my "real" day-to-day work we still use InDesign. You can say a lot about InDesign or Adobe's subscription model, but Adobe seems to have got at least something right. In all my years, ever since using the first InDesign version, I haven't even once encountered an ID file which could not be opened. Sure, a crash could make the last few edits disappear. But nothing more. I hope a lot of serious development resources at Affinity goes towards making the file format rock solid. It simply has to be. (and then of course II'm hoping for footnotes, but that's another story).
  8. Thanks for the responses! When I experiment with converting to different CMYK profiles, I now see that the text color jumps around to all kinds of different "rich blacks". Coming from another (Adobe) philosophy, I guess this is one of those Afffinity things to consider going forwards. Of course I normally want all text to default to 100 % K, regardless of any chosen (or changed) color profile. I cannot upload the original file. But I attach something similar. I first thought that a svg logo was the only problem, as I turned out it actually was in rgb space. I then made an eps version, and made sure it was exported from a greyscale document in Designer, and sure enough it reports as greyscale in Publishers Resource Manager. But it still is seen on all plates. I'm tearing my hair out now. The greyscale tiff however (from Affinity Photo), for some reason (thank heaven), is only seen on the black plate, as it should. TIFF will be my workaround this evening. BTW, found a nice online separations viewer for at least individual pages, like covers. https://www.pdftron.com/webviewer/demo/color-separation/ testafpub.pdf
  9. Ok thomaso, thanks for the tip! At least I can somehow fix the Publisher native text portions of the file. But additional "rich black" problems are now cropping up. In the files I'm trying to produce with the printers color profile, all black or greyscale elements (like logos or ISBN graphics) also turn up on the color plates. I feel I've tried everything, like un-checking "rasterise unsupported" etc. on pdf export. (I have to turn "convert image color spaces" on, as there are RGB files also. Is this the thing messing everything up). Can't experiment now as I'm out of office. I'll later try converting every bit of color to CMYK, and see what happens. A bit frustrating. Do you have any pdf settings to share, which work?
  10. I have no problem with Publisher defaulting CMYK documents to "rich black” (a mix of CMYK colors) for text. Sure I like to see a default option to use 100 % K for all text, but in the meantime I'll just define all my Text Styles as 100 % K, and problem solved - right? Wrong! Changing a documents CMYK color profile (which I had to do at the end of a large job because my client changed printers) modified all the text blocks in my document back to "rich black". Even though every text style was defined as 100 % K, and nothing else. I had to manually click on each text block, apply the original Style with no overrides (option-click) – or in cases where I had to use overrides, manually chance the color of the text back to 100 % K. Now I pray that no CMYK text element slips through, as these sorts of "mishaps" cause unnecessary and costly delays at the printers, apart from making me look like a fool. (A CMYK separations view mode would also be nice to have). I understand that a new program – even a professional app – has some kinks to iron out (remember Indesign 1, anyone?) But I really hope this gets really, really high up on someones list of critical corrections/improvements. (I Hope this is not something that will ”never be fixed” because of some underlying RGB thing with the whole suite of apps.) ps. Why am I called a "Newbie" here? I've been doing computer aided layout since PageMaker 2, back in 1987.
  11. And now, after a installing a new Mac mini, those places seemingly don't work. But putting the dictionaries also in [user]/Library/Spelling worked!
  12. I see your point, but I often start Publisher when I already have a several other porgrams running, like Affinty Photo, Affinity Designer, Safari, Mail, Apple Photos and a slew of smaller helper apps. At that point there is no available free physical RAM, according to an app like Memory Diag. What kind of memory does MacOS then allocate, and what kind of memory does Publisher use at that point? And how does the settings in the Performance tab relate to a situation like this? It would be really interesting to hear from the devs about this. No app should of course crash. When I experience crashes i try to pinpoint what I was doing. Evidently the last crashes had something to do with me using a few HEIC images. They import and display fine, but seem to cause trouble in memory tight conditions, and also generate errors when exporting to pdf. In another instance I had to change a greyscale tiff (over 5000 px width, but scaled down, so that the Resource Manager could not even display a value for Placed dpi) to a smaller png. Worked thereafter.
  13. Ok, so I seem to have found at least a partial solution: Just allocate a lot of RAM to Publisher! I have 16 GB physical installed, and I had around 7 GB allocated to Publisher. With everything else the same, I bumped Publishers memory allocation to a generous 18 GB (i.e. far exceeding the physical RAM limit) – and everything seems to run smoothly. Publisher also feels much snappier over all, when moving about in big documents. I must have had some old information in the back of my head, telling me to never allocate more than free available physical RAM (with a couple of other programs running at the same time). But this tip seems dated. Apparently virtual memory, or compressed memory, or some other sort of memory management sees to it that this "crazy" setting works.
  14. With more complex Publisher documents, I sometimes experience crashes just moving about in the document.. I have a feeling that the crashes are related to settings in the Performance section of the Preferences, but I can't find anywhere a FAQ or a comprehensive discussion on what the different choices really mean for the stability and performance of the app. A few questions: In the Display section, which is more stable: Metal, OpenGL, OpenGL (Basic) or Software rendering? I suppose Metal is fastest, or am I wrong? Does clicking "Use only integrated GPU" affect anything, especially as I only have an integrated GPU in my Mac Mini. What Does "integrated" refer to: Intel integrated graphics on the chip, or Integrated, as in "internal" as opposed to an eGPU? What effect has lowering or enlarging the RAM usage limit? Is 6 GB enough for more complex documents? Is it a good idea pushing the limit way over installed physical RAM size (I have 16 GB physical RAM installed)? Shouldn't apps allocate memory dynamically, anyway? Why am supposed to fiddle around with this? Does View quality affect the stablity of the app, since one would assume better quality would be more taxing on many resources? Does hardware acceleration/Metal compute really work in any meaningful way on Intel integrated graphics, with its paltry 1,5 GB RAM, which it allocates from main memory? So many questions, I know.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.