Jump to content


  • Content count

  • Joined

  • Last visited

About hr.mu

  • Rank

Recent Profile Visitors

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

  1. Hi Wasp11b, thanks for the reply and for the effort of investigating the issue. Your figures correspond vary much to my figures. Opening the publisher file will use about 1,4 GB memory. When exporting to pdf it will use about 5,5 GB to estimate the resulting filesize (in about 9 minutes) and it takes another 9 minutes to export the file. It does not make vary much sense to wait for estimating the filesize. I at once start exporting. Because I sync my files between laptop and pc, publisher will no longer recognize most images as current after sync and warns when exporting. If I update all linked images in one go, it will again take about 6 minutes and use about 6,9 GB memory (whatever happens when updating the images). Finally at least I got rid of the crashes when exporting. I increased pagefile.sys accordingly, that helped. I can live with slow response times because of my 8 GB memory size as long as there are no further crashes!
  2. Nice advice to upgrade RAM to 32 GB. My laptop has a 8 GB limit, no upgrade possible. And I do not like to buy a new laptop only because an application does not handle its memory usage correctly....
  3. I replicated my affinity publisher data to my tablet (windows 10 64 bit pro, 8GB Memory). Here I was able to open and export my 40 page document in Affinity Publisher. However, It took many minutes to export. The windows task manager showed a gradual increase in memory usage from 2 GB to 5,4 GB. The document itself including all linked ressources uses about 200 MB, the generated pdf file is also 200 MB of size. This looks like a serious memory issue.
  4. I created a small document (13x18cm pages) with 40 pages, almost no text and only one or two linked images per page. I tried to export a pdf document, but publisher crashes each time. If I start the export, publisher tries to estimate the size of the document. Without doing anything else, I can see how publisher builds up memory usage up to 6 GB and then ends because of lack of memory (I have a windows 7 64 bit laptop with 8 GB memory). When I try to export I also started the export without waiting for the result of the memora estimate. Publisher shows same behaviour. It builds up memory usage, it does not free any memory. One time I got a blue screen, one time I received a message that there was an error (without any further information), mostly it tells me that it ends because of lack of memory (when it hits the 6 GB size). I was not able to export any single pdf document. Also when working with the document I sometimes run into a memory issue and publisher crashes.
  5. Ups, I do not know why, but after restarting affinity publisher my german keyboard is now recognized correctly....
  6. Hi, after upgrading to the latest update Affinity Publisher does no longer recognize my keyboard with german settings. Hitting 'z' produces an 'y' und german umlaute are no longer available where they should be. I am using the software on a windows 7 64 bit pc.
  7. When trying to print under windows 10, the print window (file -> print) pops up at the top of the screen. In addition, only the lower part of the print window is visible. As the top of the print window is not visible, you cannot move the print window and use it. Under windows 7 the print window pops up in the middle of the sreen, which is fine.
  8. Under Windows 10, when right-clicking the context window appears at the top of the window, not at the cursor position. Under Windows 7 the context window pops up at the cursor position
  9. When exporting your document to PDF, links defined by their url in the text are handled as links in the PDF document. However, the underlying link in the pdf does not always reflect the complete url. If you use urls like https://de.wikipedia.org/wiki/Dreifaltigkeitskirche_(M√ľnchen) Affinity will not recognize brackets as part of the url and will only generate a link like https://de.wikipedia.org/wiki/Dreifaltigkeitskirche_ .
  10. If you try to export your document and you choose the option PSD in the export settings, Affinity publisher immediately chrashes.
  11. In my document all images were embedded by default. Then I changed all images from embedded to being linked. However, the file size of my afpub file remained unchanged (300MB), although all images are now listed as linked. It seems that they are still embedded.
  12. Hi, I am using a document setup with a sRGB color profile. I am inserting various images in the document, some have color profile sRGB, some have color profile ProphotoRGB. On the screen images with sRGB profile are shown correctly from the beinning. Images with ProphotoRGB profile are first shown very dull, it seems to me that the ProphotoRGB values are interpreted as sRGB values. Strangly, when I update an Prophoto RGB image with itself(!) the image is now shown correctly, the color profile seems to be recognized now. When exporting to 'pdf (for export)' the images are shown correctly. When exporting to 'pdf/x-4' again the ProphotoRGB images are shown very dull, the color profile is not interpreted correctly. Best regards Harald
  13. OK, I just did another test. I took two pictures with standard resolution and with sRGB and with Adobe RGB color space, and both images opened in Affinity photo without problems. Then I took a high resolution picture with a camera setting that it saves the high resolution image and in parallel it also saves the same image in standard resolution. Both of these two images cannot be opened correctly in Affinity Photo and produce this pink mess. So maybe that in this situation the standard resolution is saved differently. It would be great if Affinity Photo could also process these high resolution images!
  14. Hi Chris, thanks for the quick response. Both files open in Lightroom V6 without problems, therefore I believe it is a handling issue for Affinity Photo. I am not aware that I can influence the compression set on the camera. I am only aware that I changed the color space set on the camera between these two images. For the PANA4492.RW2 file I used the sRGB color space setting, for the _LUM0777.RW2 file I used the AdobeRGB color space (although EXIF data protocoll color space as uncalibrated. But EXIF data seem to be not reliable, i.e. they protocoll EXIF image height/width as 1440x1920 whereas image size is 5184x3888.). But color space settings should not impact the RAW format, it is only for JPG development. Also I tested high resolution images in between, but both example files have standard resolution.
  15. I use the new Panasonic DC-G9 camera and mainly deal with raw files. When I started in December, I could develop these RW2 files with affinity photo. But now Affinity Photo does not recognize these raw files any longer. Maybe I changed some camera setting, but I am not aware which setting might cause the problem now. For your information, I attach two raw files which demonstrate this behaviour. _LUM0777.RW2 PANA4492.RW2

Important Information

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.