Mithel

Members
  • Content count

    18
  • Joined

  • Last visited

  1. Oh??? Thank you. Yes, I think I switched it to always work with 32 bit (couldn't see any disadvantage to 32 bit). I just checked and sure enough, that was it. Thank you!!!
  2. Why is the "bilateral blur" filter no longer available in v1.5.2 on Windows? It used to work but now it's greyed out.
  3. Could the software please remember the last used directory separately for opening and for exporting. A frequent workflow for me is: 1) Open Image 2) Edit Image 3) Export Image (repeat many times) It's a waste of time to have to navigate back and forth between my "originals" and my "export" directory for every photo I edit. Export should remember the last directory I exported to and this should not interfere with remembering the last directory I opened a file from. This is a very simple software change but would save users a lot of time.
  4. ^^^^ I followed up on my thought. With those Develop Assistant options set to "take no action" the load time was twice as fast (half the time)! Someone might want to independently test my results I also turned "retina" rendering to lowest quality (fastest).
  5. I agree, I'd assume that Affinity is not displaying any preview. They are completely getting the image ready for post processing as they load it. Unfortunately that gives the user the impression the load times are horribly slow. I loaded up the same image side by side in Affinity (no adjustments) and in Irfanview and there is a noticable visual difference which I'm sure is due to the "Develop Assistant" doing several things: "Apply lens corrections", "Apply color reduction" (noise) and applying the tone curve. Perhaps if they didn't apply those during loading we'd have a far more responsive app. Then they could give us a button to easily apply those if we desired them.
  6. Hardware is usually not the best solution. A bit of software work can usually improve performance far more than hardware can.
  7. If that is true then the JPG preview image is a nice full resolution excellent quality image.
  8. It certainly spikes all of my CPUs (i7) but since loading a RAW file is a blink in other software, my guess is that Affinity is doing "too much" analysis and set up during load. After watching Affinity memory usage during a RAW load, it's impressive that Affinity goes from using 500 MB to using 2.5 GB of RAM to load a single file! And a second file sends it up to 4.5 GB. Thus 2 GB per image! Good thing I have 32 GB of fast RAM! Irfanview goes from 2 MB to 114 MB. Trivial memory usage! Perhaps Irfanview is only loading the JPG preview not the full RAW file?
  9. I'm sure the Affinity developers are working on this as they have said, but I'd like to chime in (and be notified when a fix is made) too. I use Nikon (NEF) raw files and load times (from SSD on a fast system) are about 10 seconds. All other software (Irfanview, Aftershot Pro 3) loads these in a "blink" (too fast to measure). This is an important concern for many users and potential users so hopefully it is getting a lot of attention. This is an operation that is done EVERY time a photo is worked on, any other feature may or may not be used on a photo but this is something we encounter 100% of the time we use Affinity (which I love).
  10. Once you've edited the low and high frequency layers how do you merge them back into being a single pixel layer that you can then do more editing on?
  11. Overall the tutorials are fantastic and an awesome feature of Affinity. However the "Raw: Developing Images" tutorial has a lot of "click on the Chromatic Aberration Reduction will reduce chromatic aberration". Uh, well, if the viewer doesn't know what chromatic aberration is then this doesn't teach them anything (same critique applies to most of the rest of that tutorial for even simple things like "contrast" which probably everyone actually knows what contrast is)
  12. I'm also interested in "Skin Smoothing". PaintShop Pro has a "skin smoothing" tool that makes this process downright trivially simple (and thus fast and easy to do). Apparently I have to research and study "Frequency Separation" (a completely non-intuitive term).
  13. Excellent tutorial, very cool concept! Thanks for mentioning this tutorial.
  14. It would be nice if we could set the default resample method when exporting files. As it is now every time I export an image as a JPG, I have to change the resample method from "Bilinear" to "Lanczos 3 Non-Separable".
  15. It's poor wording, but a very minor issue compared to other things that could be addressed.