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

Colour error on pixels along right image border

Per Karlsson
I have noticed a very strange colour error that appears sometimes on the very last pixel on the right hand border of an image.

I start with a Canon 5D mk2 cr2 file.

I process it with some adjustments with Capture One. Along the right-hand border the last pixel is wrong. Here's an example:
http://www.bkwine.com/wp-content/upload ... ureOne.tif

This is a small crop of the upper right corner of the image. Apart from being cropped it is in full size.

As a comparison, here's how it looks if instead I process it with Photoshop Camera Raw, approximately the same crop:
http://www.bkwine.com/wp-content/upload ... eraRaw.tif

If I inspect the cr2 file in Capture One at full size (or more) I can see no such coloured pixels along the border.

This seems to appear on random images, not very many, perhaps one out of 20. It seems to appear only along the right-hand edge of the image.

This is very worrying. Do I now have to check the edge of every single develop and crop around 5% of them...?

Any clue what's going on?
0

Comments

23 comments

Date Votes
  • Per Karlsson
    Additional details: It happens on both horizontal and vertical images. But always along the right hand border. It is sometimes one pixel wide, sometimes two pixels wide. It happens more like for 1 in 4 images it turns out. It happens rarely, if ever on low ISO (100 ISO) images.
    0
  • Per Karlsson
    Update:

    Feedback from Capture One tech support:

    Hello, It may be a graphics conflict. Try going to Capture One preferences and turning the hardware acceleration functions from Auto to Never. Then restart and let us know if the issue persists. Thanks,
    Phase One Support
    0
  • Per Karlsson
    Update again, the result of trying the fix suggested by Capture One tech support (my message back to tech support):

    I find this VERY worrying. Imagine what a stock image library would say if they received such images, or even a client…

    To your suggestion:

    I turned off Hardware Acceleration for Processing and then it worked OK, in most cases.

    HOWEVER, in two cases out of the approximately 80 that I reprocessed, there was STILL pixel corruption along the edge. BUT in this case it was not along the right hand edge of the image. Instead the corruption was along the top edge and ONLY close to the corners.

    I am VERY concerned that Capture One can now not be trusted to process images correctly!

    Also, going back, it means that I have to go over I don’t know how many images and check. Thousands…

    It does affect low ISO (e.g ISO 100) images, contrary to what I first thought. It is about one in three images that have this error (before turning Hardware Acceleration OFF). You can only discover the problem if you inspect very closely the images in another application than Capture One after processing….

    1) Doesn’t turning off HW acceleration deteriorate performance, so it is a bad fix?

    2) Since when does this bug exist? How far back do I have to check my archive?

    3) Is there any way to identify which images have been affected, other than visual inspection? (Opening thousands of images will take quite some time…)

    4) Are you working on a real resolution to the problem?

    5) Most IMPORTANT: the problem STILL exist after turning off Hardware Acceleration!!
    0
  • hobie
    I've noticed the same problem with cropped pictures and OpenCL switched on.
    I never noticed that with previous versions of C1, so I think it is a problem only with the present version 7.1.3. As a workaround I move the border of the cropping slightly and process the file again, that removes the error.
    Of course this behaviour is very annoying.
    0
  • Per Karlsson
    Hobie - perhaps your correct. Perhaps it came with 7.1.3...?

    Have had an extended conversation with support that I will share in the following posts.

    But just to summarise:

    This seems to be the cause:

    It seems to be an error with hardware acceleration (OpenCL).

    - I had to turn of HW Acceleration in preferences (for processing)
    - Uninstall the program (according to the lenghty instructions referenced below)
    - reinstall the program

    But I am still not 100% confident.... :-O
    0
  • Per Karlsson
    Next reply from support:

    This is not a bug,


    Oh, yes? It certainly is a horrible malfunction that I just spotted by chance.

    The hardware acceleration function is an option we offer but it does not always work for everyones computer and graphics card. You are not slowing down the program you are just running at normal operation without the added function.


    Not slowing down? So, what does "acceleration" mean?

    Another concern is that your graphics driver may not be up to date which may be why some of the files are experiencing an issue. I would suggest looking into this as well. Here is an article to explain the issue better.

    http://www.phaseone.com/Search/Article. ... nguageid=1


    My graphics driver was up to date so that was not an issue.

    But I still got errors on some images.

    Having turned off HW acceleration the error disappeared on most images but not on all.

    There were still errors on some images but instead of on the right edge it was now on the top edge.
    0
  • Per Karlsson
    From technical support:

    Is this only happening in a specfic session or catalog or have you noticed it in a few sessions now. I would suggest a clean uninstall and reinstall of the software only putting 7.1.3 back on your machine. From there you will need to check your preferences again to make sure the processing for hardware acceleration if set to Never again. Then please try a new session for processing and see if the error occurs again.

    Clean uninstall / http://www.phaseone.com/Search/Article. ... nguageid=1

    Reinstall / http://www.phaseone.com/en/Downloads/Ca ... ro-7.aspx#


    I have only just discovered this problem so I can't say if it is more than one session.

    (The reinstall refers just to Capture One, not to the whole system.)

    Important: there are quite a few things to do to clean up after uninstalling. It's not as simple as just choosing uninstall. Do read the article referenced above!
    0
  • Per Karlsson
    Following those instructions the error seems to have gone away.

    And this was my final comments to support:

    I followed the instruction to do a "clean" uninstall. And then a new installation of 7.1.3.

    I have tested with the two images that previously gave me an error even after having turned HW acceleration off.

    This time they showed no error.

    I have not tested turning hw acceleration on again... (except for display, which is now turned on)

    I also saved and copied back the user config file that was mentioned at the end of the uninstall description. That worked fine and saved me a lot of trouble setting up my custom design.

    So, thank you for helping sorting this out.

    However, I do think it is a problem of yours if this error appears. It is when using Capture One that this unpredictable and erratic error appears and it is your program that will take the flak. So I think you should be concerned and try and find a "solution" even if perhaps it is not fundamentally your problem.

    And I will certainly be nervous for some time in the future that this will happen again and will have to spend extra time double-checking images in Photoshop.

    Anyway, many thanks for your support!


    I do still think this is an issue for Phase One to deal with and to find a solution to.

    How many photographers get this error without being aware of it...? (It's not entirely easy to spot.)
    0
  • Per Karlsson
    All this being said, I was very happy with the fast and helpful answers from support! That in the end sorted it out. (I hope.)
    0
  • Coach
    I noticed this same problem also, a thin row of colored pixels on the right side of the processed images from my Canon 1Dx and 1Ds Mark III. Having had similar problems before with my Canon G12 I figured I had to turn off hardware acceleration. That seemed to have solved the problem, but now the processing is slow. There may still have been glitches that I missed. I didn't notice a problem with release 7.1.2. These things seem to come and go with Capture One....
    0
  • Raymond4
    Hi, checked my 1ds3 images all perfectly ok. Could this be graphics card related. Are you using Radeon AMD graphics? I used to have all manner of glitches trying various AMD cards - latest was HD7870, until I changed back to nvidia.

    C1pro v7.1.3 Win 7 64bit i7 920 12GB ram. Nvidia GTX770 2Gb.
    0
  • Per Karlsson
    Could be so. Yes, I use AMD Radeon HD 7800M Series. Not much to do about it since it is on a laptop (mobile workstation).

    Might be useful for people who experience the problem to report it to support though:
    http://www.phaseone.com/en/SupportMain.aspx
    0
  • hobie
    No, that can't be the reason. I've got this error on a Nvidia GTX 460. OpenCl is working very well with this card, speeding up the processing three times faster than with OpenCl switched off.
    0
  • Per Karlsson
    That's interesting (and comforting for me who's sitting here with an AMD card 😉 ).

    So then perhaps it is an inherent problem with OpenCL. Or with Capture One?
    0
  • Per Karlsson
    One more update on this issue with pixel errors.

    I turned of acceleration for processing but put it on "automatic" for display, hoping that display using OpenCL would not be an issue. (after making a clean reinstall)

    Unfortunately I was wrong.

    Having acceleration on "automatic" for display caused a similar pixel error on two (2) out of 300 images in a recent batch of images.

    When I turned off acceleration for display (and did a new session) it did not generate errors.

    So, I have to turn hardware acceleration (OepnCL) off, put it on "never", both for display and for processing for Capture One to process the images correctly.

    This is a great disappointment.

    Phase One support has been very helpful (!!) in sorting this out.

    But they also say that "it is not a Capture One problem". I disagree. They have built a software (Capture One) that uses a current technology (OpenCL) and when it does the program generates defective images. Can't help to think that it is an issue for Phase One, and for people using Capture One. I hope that Phase One can figure it out so that I can turn on hardware acceleration for a future release...
    0
  • Christian Gruner
    Thank You for Your reports. This is fixed in an upcoming version of Capture One.
    0
  • Per Karlsson
    Christian,

    That would be great! Looking forward to that. Thanks for your feedback!

    -P
    0
  • Per Karlsson
    @ Christian Gr - I see you didn't need the reference I gave you in another post. You were already here!

    To my question:

    You mentioned in your previous message that
    Thank You for Your reports. This is fixed in an upcoming version of Capture One.


    7.1.4 just came out. Is that the "upcoming version" you refer to with this issue fixed or will the OpenCL / hardware acceleration fix come later?

    (It is useful to know when I should turn on HW acceleration again! To do some tests.)

    -Pere
    0
  • Christian Gruner
    [quote="perkarlsson" wrote:
    @ Christian Gr - I see you didn't need the reference I gave you in another post. You were already here!

    To my question:

    You mentioned in your previous message that
    Thank You for Your reports. This is fixed in an upcoming version of Capture One.


    7.1.4 just came out. Is that the "upcoming version" you refer to with this issue fixed or will the OpenCL / hardware acceleration fix come later?

    (It is useful to know when I should turn on HW acceleration again! To do some tests.)

    -Pere


    Yep, this is fixed in 7.1.4
    0
  • Per Karlsson
    That's great! I think I'll start with some tests so that I don't have to go through 1500 processed images again. 😉
    0
  • Per Karlsson
    @ Christian Gr,

    I decided to test.

    I updated to the new version.

    I turned on hw acceleration to 'auto' for display. I did NOT turn it on for processing (that's less important for me). I then processed a batch of some 250 images.

    It was ALMOST ok. None of the images displayed the colour error along an edge that I had seen previously. BUT four (perhaps a few more) of the images had *missing* pixels in one corner. Just two or three or four missing (or grey) pixels so it is quite difficult to spot, unless you are looking for it.

    So, less sever error than before but still an error. Plus more difficult to spot.

    FYI I have filed a follow up message on my previous error ticket to support. (Ticket id 129210)
    0
  • Christian Gruner
    [quote="perkarlsson" wrote:
    @ Christian Gr,

    I decided to test.

    I updated to the new version.

    I turned on hw acceleration to 'auto' for display. I did NOT turn it on for processing (that's less important for me). I then processed a batch of some 250 images.

    It was ALMOST ok. None of the images displayed the colour error along an edge that I had seen previously. BUT four (perhaps a few more) of the images had *missing* pixels in one corner. Just two or three or four missing (or grey) pixels so it is quite difficult to spot, unless you are looking for it.

    So, less sever error than before but still an error. Plus more difficult to spot.

    FYI I have filed a follow up message on my previous error ticket to support. (Ticket id 129210)


    Judging from the data you provided (the group of 2-9 grey pixels in a corner) this is a very different issue from the one you reported first.
    I will look further into it tomorrow.
    0
  • Per Karlsson
    Yes, I agree. It does not look quite the same.

    On the other hand, I have never seen it before. (And I don't know if it will go away if I turn off acceleration. Will have to see how it goes.)

    Also: the previous issue was similar in that it was one row of mis-coloured pixels that always started in a corner. Now it is much fewer pixels but it still starts in a corner and goes along an edge.
    0

Post is closed for comments.