altae

Members
  • Content count

    47
  • Joined

  • Last visited

About altae

  • Rank
    Member

Contact Methods

  • Website URL
    https://the-digi-picture.com

Profile Information

  • Gender
    Male
  • Location
    Switzerland
  • Interests
    Photography of course ;-)

Recent Profile Visitors

177 profile views
  1. I really like the focus merge functionality of Affinity Photo but it lacks one essential feature: Saving the current state in order continue later. Currently the sources window that lets you manually blend the different sources (and thus correct ghosts introduced during the focus merging process) disappears if the program is closed. I know I can re-add the sources after loading the file but this is not nearly as intuitive and exact as the dedicated "focus merge mode". To me that's a major drawback as focus merging can be very time consuming work which takes hours. What if I need to take a break and want to continue later? Currently I have to leave Affinity Photo open and hope that the program does not crash while taking a break. What if the program crashes during the process? What if accidentally remove the sources (silly but things like this happen)? Please add either a possibility to save the document and reopen it later with the dedicated "focus merge mode" still active meaning the sources still present in the sources window and the clone tool still working without having to select a source point. Or, even better, give us the possibility to switch the "focus merge mode" on and off at will. This would be a major improvement. By the way: I don't use the HDR merge functionality but I guess that it's ghost removal tool works the same way as the ghost removal in focus merge. It would be great if you could implement the same functionality there too.
  2. There's something that has been bothering me from the very moment I started using Affinity Photo: The calculation of the estimated file size in the export dialogue. If I want to export a multi layered project this calculation renders the whole program unresponsive until the approximate file size has finally been determined. And every successive change of the export settings causes Affinity Photo to recalculate the file size and the program becomes unresponsive once more. The described issue is very annoying and also unnecessary to me as I don't see the point in calculating such an estimation. I've got enough experience to know that a jpg with a certain quality setting is going to be of a certain size. Is it possible to optimize the corresponding algorithm so the waiting time can be eliminated? Or maybe you can implement a switch which let's the user turn this feature on or off which would also improve the situation for all those who don't need this estimation. Thanks in advance for looking into it.
  3. I realized that in the latest stable version 1.6.1.93 the "Shadows Range" value of the Shadows & Highlights Live filter is still reverted to 50 % when the corresponding image file is closed and loaded again. I thought this issue had already been fixed?
  4. This has been the case for several versions now. @Serif: Please look into it. What's strange is the fact that it's only that slow if I draw in the "edit mask" mode. If I draw without showing the mask there is almost no lag.
  5. On my computer it's not that bad but I can confirm that drawing on masks is generally very slow. I edit a lot of 32 bit RGB files and masking is definitely no fun at these waiting times before a brush stroke is finally applied. This is still the case with the latest stable release.
  6. I can confirm that the above mentioned bugs have been fixed in version 1.6.0.89. This thread can be archived.
  7. Performance of the healing brush when using "Current layer & Below" is still unbearable. Shadows & Highlighs live filter still reverts Shadows Range to 50 %. New: The Blend Ranges dialogue is flawed, as soon as there are 3 or more points to define a custom blend range the corresponding values cannot be entered manually as the boxes for the input and output values are greyed out (screenshots attached).
  8. Masks in 32 Bit: Preview exposures still influences the grey tones shown when editing a mask. If I paint an area in middle grey (grey value 128) and increase the preview exposure this area becomes white and if I decrease the exposure the area becomes black. Masks in 32 Bit: I have a 32 Bit panorama with a total of 3 layers. If I add a mask and edit it using the mask edit feature the brush strokes are so slowly applied that I have to wait minutes for Affinity to complete the process. The corresponding file is a 32 Bit .afphoto file and the image is 12341 X 5524 pixels.
  9. Inpainting brush in 32 bit mode: Preview exposure changes color of marked area. Is that on purpose? Wouldn't it be more logical if the color of the marked area was always red? Healing brush in multi layered images: Performance when using "layers beneath" as source is still very bad, hardly usable at all.
  10. The Shadows Range of the Shadows & Highlights Live Filter is still reset to 50 % after closing and reloading a file.
  11. Using the latest beta I've encountered a few more problems but I cannot really tell if they are actually new and related to this particular version. Healing brush: If used in a multi layered document the performance of this tool is so poor (meaning so slow) that it becomes literally unusable. Every brush stroke causes the program to become unresponsive for seconds and even after the brush stroke has been applied the program keeps lagging badly until I select another tool. Shadows & Highlights Live Filter: It keeps resetting the shadow range to 50 % every time the corresponding file containing such live filter is opened. I consider this a major issue because this actually means that despite saving the document Affinity resets the changes made by this filter every time the document is opened. HDR Merging: I tried to merge a 40 MP HDR panorama (5 exposures, each one consisting of 6 vertical shots stitched by PtGui). The first try ended with Affinity crashing while applying noise reduction. The second try (this time noise reduction was inactive) failed because after merging the exposures the performance of ghost removal was so poor, I had to wait minutes to simply take a look at the different sources in order to decide which one to use for removing a ghosted area. By the way, my computer is fairly powerful (AMD FX-8350, Geforce 770 GTX, 32 GB Ram, OS and Affinity run on a Samsung SSD) and easily handles any image editing tasks including merging large HDR photos using tools like Photomatix.
  12. So far the new beta works well for me. Thanks for your efforts
  13. The inpainting brush works again as expected, at least for me. It looks like we are getting somewhere
  14. After a bit more testing I can confirm that the first issue does indeed not occur with all exr files but so far I've been able to reproduce the described behaviour with several of my exr files, not only with the one I took the screenshots from. I uploaded the corresponding exr file for you (the one from the screenshots). The mask issue on the other hand is reproducible with each and every of my exr files. I don't need to press any keys or do anything specific. Just opening the file, adding a mask, drawing some lines on the mask and increasing or lowering the preview exposure afterwards does the trick. 20170708_Rheinfall_HDR_Merged.exr