メインコンテンツへスキップ

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

v 3.7.8 40D raw conversion black lines along long side

Mike Bailey
This has been a bug in the past with other cameras and conversions, and I don't know why on earth I didn't notice it at once. Conversions of 40D raw files produce black lines along the long side of the image. The solution in the past for handling this was for Capture One to throw away the last 8 lines of pixels when converting, i.e. like with the 5D instead of 4368 x 2912, you get 4368 x 2904. For the 20D you instead of 3504 x 2336, you get 3504 x 2332.

This is under both Windows 2000 and WIndows XP.

With the 40D, which nominally should be 3888 x 2592, a file of 3888 x 2592 is created, BUT the lines 2588 through 2592 are bad. 2588 has no color, 2589 is a series of black pixels and gray pixels, 2590, 2591, and 2592 are all black.

It looks like it isn't being handled any better than in the past with other cameras, but this time the last 4 to 8 lines of pixels aren't thrown away to resolve this internal bug with Capture One. Lightroom (and others) manage to produce the full 3888 x 2592 correctly.

I'm sure others have seen this, but wonder why it hasn't been reported. I did file a bug report.

Did anyone ever figure out a workaround other than cropping after developing the file(s)?

Mike
0

コメント

9件のコメント

日付 投票
  • Paul Steunebrink
    Just curious, does cropping before development also helps (if yes, you could copy the crop to all images)?
    0
  • Mike Bailey
    Paul,

    Good idea... I normally do not crop prior to development, so this never occurred to me. The preview, zoomed or not, does not show the problem, and trying to crop several lines off one side is rather imprecise, but it is doable and seems to work. I just tried and got a 3888 x 2588 sized developed TIFF with the screwed up lines left off.

    Mike
    0
  • Paul Steunebrink
    Mike,
    To crop before development is only a workaround, but if it works for you it save you time and perhaps irritation. Worth a lot too 😄
    The preview is just a rough estimation of the image. Not all algorithms are processed for reasons of speed. The focus windows is much more accurate. Maybe you can see the processed black lines in there.
    0
  • Janne
    I haven't been able to re-produce this bug. What firmware are you using?
    0
  • Mike Bailey
    Thanks Paul... And to answer Janne, it was firmware version 1.0.5, the latest. I also reproduced the same results using a CR2 file kindly posted on outbackphoto.com from an earlier version (1.0.3) of the firmware.

    However, it is all a moot point. Despite the glowing adoration by most for the 40D, I have found the noise worse even than my 20D, and of course far worse than my 5D. Image quality suffers as a result. I have processed enough files using several different raw converters to compare the results, including Capture One, to come to the conclusion that the 40D won't do as a backup for my 5D, or a replacement for either of my 20D bodies. Looks like another 5D for me after I return this 40D. Disappointing, but that's my opinion from what I see.

    Mike
    0
  • Janne
    I agree on the noise issue. I was hoping some improvement in that area thanks to the new DIGIC3-processor but so far the results are less than impressive.

    Still, I haven't been able to re-produce this black line You mentioned?
    0
  • sebi
    the noise isnt worse than previous bodies, except the gain is pushed at lower iso, so you'd have to compare an iso 100 on the 40d with a iso 400 on a body like a 400d or 20D.
    try this page http://www.astrosurf.com/buil/eos40d/test.htm
    0
  • Janne
    Sebi, thank you, that was an interesting link.
    0
  • Janne
    Interesting enough, our 40D now creates the black line mentioned before.
    0

投稿コメントは受け付けていません。