Jump to content

hr.mu

Members
  • Content Count

    27
  • Joined

  • Last visited

About hr.mu

  • Rank
    Newbie

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. 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!
  6. 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.
  7. 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
  8. when working with an image editing software I very often use tools with an adjustable tool size (brushes, pencils, eraser, clonig tool, ....). And I very often adjust their tool size while working with it. In affinity photo it is mostly very akward to adjust these tool sizes: You have to click on the pixel size field, you have to blindly adjust the size by ruler (you do not see the resulting actual tool size) and you have to click again to confirm this resizing. Only now you see the resulting new tool size. If it is not correct, you have to redo all over again. It would be much nicer if we could do all resizing for any tool by just right clicking the mouse button together with the ALt-key and dragging the mouse according the new size, which is cocurrently being shown while dragging.
  9. when developing HDR images there is the danger that with RGB color mode you get color faults, because RGB represents color and luminance in the same value. If Affinity Photo would enable a LAB 32 bit HDR color mode that would solve the problem. Because color and luminance are now separated, the large dynamic range of HDR images are mainly reflected in luminance. This prevents color faults during HDR generation. By the way, I like the way Affinity Photo is adressing HDR development in the workflow. However, because I quite regularly get color faults during development, I can not use it in many situations (see attached image as an example for such a color fault in the sky). In this case I use my LAB 32 bit based HDR development programm (Oloneo), which produces nicer color without color faults.
  10. Hi Chris, thanks for the response. It is true, with an image open the background slider is working too. But I still see no effect for the artboard background slider (maybe I do not know what this is all about) and the tool icons do not adjust for light UI settings. I attach a screenshot of the UI light. I am using a windows 7 Professional 64 Bit environment. Apart from Affinity Photo there is only a firefox browser and Outlook 2013 open when testing this issue. I use a NVIDIA GeForce GTX 1050 Ti graphic card which is recognized by affinity photo settings. Cheers
  11. In your Light UI video you demonstrate how to adjust the UI appearance. Under windows it does not seem to work correctly. Under windows I can switch between light and dark UI style and the UI gamma slider seems to work. The background and artboard background grey level sliders do not show any effects under windows. The tool icons are not adjusted according style. With light UI I see the same icons with black background as used with the dark UI style. E.g., the cutting tool is just a dark square with light UI style. The front UI size adjustment (default / large) is missing alltogether under windows. Can I somehow activate the backgroud grey level sliders and adjust the tool icons for the light UI style?
  12. When opening an image file with embedded color space profile, you can either work in affinity photo with this embedded color space profile or affinity photo will apply color management to adjust the image to the default color space profile as set in the affinity photo color settings. For me it would be much more economic if the color settings would allow to inform if the embedded image ICC profile differs from the affinity photo default ICC profile (according settings) and asks whether to keep the embbeded profile or change it (comparable to photoshop handling).
  13. Affinity Photo help documents that one can change the brush size (exactly as in photoshop) by moving the mouse left/right while pressing the Alt-key and the right mouse button. In the current windows version this seems not yet to be implemented (similar to the up/down adjustment). Is this feature in the pipeline?
×
×
  • 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.