Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Hi MEB, what is going on with the reported issue? Is it planned to be fixed? Let me know please. Regards, Andrzej
  2. Hi MEB once again, for some reasons I was in a hurry writing the above answer, so I would like to add some words now. Normally my projects are rather simple, as I am an amateur photographer and my goal is to get as much as possible from my shots. In other words to get best looking photos. It means I use mainly different adjustments, also losless, using layers, masking etc. Sometimes I duplicate layers and blend them latter. The problem described above I noticed during my normal workflow, which usually contain adjustment layers, but confirmed with the plain, not adjusted picture, as I wrote in the previous post. I would like to point it out once again, that if I open ready 1920x1080 picture, do nothing and than export it with different algorithms settings, all is correct, as expected. If it is a file resized in AP to the same 1920x1080, than it happens (but not always!).
  3. Hi MEB, It doesn't depend on layers, I just confirmed this. I opened the file, cropped to 16:9, resized to 1920:1080 and exported, without any adjustments. No adjustmsnts, no leyers. The results as above.
  4. I’m sorry for the very long story, but I didn't find the way to shorten the description of noticed problem. My final steps of jpg image processing are cropping, usually to 16:9 proportions, resampling to 1920:1080 and sharpening using the filter best suited to the photo. Next I export the picture to disk again as jpg, using export command and don’t change the picture size during export. Unfortunately I noticed, that sometimes the saved pictures looked in Faststone (or any picture viewer) are softer, than before export, viewed in AP. It is particullary obvious on pictures containing many tiny, sharp details. The difference is not big, but noticable. It is annoying, because the final result is a bit unpredictable in terms of sharpness and can differ from what I got in the edition. I assumed, that as long as I don’t change the picture size on the export, the choice of the algorithm displayed in the export dialog box is irrelevant and it was left “Bilinear” by default. I was wrong. In most cases the results were the following: nearest neighbour – sharpest, bilinear – softest, Biqubic and Lanchos 3 Separable between them; Lanchos 3 Non-separable very oversharpened; What is weired, there are photos, which are not suffer from this phenomenon, but I could’t find any regularity. Trying to better understand it I did some additional tests: 1. I prepared exactly 1920:1080 picture in another software and opened it in AP, than exported it as is, choosing all algorithms from nearest neighbour to Lanchos 3 Non-separable. There was no difference between exported files - as expected. 2. I opened the jpg picture 4928x3264 (the original size from 16 Mp camera) and resampled it to 1080 high, getting 1630,6 width and: a. Exported it with no any change, getting different looking pictures, depending on the algorithm set in the export dialog box, as described above. I can eventually understand it: the width of the final picture (displayed in the export dialog box) is 1630 instead of the initial 1630,6, so perhaps there can be any role of the resampling algorithm. For confirmation I did the following: b. In the Resize Dokument dialog box I changed 1630,6 to 1630 (1080 hight left unchanged) and repeated steps from 2a), this time getting identical results for each exported file, despite of the algorithm. It can confirm the conclusion from the point above. It seems there is nothing wrong in the results of these tests, contrary to the normal workflow, described above. I hope I’m right posting this description in the Bug section, because there is something wrong from my point of view. I hope you will find the way to fix the problem and I will be able to stop worry about the final result of my processing. Best regards, Andrzej
  5. The list of fixes looks impressive, but unfortunately it still crashes with Neat Image plugin. Best regards and good luck with next fixes, Andrzej
  6. Some nice improvements, but still crashes with Neat Image plugin.
  7. Affinity Photo ver. worked fine with the latest relase (compatible) of the Neat Image plugin. After upgrading to AP crashes. Uninstalling and installing the previous version of AP makes it working again. Andrzej Edit: I just noticed, that the same crash occurs, when use denoise filter of Affinity Photo.
  8. Sean, you were right that it has something to do with two monitors. I did a lot of tests and I have a lot of observations. I can force the AP working properly, but in a strange way. I will do another tests and will present the results after sorting them out. This behaviour was not observed on my old computer with Win 7, AP1.5, all betas and AP1.6, also working with two monitors. Andrzej
  9. Hi Sean, thank you for the reply. Yes, I have two monitors (laptop plus the bigger one). I did what you adviced, but unfortunately nothing has changed. Andrzej
  10. I installed AP 1.6.089 on the new computer with WIN 10 OS. It worked fine for few days, even today. I installed DxO Optics PhotoLab, which worked fine. After that I noticed strange behaviour of my AP: If I choose any adjustment tool/adjustment layer/filter it adds the new layer and a new positions in the history, f.e. "Add level adjustment" and "Set adjustment parameters", like it should. Unfortunately I can do nothing, because there is no visible corresponding tool box with sliders. If I choose Filters->Sharpen->Unsharp Mask or Clarity, cursor changes shape and a little pice of line (?) is displaye under it and nothing happens. I played before with Liquify Persona a little and could deform a picture - nothing happens with the picture now. These are problems I noticed, I'm not sure if it is all. As I mentioned I noticed this strange things after installation of DxO Optics PhotoLab. I do not claim it was the reason, because both programs worked fine on my old computer (Win7). On the new computer AP worked fine with DxO Optics Pro 11. What I did: Uninstalled DxO Tried repair function from AP installator Uninstalled AP Cleaned registry with CCleaner Installed AP again I rebooted the computer many times of course. All my efforts did not produce any results. What more should I do??? Please help! Andrzej A little suplement: I just remembered, that prior to the notice of the described problem I deleted all cropping presets. Maybe it has something to do with it?
  11. It highly depends on the resolution. I checked it roughly in function of Mpx and the results are as follows: for 2 Mpx about 1 sec, for 14 Mpx about 20 sec, for 16 Mpx about 110 sec. This is not the linear function. For 24 Mpx f.e. it may take a long long time. I used this function several times in latest betas, but always for 2 Mpix, so I didn't notice any problem.
  12. Here about 1 sec on the 1920x1080 file. Perhaps will be longer for higher resolution files. Maybe there is a OS problem?
  13. Yes, Depth of Field, both Elliptical and Tilt Shift. I checked it once again now and both work fine. Win7, i5, 8 GB RAM.
  14. Works perfect here, both in beta and in the final 1.6 version.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.