Canon's latest horror: Black pixels in 5D II

Discussion in 'Canon' started by RichA, Dec 9, 2008.

  1. RichA

    RichA Guest

    RichA, Dec 9, 2008
    #1
    1. Advertisements

  2. RichA

    RichA Guest

    No, actual black spots (smaller than the images of the lights) on the
    right hand side of each light image. More visible on the lights in
    the middle and on the right of the image.
     
    RichA, Dec 9, 2008
    #2
    1. Advertisements

  3. RichA

    Paul Furman Guest

    The strange thing is square highlights on the x-mas lights. It looks to
    me like the 85/1.2L's even-counted non-rounded 8 aperture blades are
    doing funny things and that causes the black spots. It is a challenging
    scene.

    --
    Paul Furman
    www.edgehill.net
    www.baynatives.com

    all google groups messages filtered due to spam
     
    Paul Furman, Dec 9, 2008
    #3
  4. RichA

    Colin.D Guest

    This effect may be present in other cameras as well, but just not
    discovered yet.

    It looks to me like the saturated highlights are causing linearity
    problems in the pixel amplifiers, depressing the following pixels
    towards black until the amplifiers recover a few pixels later.

    If so, I think this is a major, as I believe the amplifiers are part of
    the CMOS sensor design.

    Colin D.
     
    Colin.D, Dec 9, 2008
    #4
  5. RichA

    RichA Guest

    That is, if it didn't appear with other lenses, which it does.
    Interesting effect, whatever the cause.

    http://forums.dpreview.com/forums/read.asp?forum=1032&message=30276248
     
    RichA, Dec 9, 2008
    #5
  6. RichA

    RichA Guest

    When did you buy one?
     
    RichA, Dec 9, 2008
    #6
  7. RichA

    RichA Guest

    Check this out:

    http://forums.dpreview.com/forums/read.asp?forum=1032&message=30277522
     
    RichA, Dec 9, 2008
    #7
  8. RichA

    RichA Guest

    RichA, Dec 9, 2008
    #8
  9. RichA

    ASAAR Guest

    No need to apologize. Sometimes replies contain plain text and an
    HTML copy of same. My newsreader is configured to display the text
    and represent the HTML portion with an icon which can be expanded
    into text if desired. I checked all three of your replies in this
    thread (including the one Alan replied to) and none showed any HTML
    or an HTML icon. If you read enough of his replies you'll see that
    he is extremely quick to criticize others. Alan's request for you
    to stop using HTML may be due to an accidentally triggered knee-jerk
    reflex, or possibly due to his computer being infected by a virus.

    Or maybe my computer has been infected and the virus is stripping
    HTML out of newsgroup articles. Maybe some others will describe
    what they saw in your message that supposedly contains HTML. :)
     
    ASAAR, Dec 10, 2008
    #9
  10. RichA

    Paul Furman Guest

    I've seen multiple examples with the black dot on the right. It does
    seem to be a sensor reading/processing issue not optical as I'd thought.

    --
    Paul Furman
    www.edgehill.net
    www.baynatives.com

    all google groups messages filtered due to spam
     
    Paul Furman, Dec 11, 2008
    #10
  11. RichA

    ASAAR Guest

    Suggestion forwarded to author. You've just been nominated for a
    MacArthur Grant.
     
    ASAAR, Dec 11, 2008
    #11
  12. RichA

    Paul Furman Guest

    My somewhat vague understanding:
    The charge is pulled off the sensor in one direction & CMOS chips do
    some processing at each pixel, Colin says it's amplifying (ISO
    adjustment). Turning off some processing options seemed to fix it in the
    dpr discussion, was that a shadows & highlights type curve, something
    applied to the raw file (probably not)?

    --
    Paul Furman
    www.edgehill.net
    www.baynatives.com

    all google groups messages filtered due to spam
     
    Paul Furman, Dec 11, 2008
    #12
  13. That's certainly just cause to jump down someone's throat, then, isn't
    it, Mr. Ambassador??
     
    John McWilliams, Dec 11, 2008
    #13
  14. RichA

    Paul Arthur Guest

    No, it's not. His post did not contain HTML, ergo if you saw HTML your
    newsreader is broken.
     
    Paul Arthur, Dec 11, 2008
    #14
  15. RichA

    Paul Arthur Guest

    I repeat: his post was plain text. Anything you saw that didn't look
    like plain text was produced by your newsreader.
     
    Paul Arthur, Dec 12, 2008
    #15
  16. RichA

    ASAAR Guest

    You rarely do anything but argue, even when you're wrong. Now
    you're changing what you "saw" from HTML to "style" tags.
     
    ASAAR, Dec 12, 2008
    #16
  17. RichA

    ASAAR Guest

    You rarely do anything but argue, even when you're wrong. Now
    you're changing what you "saw" from HTML to "style" tags or
    whatever. Whether viewing the text from G Paleologopoulos's
    messages in raw mode or with a hex editor, there is nothing to be
    found but plain text. No HTML. No tags. No whatever.

    That does not appear to be the case. The last text appearing in
    the message was (not counting quotes and substituting "<CR>" and
    Did the HTML or whatever precede this or follow it? Oh wait, you
    won't see this, since just like SMS, you use your KF to avoid having
    to face reality, or see anyone getting on your case when you're
    either wrong or obnoxious.
     
    ASAAR, Dec 12, 2008
    #17

  18. You're right; I 'overspoke'. However, oh. well, nevermind. .....
    Eeeewwww. If it's what I think you mean.

    "Homey don't play that"
     
    John McWilliams, Dec 12, 2008
    #18
  19. Check out my post up thread. There's a setting in the headers that some
    newsclients pick up and make the display different from plain plain text.

    I thought it was simply unwelcoming to have pointed it out, anyhow, I
    hope this is done.
     
    John McWilliams, Dec 12, 2008
    #19
  20. RichA

    ASAAR Guest

    I guess you're referring to
    You may be on to something there if it's that charset that you're
    referring to. But I noticed several odd things about this. One
    informative web page indicated that the windows-1253 encoding might
    be used, with a caveat :
    http://www.cs.tut.fi/~jkorpela/unicode/greek.html

    and on another web page there was the suggestion that the use of
    windows-1252 (2, not 3) should be avoided.


    http://www.velocityreviews.com/forums/t300384-disadvantages-of-using-windows1252-codepage.html


    Oddly, I noticed that code pages aren't constant, and I wouldn't
    expect people to frequently redefine the character sets used by
    their newsreaders. G Paleologopoulos uses OE, sometimes with
    windows-1252 and sometimes with windows-1253. Paul Furman uses
    Thunderbird 2.0.0.18 (Windows/20081105) and his some of his replies
    use windows-1253 while others use the ISO-8859-1 charset. Alan uses
    the same version of Thunderbird as Paul, but for the Mac. and
    appears to use only ISO-8859-1, but when using a previous version
    (Thunderbird 1.0.6) switched between ISO-8859-1 and windows-1252.
    Perhaps the switching is due to having and using several installed
    newsreaders, each with slightly different configurations.

    Some people see helpful advice as negative criticism, others
    don't. Trying to help is always a gamble, risking unintended
    offense, although with some it's no gamble - you know in advance
    that they'll probably take offense. Someone should write a song to
    help decide what to do, maybe ending with lines like those from The
    Gambler's* "You gotta know when to hold 'em, know when to fold 'em.
    Know when to walk away, know when to run."

    * lyrics attributed to Bobby Bare, Kenny Rogers, Don Schlitz and
    possibly others.
     
    ASAAR, Dec 12, 2008
    #20
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.