Zum Hauptinhalt gehen

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

TIF from NEF

Kommentare

2 Kommentare

  • Drew Altdo
    Hello,
    Discrepancy in all aspects is to be expected when you up-res your image by such a drastic degree. You are currently shooting a 12 Bit RAW file and then turning it into a 16 Bit file. The color value that you see in Capture One is your RAW data at 12 bits, while the value seen in your processed file is the the result of stretching that 12 bits of data. Your camera can only collect 4,096 colors (2 to the 12th power), but the image you are creating has 65,536 colors (2 to the 16th power). That's quite the jump.
    0
  • Florin Coter
    Hi Drew,
    Thank you for the answer.
    I do not want to up-res, and did not know what is happening since the user manual says nothing on this issue. I wanted the image saved non lossy. That's all. If a linear stretch is done one ends with 1 bit error per channel and 1.7 per gray level. I can live with this and I would have not spent time writing this message. I have a PhD in Physics and about 5 years of image and signal processing experience. I have never encountered a NON lossy file format translation algorithm that modified ANY bit value. NEVER. ALWAYS, but ALWAYS the extra bits of resolution are zero padded. No less, no more info. It is hard to believe that the best raw processor (in my opinion) will modify the file contents in a non lossy format in such a strange way (to say the lest) without informing the users. If this is the case, Phase one is downgraded to the best viewer, at most. Certainly, I have never encountered such undocumented content modification with CS or Bible...
    I would like to kindly ask for a second technical opinion from Phase One, or at least to explain how we can save a 12bit image in a 16bit image without any change of info using your product.
    Kind regards,
    Florin.
    0

Post ist für Kommentare geschlossen.