Click here to go to the first RED TEAM post in this thread.   Thread: precise R1 sensor pixel size needed... Mr Nattress ?

Reply to Thread
Results 1 to 6 of 6
  1. #1 precise R1 sensor pixel size needed... Mr Nattress ? 
    hi people

    I'm hoping to find a definitive number for the exact pixel size of the R1 in mm.
    I've done quite a bit of searching but there are confusing numbers out there...
    according to the RED ONE specs the R1 has a pixel size of 0.005419922mm
    according to jlf.com it is 0.005400391mm
    but according to another post it is 29microns square which gives 0.005385165mm

    I don't need the actual photosite ? size just the distance between each pixel centre, so something very close to one of the above numbers , I just need to know which one to believe !
    I realise this is kind of ridiculous but it's for some rather arcane trig i'm working on and the numbers are being amplified to a point where those decimal places really start counting...

    thanks../daniel
    Reply With Quote  
     

  2. #2  
    Well, I'm at a loss as to what calculations you could be doing that would require such a level of precision... Short of designing your own alternative OLPF or sensor mask. But you don't need the photosite well size, just the gross pixel dimensions. That said, I'm going with the first number you specified -- 0.005419922mm. And don't worry about the 29 microns square, someone was just rounding it off.

    Anyway, got me curious... What is it that you could be doing?
    - Jeff Kilgroe
    - Applied Visual Technologies, LLC | RojoMojo
    - EPIC-M Package Available! Over 1TB SSD media, RPP's & more.


    List of all current RED software tools.
    Reply With Quote  
     

  3. #3  
    Senior Member
    Join Date
    Sep 2007
    Posts
    114
    Respectfully, I don't work for RED, and I'm certainly not trying to stifle discussion, but your question seems to be something that is intrinsically part of the math that makes up the RED images. You should probably talk to RED directly, since it seem dangerously close if not over the line of IP.
    Reply With Quote  
     

  4. #4  
    Senior Member
    Join Date
    Aug 2008
    Posts
    3,509
    Reminds me of the math professor who gave a physics student and and engineering student a thought experiment to solve:
    " Imagine you both are at one end of a long hall and there is a beautiful woman at the other end. You each take turns walking toward the woman, but you can only go half of the remaining distance each turn. The one who gets there first gets to have sex with her. Who wins?"
    The students both begin madly crunching the numbers on their calculators. Finally the physics student throws his hands up in exasperation; " Impossible, you never get there!"
    The engineer says, "Yeah, but I can get close enough."
    Reply With Quote  
     

  5.   This is the last RED TEAM post in this thread.   #5  
    I've always done the math with 5.4 microns

    Graeme
    www.red.com - 5k Digital Cinema Camera
    Science enables stories. Stories drive science
    FLUT™, Image Processing, Colour Science and Demosaic Algorithms, REDRAY 4K delivery
    Reply With Quote  
     

  6. #6  
    yeah that's what I've been using, but It's very reassuring to know that's what you use Graeme !

    and for those that were interested. I'm working on a script to control a moco head.
    The idea is that I can plug in the focal length and capture resolution and the script will do the rest (single pixel FOV !)
    you'd be surprised how much of an effect those decimal places have, especially with long lenses.

    ../daniel
    Reply With Quote  
     

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts