Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

More Windows on ARM C1 results

Comments

6 comments

  • Ulrich Roxburgh

    Ignore that. I found out if I regenerated the preview, the problem goes away. Sigh. I guess this means I need to regenerate all previews. At least its fast on this device.

    0
  • Ulrich Roxburgh

    Yeah me too. And if they worked on implementing the AI portions using the new AI chips....

     

    0
  • Ulrich Roxburgh

    Sigh. It looks like there is definitely still a bug here. I've had a few photos where the AI mask seems to work, but most of them fail with the lace like highlights, and inconsistent generation of the mask. Very frustrating. I'll put in that bug report tomorrow.

    0
  • Ulrich Roxburgh

    Some further testing shows this is all to do with the preview. When you edit a photo at anything less than the size of your previews, C1 does not reference the original at all, it uses the Preview. If you are using the AI brush at this zoom level that does not work properly on a Windows on ARM device. However, if you zoom in to 100% and use the AI brush on the same photo it works perfectly, because at this zoom level C1 uses the original file.

    0
  • Walter Rowe
    Moderator
    Top Commenter

    This is great info. I hope you will provide it to Capture One in a support case.

    1
  • Ulrich Roxburgh

    Some further results (positive this time). I do most of my editing directly on my laptop, but I do also edit on the widescreen monitor I use for work. As a result, I had set my previews to 4K resolution, and its these previews that were causing problems with the AI Smartbrush. I wrote above how when you zoom in to 100% (when C1 will use the photo directly, and ignore the preview), it all works. 

    Anyway, last night I changed my preview generation size to 2880 and regenerated a couple of years of photos. Now when I try to use the AI brush on these photos they also work perfectly. So, it looks like the problem only occurs at these higher preview sizes. I'll probably do some more tests, but I will go ahead and raise a support case to C1 about this.

    0

Post is closed for comments.