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. ⚠️

Process Recipe full of noise and artefacts

Permanently deleted user
Dear users,

Maybe I am doing something completely wrong, is my MacBook Air not up to this task or another reason. I made a process recipe. When I press "process", the photo comes out full of artefacts, noise etc. This didn't happen before. I already processed some photos without a problem. My recipe is JPEG, Quality 80, Adobe RGB, Resolution 75px/in, Scale Long Edge 2000px, no output sharpening. MacBook Air 2017, OS 10.15.3.

Thank you very much in advance for your help.
0

Comments

9 comments

Date Votes
  • Permanently deleted user
    Hi,

    This is an issue which has been discussed very often. Maybe you could first try setting the harware acceleration to "None".
    Robert
    0
  • Permanently deleted user
    Hello Robert,

    My apologies for not looking hard enough into this issue in this forum. I sincerely appreciate your quick reply. You have helped me a lot, because this has taken care of my problem.

    Thank again!

    Kamiel
    0
  • David Graeme-Baker
    Can someone direct me to where this subject has been discussed before - can't find it.
    I recently had 60 Raw images I wanted to process to JPEGs and 20 of them came out solid black - not a good look.
    Used a standard JPEG recipe from the list but it failed. Took several goes to get it to work and I still can't work out what went wrong
    0
  • Paul Steunebrink
    Pixcels wrote:
    Can someone direct me to where this subject has been discussed before - can't find it.
    I recently had 60 Raw images I wanted to process to JPEGs and 20 of them came out solid black - not a good look.
    Used a standard JPEG recipe from the list but it failed. Took several goes to get it to work and I still can't work out what went wrong

    Maybe hardware acceleration did not do its work properly. Switch to Never (for processing at least) and try again.
    0
  • David Graeme-Baker
    Thanks Paul - that does seem a possible cause.
    For those like me who didn't know how to turn off "Hardware acceleration";
    in Capture One go to
    Preferences -> General->Hardware Acceleration (Open CL for) and in the Display and Processing tabs select "Never".
    Hope that helps
    0
  • SFA
    Pixcels wrote:
    Thanks Paul - that does seem a possible cause.
    For those like me who didn't know how to turn off "Hardware acceleration";
    in Capture One go to
    Preferences -> General->Hardware Acceleration (Open CL for) and in the Display and Processing tabs select "Never".
    Hope that helps


    It would be worth checking for updated GPU drivers.

    Or, if you have the latest drivers installed, try going back to a previous driver. Sometimes it helps.


    Grant
    0
  • Paul Steunebrink
    SFA wrote:
    Pixcels wrote:
    Thanks Paul - that does seem a possible cause.
    For those like me who didn't know how to turn off "Hardware acceleration";
    in Capture One go to
    Preferences -> General->Hardware Acceleration (Open CL for) and in the Display and Processing tabs select "Never".
    Hope that helps


    It would be worth checking for updated GPU drivers.

    Or, if you have the latest drivers installed, try going back to a previous driver. Sometimes it helps.


    Grant

    Grant, for Windows this is good advice, but for Mac users, they are not aware of different versions of those drivers as they come automatically with the operating system and are not installed separately. 😉
    0
  • SFA
    Paul_Steunebrink wrote:
    SFA wrote:
    Pixcels wrote:
    Thanks Paul - that does seem a possible cause.
    For those like me who didn't know how to turn off "Hardware acceleration";
    in Capture One go to
    Preferences -> General->Hardware Acceleration (Open CL for) and in the Display and Processing tabs select "Never".
    Hope that helps


    It would be worth checking for updated GPU drivers.

    Or, if you have the latest drivers installed, try going back to a previous driver. Sometimes it helps.


    Grant

    Grant, for Windows this is good advice, but for Mac users, they are not aware of different versions of those drivers as they come automatically with the operating system and are not installed separately. 😉


    Good point Paul but at the back of my mind I thought I had seen some advice that might suggest a way through that limitation. Is there no way at all to introduce updated drivers between releases? Or maybe revert to earlier versions?

    If not I suppose it is a matter of wait and see what comes up in the next release. Perhaps someone could check the beta?

    Of course if hardware acceleration is not a significant factor in a user's workflow leaving it off is probably going to be fine.)

    ( 10.15.3 is the OS also known as "Catalina", right?)

    Grant
    0
  • Paul Steunebrink
    SFA wrote:
    ( 10.15.3 is the OS also known as "Catalina", right?)

    That is correct, macOS 10.15.x a.k.a. Catalina
    0

Post is closed for comments.