(embiggenable)
(embiggenable)
(embiggenable)
(embiggenable)
I TOOK AN OATH THAT I WAS NOT GONNA do it but I gave in and did it nevertheless. Made a few iPhone Apple PRORAW pictures just to see what’s what and, damn it, it is even worse than I thought it might be. That is to write, the files are so superior to iPhone jpegs-which are very good-that I am now doomed to making PRORAW files forever.
What that means is extra processing steps-mainly adding CAMERA RAW processing to the workflow-and, in the case of making 48mp originals (main camera only), the resulting 210mb files will definitely require increasing my storage / backup needs. Fortunately, it seems that my desktop Mini Mac is up to the task of handling the bigger files. Although, that written, I have set my camera format preferences to making12 mp files - I’ll save the 48mp format for special picture making situations.
The 4 pictures in this entry are examples of the results from PRORAW files.
RE: “superior to iPhone jpegs” - the primary differences that I see in PRORAW files are; A. (obviously) the total lack of any AI applications that create a look that Apple developers think is what a picture should look like, B. hence, rather nice tonal smoothness, C. increased dynamic range (more shadow detail, smoother highlights), D. “natural” color and color saturation, E. increased but not exaggerated fine detail.
CAVEAT: Unlike that Texas based gear-head who actually believes that he can post jpegs online that illustrate the fine visual file qualities of different lens / camera sensors, et al, I realize that my sample images might not demonstrate fully the visual qualities of the PRORAW files.
My only suggestion to those of you who might be “serious” iPhone camera module users who “concentrate” when making your pictures, try PRORAW. You might like it.