Blenheim Orange wrote:
I don't think this is necessarily true, either. Canon cr raw files don't take any time to "process data" and whether or not a person is making so-called "mistakes" has nothing to do with which format to use. I work with raw files because the subtle color variations and fine detail that are critical to the results I want with the subjects I shoot are better represented in raw files than they are with camera generated JPEGs - much better - and that is before any "processing" or time consuming effort. The quality of the JPEGs and especially of the TIFF files that I output from the raw files for posting online and printing, almost always with very little work - a few seconds - is almost always much better than could ever be achieved by starting with camera generate JPEG files. Typically none of that involves "mistakes that can't be corrected as a JPEG," although it is much easier to salvage marginal images when working with raw files, However, for me, since the raw files gives such better feedback, such a better representation of what the sensor captures, that working with raw files means far, far fewer "mistakes" and much improved "in camera" images. Working with camera generated JPEGs is always a guessing game and results are less predictable.
Working with raw files has meant less time spent, less skills required, more predictability and far better image quality. For me the decision to work with raw files was a "no brainer" as the saying goes - once I saw them, which is why I think the idea that "you can't see them" is misleading. I can "see" them. I can "see" them before any "processing" which is why I think the idea that raw takes a lot of time and skill in pp can also be misleading.
There is an unbelievable amount of confusion about this topic and I don't claim to be an authority. I am describing my experience.
Mike
I don't think this is necessarily true, either. Ca... (
show quote)
The two key phrases I read here are, I am not certain, and I don't think.
You're not certain that RAW files are unprocessed data files? I'm certain of it. As for being able to see the image, what part of embedded JPEG thumbnail didn't you understand?!
What make mistakes means is, didn't get all the processing parameters set correctly for the camera to process the RAW data into best case JPEG images. Once the data is processed and compressed, you can't get it back, the camera throws it away.
Again, RAW is NOT, NOT, NOT an image format, it's the data that came off the image sensor, passes through the image processor and is then written to memory. It's all the data, repeat, all the data that came from the sensor and some more data the cameras image processor tacked on, like that thumbnail. That's pretty much why Nikon RAW files are different from Canon RAW files. Their proprietary data is different, but the concept is the same. It's kinda like but not the same as, the difference between EBCDIC and ASCII.
The reason you can and do get better images or at least better control over the images when you process them is, RAW is all the data; no compression, nothing removed; it's all the data. JPEG'S are not...
I'm pretty sure you work with RAW because it gives you all the data which gives you control over the final quality of the image. Instead of having the camera process the data into images, you do it yourself. It's quite easy to do if you have the right software and have a clue, and obviously you do.
Here's where I'm coming from. Data is data is data. There are all kinds of data. Processed data, raw data, whatever. I worked in the information technology industry for close to 40 years and my specialty was data. Data capture, data integrity, data design and formatting, just about anything pertaining to the actual client data before it was loaded onto our systems and after. My teams motto was, "Data R Us". I have maybe, a wee bit (or byte) of an understanding of, data. The stuff gathered by and stored on digital cameras is nothing more than data. The fundamental difference being the end result. Digital images, photographs, instead of financial reports or spread sheets or statements or checks or deposit tickets. It's all data to me... And, I know, or use to, a bit about programs that manipulate, modify and or process data. I've written thousands of programs over the years using standardized and proprietary languages. I've worked with several different data base management systems over the years and have even designed my own proprietary database complete with custom designed file formats, linkages, pointer systems, compression logarithms and mnemonics. And some of it even included embedded image data.