Jump to content

Jeroen

Members
  • Content count

    60
  • Joined

  • Last visited

About Jeroen

  • Rank
    Member

Recent Profile Visitors

377 profile views
  1. Hi Justin, Interesting.I can see that NaN values might certainly cause erratic behaviour. The question of course is where they come from. You are correct in that I developed from a raw file, and I did it in AP. I do not keep records of develop adjustments. Normally I tend to keep development settings simple and leave most of the work to the Photo persona, but I do not remember exactly what I did here. I can provide the raw file though, if that might be of use. It is a Canon .CR2 file. Let me know if you would like me to. Best regards, Jeroen.
  2. I could not replicate it, but I recall having noticed similar behaviour at other times. If and when it reoccurs I will report again, with as much information as I can.
  3. See attached image. The HSL adjustments and WB adjustment suddenly stopped working. The Levels adjustment still worked.I made a recording of the "HSL lucht" adjustment not reacting, also attached. Maybe it is relevant that I have layer masks on the HSL and WB adjustments, and not on the levels adjustment. After saving and reloading the project, the problem had gone away. I therefore suppose the project file would be of little value in diagnosing the issue, but I kept it safe and can upload it if requested. For the record, I had Metal compute activated and the project is in 32 bit HDR. Schermopname 2019-07-12 om 11.08.02.mov
  4. I uploaded "About this Mac' to the Dropbox link you provided. Please let me know if I can be of further help.
  5. Uploaded. Please let me know if I can be of further help.
  6. Uploaded. Please let me know if I can be of further help.
  7. Thanks for the encouragement. I now have a workaround. Yet, I may misunderstand you here... but it seems to me there is definitely something wrong at the moment. I have a 2019 Mac with all software up to date. You are certainly not suggesting that Metal support is fine as it is, and thus needs no fixing? Then, why is it not working as expected?
  8. Disabling Metal compute does indeed fix the issue. I have uploaded the file to the link you sent me.
  9. In attached project, the following shows artifacts appearing when applying a live denoise filter, even after resetting the filter: With the denoise filter deactivated the artifacts disappear: Exporting to jpg of the project with the filter active also shows artifacts, although different ones: Exporting with the filter deactivated gives a clean picture. The project can be closed and reopened, and the behaviour remains. Jeroen. IMG_2333_Golf.afphoto
  10. Quite right. I now also understand why the lines appeared only after cropping. This has to do with the display threshold value for the baselines. Issue completely solved. Thanks.
  11. I changed the zoom level up and down. The striping changes with it. Attached is a picture of zoom level 4. If I zoom further out, it does not look like pixels: So it is not in the image, which explains why it is not in the jpeg. It must be a sort of display issue, but one that scales with the zoom level. The lines are very neat. The thickness of the lines remains constant.
  12. Attached is a screen shot of AP 1.7, with a picture loaded. It displays with horizontal stripes: I am not aware of having created these, nor do they show when I export the file to jpeg: I have not been able to reproduce the issue, but I have kept the history saved with the file. One unusual thing - for me - is that I applied tone mapping. The problem appeared after I cropped. Affinity Photo 1.7.0, iMac (Retina 5K, 27-inch, 2019), Radeon Pro 580X 8 GB, MacOS 10.14.5 Mojave
×

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.