|
yeah, the raw values come straight from the sensor and the post-processing you do on it mirrors the processing the camera would do internally: debayer, anti-alias, a matrix from the camera manufacturer that converts sensor values into linear light, sharpening. if you write your own raw decoder you can do have this fun yourself. lots of film and tv people were snooty about bayer pattern for a long time because in theory you're losing chroma resolution but it really does work extremely well (and also our eyes don't give a poo poo about chroma resolution). making debayering better in code turned out to be easier than maintaining accurate optical beam splitters for 3-ccd. foveon sensor is neat but it's more complicated to make, more expensive and debatably higher quality - sticking another object in front of your green sensors isn't going to help low-light performance. lightfields are very cool but permanently five years away
|
#
¿
Jan 5, 2022 10:53
|
|
|
|
| # ¿ Apr 20, 2024 02:15 |
|
|
echinopsis posted:
the "develop" stage is moving the image from bayer pattern into RGB, after which you lose the ability to do certain things but you shouldn't necessarily lose dynamic range. adobe lets you click the format text at the bottom of the window and bring the image data into Photoshop as 16-bit fixed point (the default is 8) which should be able to preserve the full range of any camera raw, assuming you don't wildly blow it out.
|
|
#
¿
Jan 24, 2022 20:37
|
|
|
i'd have thought srgb was still pretty dominant for web/desktop even if p3 support has expanded.
|
|
#
¿
Aug 11, 2023 16:23
|
|
|
if you're shooting raw then it's not applying any transform to the data until you get to lightroom, it's just tagging the image with what it reckoned at the time. if you want everything consistent + correct shoot a blank piece of paper (or, say, a macbeth chart) in the light you're in as part of the set.
|
|
#
¿
Jan 21, 2024 11:23
|
|