Jump to content

Rabari

Members
  • Content count

    22
  • Joined

  • Last visited

About Rabari

  • Rank
    Newbie

Contact Methods

  • Website URL
    https://www.sandelinmedia.com

Profile Information

  • Gender
    Male
  • Location
    Helsinki, Finland

Recent Profile Visitors

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

  1. 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.
  2. 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.
  3. 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.
  4. Rabari

    Damaged File

    Publisher looks very promising, and I really would like to use it, especially since i moved to Catalina, and ID CS6 won't open anymore. But save files should never become corrupt. Never, ever. No matter what. Let me repeat that. Never. Not for programs like Publisher, which often are used for ”mission critical” work – with tight and immovable deadlines. I've used Publisher now for a couple of fairly large projects (tabloid size, 20 pages, with the usual assortment of linked raster and vector images of different formats and color systems), and I regret to tell you I find myself back in PageMaker days, when a whole day of work could disappear in a puff of smoke because of strange, hard to reproduce crashes and subsequent corrupt, unopenable save files. Now, after saving a lot of "known last good state" files, and after I fiddle around with saving linked images in another format, or clicking different things in the Metal/One GL acceleration settings, or changing around options in the pdf export settings, I do manage to (barely) get my Publisher jobs to the finish line… You can say a lot about Adobe and InDesign, but ever since I started using ID 2.0 waaay back in 2002, I have never come across a situation where an ID save file would be corrupt and unopenable, or for that matter that the app would crash when doing normal stuff like moving around in the document, or exporting a pdf. This one Adobe really nailed. Strangely, some problems, sometimes, seem to resolve when I restart the machine. Are th eproblems then mainly memory corruption issues? Running out of memory? Or something to do with the GPU acceleration? Or a combination? I can't pin it down. Regardless, robustness of the app and the save file should now be of the utmost, highest priority for the Publisher developers, even at the expense of new shiny features (though i of course eagerly await footnotes…) Rant over. MacMIni late 2014, 16 GB, MacOS 10.15.1 Publisher 1.7.3
  5. …aaaand suddenly everything works just as it should. Without a restart. Without even quitting and restarting the app. Just letting everything sit over the weekend when I was away… I have a feeling this is not the first time small problems seem to fix themselves. Are there silent updates going on behind our backs?
  6. Since upgrading to Catalina, i cannot type anything into the main toolbar font selection box. If I select some text in my document, then click in the font menu (which opens normally)… …and type in for instance "Adobe Caslon" to quickly change the font of my text in the document… …nothing happens in the font menu (it stays at "Arial"), but instead the text in my document is replaced with "Adobe Caslon"- Workaround is to scroll to the desired font in the font menu. Pic 1: Before clicking in the font menu box: Pic 2: after trying to select Adobe Caslon by typing in the font menu box (instead of scrolling down the font list)
  7. Thank you for the illuminating responses! Using the CMYK/8 Document Colour Format setup fixed the problem. Why didn't I try that in the first place? (A bit strange that the Grey/8 setup produces four colour plates… I used the Generic grey profile. Seems like there is a great deal of RGB going on in the Affinity apps behind the scenes)
  8. When exporting a pdf for press printing, I can't get any graphical elements to export as K only, even though I define them for instance as 10 % K with the CMYK sliders on the Colour palette. They turn up on every printing plate (C, M, Y, K). Even text defined as black is output to all plates. This is problematic, as simple b/w pages could be output as expensive four colour jobs, with unnecessary registration problems etc. I've used a "Press (Print Ready)!" document setup, and a document Colour format which corresponds with the output I desire (Grey/8). I output the pdf to a pdf/x-4 format. I've tried creating my own colours in the Swatches palette, but I just can't figure this one out. Example: 1. Below are some elements, all defined as percentages of K. Selected is a 15 % K rectangle 2. The exported pdf opened in Acrobat, which shows the elements appearing on all plates. When deselecting Process Black, as in the screenshot, nothing should be visible, as all elements should be shades of "pure" black)
  9. I made a similar post some time ago. That seemed to be the only way of using additional spelling and hyphenation dictionaries. A real nuisance every time the app got an update. Now I tried placing the hyphenation and spelling folders also in Library/Dictionaries Seems to work!
  10. Rabari

    Memory leak?

    As my problem seems pretty isolated - could it be that it was a conflict with the app Memory Diag? Memory Diag tries to free up memory under constrained situations. It looks and ”feels” nice to see your "Free Memory" go from, for instance, 170 MB to a couple of Gigs – but who knows what it actually does, mucking about in the memory management? Perhaps better to stay off it.
  11. Rabari

    Memory leak?

    Open, no full screen, no documents open
  12. After using 1.7.0. extensively I left the app open overnight and through the next day (with no documents open). When i returned tonight Photo was unresponsive. I checked Activity Monitor and it showed Photo consuming over 70 GB memory. Note that Publisher was also running at the same time – any connection? Similiar things happened during the Beta, but at that time the app also consumed all virtual memory, and subsequently all free space on my startup SSD. This didn't seem to happen this time with 1.7.0. The disk looked normal, although the Photo memory use reported by Activity Monitor looks extreme. Mac OS 10.14.5 Mac mini Intel Core i7, 3 GHz, 16 GB
  13. Workaround for problem 1: Deselect "Separated mode" in Window menu Reselect "Separated mode" in Window menu Document shows in main monitor.
  14. Setting via Hyphenation option. It's great that Publisher finds it, after I manually, and every time the app is updated, install the hyphenation file in the Application bundle. The problem is not that I can't get hyphenation working. My point is that mucking about in the Application Bundle has never been a recommended activity, and certainly nothing you would instruct inexperienced users to do every time the app is updated. So the shipping version should recognize other places. The user/Library/Spelling folder would be better, even if it resides in the (nowadays) hidden Mac Library folder.
  15. I was asking, as creating a Spelling folder inside my user folder did not work. As did not, eventually, using the Spelling folder in the /user/Library folder. I can get hyphenation working only by installing the hyphenation dictionary directly into the app bundle. Tedious.
×

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.