How Important is Shooting in Raw?

Newbie444

Member
Messages
20
Reaction score
4
I am so annoyed shooting in Raw. I don't even know what it does, to be honest. I think it makes editing a lot easier? I just find shooting in Raw is more of an annoyance than a help, because I have to convert to a jpg. anyway, because barely anything is compatible with Raw, I find. So should I just not shoot in Raw?
 
Solution
I am so annoyed shooting in Raw. I don't even know what it does, to be honest. I think it makes editing a lot easier? I just find shooting in Raw is more of an annoyance than a help, because I have to convert to a jpg. anyway, because barely anything is compatible with Raw, I find. So should I just not shoot in Raw?
If you're still in this stage of developing your photography, and do not require the immense flexibility that RAW files provide, just shoot JPEG for now. Raw files don't just get "converted" to JPEG, they have to be processed by you manually to get the right exposure (pull up shadows, make highlights not so overwhelming), WB, artifacts, and so on. This can be done in CameraRaw, or Lightroom, or other alternatives...
RAW files generally have no In-camera PP applied to them, as they are RAW "uncooked" data from the sensor, so they are generally flat-looking and a bit soft, but the good ones look a bit better.
Raw files do not have any particular look, they are latent images, open for interpretation.
I think you know what I mean. When viewed though a standard photo viewer, they are interpreted as flat, and sometimes soft on a pixel level.
I don't understand this. What is a "standard photo viewer"?
I suspect that the problem is, now that operating systems have raw converters built-in, some people are losing track (if they ever had any track) of the processes that are going on in producing a viewable image.
Are they actually doing a conversion or just extracting the embedded JPEG?
 
I am so annoyed shooting in Raw. I don't even know what it does, to be honest. I think it makes editing a lot easier? I just find shooting in Raw is more of an annoyance than a help, because I have to convert to a jpg. anyway, because barely anything is compatible with Raw, I find. So should I just not shoot in Raw?
Raw files keep all the data the sensor captures (typically 12-14 bit data), while JPEG reduces the dynamic range to 8 bit...

However my camera if set up moderately well usually does a MUCH better job of the JPEG conversion than I can. It gets better results, and is a lot less effort. So most of the time I shoot JPEG.

There are times when I shoot both (or save the Raw data after taking the shot, but these are in all reality for some mythical time in the future when I will look through the thousands of images on my computer & reprocess the best ones.

I would class myself to be an advanced photographer (I teach at a local workshop) but only a relative beginner at processing, which has much less interest for me.
 
I am so annoyed shooting in Raw. I don't even know what it does, to be honest. I think it makes editing a lot easier? I just find shooting in Raw is more of an annoyance than a help, because I have to convert to a jpg. anyway, because barely anything is compatible with Raw, I find. So should I just not shoot in Raw?
If you search the forums there are hundreds of threads on this and you will almost certainly get the same responses in this thread as the others got in theirs.

Raw is the max output you can get from your camera and it gives greatest leeway for editing in post, if that is what you want to do. Raw files are also much larger in megabytes than jpegs.

You can also shoot in jpeg but if you are prone to blowing the highlights they will be less easy to rectify in post.

Personally I shoot in a mix of raw or jpeg. I shoot jpeg when I am sure I will nail the exposure and perhaps the photo is less essential or important than others. I do like shooting jpeg and have done so for 16 years.

I shoot raw when it is a once in a lifetime photo, or for some other reason more important than my normal general photography. I could shoot raw+jpeg but at the moment I don't have large enough memory cards.

What gear do you have, and does your camera maker not provide raw processing / editing software?

Mark_A

Thread for Sunrise & Sunset pictures (part 3!)
 
RAW files generally have no In-camera PP applied to them, as they are RAW "uncooked" data from the sensor,
Raw (not 'RAW', it isn't an acronym) ...
Some camera manufacturers would disagree.

For instance Canon uses "RAW" (all uppercase) in the manual for the 5D mark IV.
Yup, camera manufacturers get very many things wrong. They employ technical authors who think that their purchasers are idiots and everything needs to be dumbed down if they are to understand them, even to the point of telling them things that aren't true, a bit like some members of this forum. 'Raw' is simply an adjective, and there is no reason that it should be written in upper case.
While all uppercase generally indicates an acronym, common usage sometimes deviates. For instance, "scuba" is an acronym (Self Contained Underwater Breathing Apparatus), yet is usually is written in lower case.
So, how many other adjectives do you write in CAPITAL letters? The reason for writing 'raw' in capitals is simply that at some stage a while ago, there were some numbskulls who thought that capital letters were used to denote a computer file type, having only had exposure to one dysfunctional operating system that required them to only use capital letters in file names.
so they are generally flat-looking and a bit soft, but the good ones look a bit better.
They don't 'look' like anything. They are unprocessed, they don't exist in a colour space, they have no colour, no brightness. All they are, is a record of exposure, pixel by pixel. They don;t become a viewable image until processed.

...
If you want to get technical, JPEG images don't 'look' like anything. They are just a file of numbers.
The question is, what do those numbers represent. In a JPEG file (once decompressed) those numbers represent a tonality against a defined standard colour space of each pixel in the image.
However, when we talk about the 'look' of a JPEG we generally talk about how it should appear if it is displayed according to various standard rules.
No, we talk about how it should look if correctly displayed. The numbers in the JPEG file define precisely how it ought to look. The only question is whether the viewer software or hardware gets it right or not.
Similarly, when we talk about the 'look' of a RAW file, we generally mean how it will look if it is displayed using some default settings.
It cannot be displayed using 'default settings'. What is in the raw file is simply a set of exposure measurements. The representation (i.e., which number represents which exposure) and the nature of the wavelength filtering of those exposure measurements varies from camera to camera. There is no set of defaults available.
That "display" is a complicated process as it generally involves demosaicing the data. As such, "displaying" a raw file using "standard" settings, is a bit less deterministic than "displaying" a JPEG file.
That really is nonsense. What you are describing is 'processing', not 'display. Before an image can be 'displayed' it has do be defined in terms of colours and lightnesses. A raw file isn't.
The common element is that you need a context before you can talk about how a set of numbers will look. With JPEG files, that context is better defined than with RAW files.
That all depends on what you mean by 'better defined'. What the numbers means in a JPEG file is defined by an exact and formal specification backed by international standards and underpinned by perceptual research about how we see colour and tonality. It defines exactly how the image represented by those numbers should be presented, and any deviation from that is an error. What's in the raw file determines only how that particular camera measured the scene,
I think the point AmazingLight was making was that using the default settings as his processing context, a RAW file can result in a "flat" and/or "soft" image.
What would those 'default settings be'. Until processed a raw file has no defined meaning, in terms of how you would see the image.
I think your point was that one shouldn't assume any particular context for processing RAW files, and hence it doesn't make sense to talk about what they "look" like. Depending on the processing, they may result in an image that is flat or vibrant, soft or sharp, etc.
No, that wasn't my point. My point was that until processed, a raw file doesn't have any defined human perceptual meaning.

I know that you used to resent digidog getting at you all the time, but when you come up with nonsense like that, I have sympathy with his frustration.

--
Tinkety tonk old fruit, & down with the Nazis!
Bob
 
Last edited:
RAW files generally have no In-camera PP applied to them, as they are RAW "uncooked" data from the sensor, so they are generally flat-looking and a bit soft, but the good ones look a bit better.
Raw files do not have any particular look, they are latent images, open for interpretation.
I think you know what I mean. When viewed though a standard photo viewer, they are interpreted as flat, and sometimes soft on a pixel level.
I don't understand this. What is a "standard photo viewer"?
I suspect that the problem is, now that operating systems have raw converters built-in, some people are losing track (if they ever had any track) of the processes that are going on in producing a viewable image.
Are they actually doing a conversion or just extracting the embedded JPEG?
Generally nowadays they are processing (not sure a 'conversion' is quite the right word, it suggests that they are equivalent). The embedded JPEG is variable in terms of pixel count and quality.
 
Raw is the max output you can get from your camera and it gives greatest leeway for editing in post, if that is what you want to do. Raw files are also much larger in megabytes than jpegs.
It's worthwhile checking your file sizes. You might assume that they are, but it isn't always the case.
 
I am so annoyed shooting in Raw. I don't even know what it does, to be honest. I think it makes editing a lot easier? I just find shooting in Raw is more of an annoyance than a help, because I have to convert to a jpg. anyway, because barely anything is compatible with Raw, I find. So should I just not shoot in Raw?
Raw files keep all the data the sensor captures (typically 12-14 bit data), while JPEG reduces the dynamic range to 8 bit...
No, it doesn't. JPEG is not linearly encoded.
 
I am so annoyed shooting in Raw. I don't even know what it does, to be honest. I think it makes editing a lot easier?
Raw affords you more latitude. For starters you can change WB, brightness, saturation, contrast, tonal curves, sharpness, and noise reduction.
I'm not trying to be pedantic, but sometimes using the wrong term really does embed a way of thinking that makes it hard to understand. Raw doesn't allow you to change WB, brightness, saturation, tonal curves etc. It enables you to establish what those should be in the first place. The whole point is that a raw file has no defined white balance (apart from WB preconditioning in some cases), brightness saturation, tonal curves. In fact, the whole false idea that a raw file has some defined 'brightness' is responsible for the whole ISO myth, that somehow as the ISO is turned up this 'brightness' has to be increased (the idea being that 'amplification' increases it).
 
Raw is the max output you can get from your camera and it gives greatest leeway for editing in post, if that is what you want to do. Raw files are also much larger in megabytes than jpegs.
It's worthwhile checking your file sizes. You might assume that they are, but it isn't always the case
Hi Bob,

On my D800 max raw files are about 70mb, 12bit compressed raws are about 30mb and medium jpegs about 10mb.

I only recently got it and 70mb max raws are still freaking me out a bit :-)

Mark_A

Thread for Sunrise & Sunset pictures (part 3!)
 
I think the point AmazingLight was making was that using the default settings as his processing context, a RAW file can result in a "flat" and/or "soft" image.
What would those 'default settings be'. Until processed a raw file has no defined meaning, in terms of how you would see the image.
The "default" settings are whatever your raw processing software use when you don't otherwise change them.

I think your point was that one shouldn't assume any particular context for processing RAW files, and hence it doesn't make sense to talk about what they "look" like. Depending on the processing, they may result in an image that is flat or vibrant, soft or sharp, etc.
No, that wasn't my point. My point was that until processed, a raw file doesn't have any defined human perceptual meaning.
There is a difference between "any defined meaning" and a "well defined meaning".

Even without a specific context a raw file will have some associated meaning. Given the embedded metadata, there are areas of the image which will be green, blue, red, etc. Some areas will be darker, and others will be lighter.

What we don't have is an "exact" meaning. Without knowing the particulars of the raw processing, we don't know exactly which shade of green, blue or red we will get. If the particulars are unusual, we might actually get something that isn't green, blue or red.

So the question becomes one of whether it is helpful to know a probably approximation of what the result will be?

One of the issues I see on these forums (particularly the beginners forum), is a disconnect between what the beginner sees with his own eyes, and the experts that tell him he is wrong.

For instance, put a camera on full automatic, and take a RAW photo of green grass, outdoors. A beginner will most likely end up with an image where the grass looks "green." It's confusing when an "expert" tells him he is wrong, because we don't have enough information to know exactly which shade of green he will get.

A beginner who is shooting RAW for the first time may very well get flat colors and soft details. Telling him he is wrong is confusing. Clearly, that conflicts with the direct evidence in front of his eyes.

From an overview perspective, the data in a raw file does generally correspond to colors. However, it's fair to say that the correspondence is neither exact nor immutable.

I know that you used to resent digidog getting at you all the time, but when you come up with nonsense like that, I have sympathy with his frustration.

--
Tinkety tonk old fruit, & down with the Nazis!
Bob
 
I am so annoyed shooting in Raw. I don't even know what it does, to be honest. I think it makes editing a lot easier?
Raw affords you more latitude. For starters you can change WB, brightness, saturation, contrast, tonal curves, sharpness, and noise reduction.
I'm not trying to be pedantic, but sometimes using the wrong term really does embed a way of thinking that makes it hard to understand. Raw doesn't allow you to change WB, brightness, saturation, tonal curves etc. It enables you to establish what those should be in the first place.
Okay, then shooting Raw allows you to change your mind about those things, or to experiment with them at your leisure.
The whole point is that a raw file has no defined white balance (apart from WB preconditioning in some cases),
Just to be clear, I have never seen any difference in a Raw file by changing the camera's WB setting.
brightness saturation, tonal curves. In fact, the whole false idea that a raw file has some defined 'brightness' is responsible for the whole ISO myth, that somehow as the ISO is turned up this 'brightness' has to be increased (the idea being that 'amplification' increases it).
I never said there is a defined brightness to a Raw file. Indeed, the ISO of the shot is rather malleable, but I wasn't going to tell a "Beginner" that ISO can also be changed (or if you prefer, established). One thing does lead to another, but why clutter up a thread about shooting Raw with a discussion of the "Exposure Triangle?"
 
Last edited:
Raw is the max output you can get from your camera and it gives greatest leeway for editing in post, if that is what you want to do. Raw files are also much larger in megabytes than jpegs.
It's worthwhile checking your file sizes. You might assume that they are, but it isn't always the case
Hi Bob,

On my D800 max raw files are about 70mb, 12bit compressed raws are about 30mb and medium jpegs about 10mb.

I only recently got it and 70mb max raws are still freaking me out a bit :-)
Lossless compressed typically cuts the file size in half.
 
Raw is the max output you can get from your camera and it gives greatest leeway for editing in post, if that is what you want to do. Raw files are also much larger in megabytes than jpegs.
It's worthwhile checking your file sizes. You might assume that they are, but it isn't always the case
Hi Bob,

On my D800 max raw files are about 70mb, 12bit compressed raws are about 30mb and medium jpegs about 10mb.

I only recently got it and 70mb max raws are still freaking me out a bit :-)
Lossless compressed typically cuts the file size in half.
Indeed, no reason not to use lossless compressed. Most cameras, that's the only raw option there is.
 
RAW files generally have no In-camera PP applied to them, as they are RAW "uncooked" data from the sensor, so they are generally flat-looking and a bit soft, but the good ones look a bit better.
Raw files do not have any particular look, they are latent images, open for interpretation.
I think you know what I mean. When viewed though a standard photo viewer, they are interpreted as flat, and sometimes soft on a pixel level.
I don't understand this. What is a "standard photo viewer"?
I suspect that the problem is, now that operating systems have raw converters built-in, some people are losing track (if they ever had any track) of the processes that are going on in producing a viewable image.
Are they actually doing a conversion or just extracting the embedded JPEG?
Generally nowadays they are processing (not sure a 'conversion' is quite the right word, it suggests that they are equivalent). The embedded JPEG is variable in terms of pixel count and quality.
You can replace embedded JPEGs in a raw, and it may turn out it is not processing, especially for some newer cameras.
 
I am so annoyed shooting in Raw. I don't even know what it does, to be honest. I think it makes editing a lot easier?
Raw affords you more latitude. For starters you can change WB, brightness, saturation, contrast, tonal curves, sharpness, and noise reduction.
I'm not trying to be pedantic, but sometimes using the wrong term really does embed a way of thinking that makes it hard to understand. Raw doesn't allow you to change WB, brightness, saturation, tonal curves etc. It enables you to establish what those should be in the first place.
Okay, then shooting Raw allows you to change your mind about those things, or to experiment with them at your leisure.
I think that is better. I wasn't getting at you, I think the way you said it is reasonable until you begin to think what other people might get from it. A long history of discussions here, when you get played back such explanations as the cause of misconceptions has led me to think maybe that one just needs to be aware of other possible interpretations than your own.
The whole point is that a raw file has no defined white balance (apart from WB preconditioning in some cases),
Just to be clear, I have never seen any difference in a Raw file by changing the camera's WB setting.
Then presumably you haven't used a camera with WB preconditioning.
brightness saturation, tonal curves. In fact, the whole false idea that a raw file has some defined 'brightness' is responsible for the whole ISO myth, that somehow as the ISO is turned up this 'brightness' has to be increased (the idea being that 'amplification' increases it).
I never said there is a defined brightness to a Raw file. Indeed, the ISO of the shot is rather malleable, but I wasn't going to tell a "Beginner" that ISO can also be changed (or if you prefer, established). One thing does lead to another, but why clutter up a thread about shooting Raw with a discussion of the "Exposure Triangle?"
I wasn't suggesting that you had. I was just warming to the subject. My apologies if you think it's a diversion. Again, my experience is that this whole web of misconception tends to be terminologically linked.
 
no reason not to use lossless compressed.
When a Huffman gets corrupted, recovery is close to impossible. With uncompressed formats, on the other hand, the damage is local.

Oddly enough, if the proper backup procedure is in place, that is the only question is the disk size/model and how/when to round-robin the disks, it doesn't matter what is the size of the raw.

But when (and that's mostly how it is, especially in the field - that's why we receive massive recovery requests, and often the only thing we can help with is extraction of embedded JPEGs) the procedure is consumer-level or simply absent, uncompressed files are the safer option.
 
...

I think the point AmazingLight was making was that using the default settings as his processing context, a RAW file can result in a "flat" and/or "soft" image.
What would those 'default settings be'. Until processed a raw file has no defined meaning, in terms of how you would see the image.
The "default" settings are whatever your raw processing software use when you don't otherwise change them.
Which means nothing at all, since you don't know what the raw processing software is, what its designers thought the 'defaults' should be or, indeed, which camera or brand you are using. So, there is no universal 'default' which would justify the statement that 'a RAW (sic) file can result in a "flat" or "soft" image', which is, I'm afraid just non-factual.
I think your point was that one shouldn't assume any particular context for processing RAW files, and hence it doesn't make sense to talk about what they "look" like. Depending on the processing, they may result in an image that is flat or vibrant, soft or sharp, etc.
No, that wasn't my point. My point was that until processed, a raw file doesn't have any defined human perceptual meaning.
There is a difference between "any defined meaning" and a "well defined meaning".
I qualified it advisedly, because obviously, since you can use a raw file to create a file with a well defined perceptual meaning, there is some kind of link. But the point is, the numbers in the raw file don't define the 'look' of the image without a set of assumptions the processor has to make, which are not in any way 'default'.
Even without a specific context a raw file will have some associated meaning. Given the embedded metadata, there are areas of the image which will be green, blue, red, etc. Some areas will be darker, and others will be lighter.

What we don't have is an "exact" meaning. Without knowing the particulars of the raw processing, we don't know exactly which shade of green, blue or red we will get. If the particulars are unusual, we might actually get something that isn't green, blue or red.
That amounts to what I said above, clearly since you can derive a perceptually defined link there is some meaning, which is why I qualified the statement as I did. I get the impression now that you're trying to squeeze through that qualification so as not to be wrong. Sure, you can find a route by which what you said isn't complete garbage, but that's actually denying the intention of it, and also ignoring its misinformation potential, which is why I challenged it.
So the question becomes one of whether it is helpful to know a probably approximation of what the result will be?
No, that's a new question that you've raised now so as to use it to avoid having been wrong. It's a question that is irrelevant to the discussion.
One of the issues I see on these forums (particularly the beginners forum), is a disconnect between what the beginner sees with his own eyes, and the experts that tell him he is wrong.
'Experts' don't usually tell beginners that they are wrong.. They seek to inform them. The people who get told they are wrong is people posing as 'experts' who are, in terms of the material as much beginners as the beginners, but just don't realise it.
For instance, put a camera on full automatic, and take a RAW photo of green grass, outdoors. A beginner will most likely end up with an image where the grass looks "green." It's confusing when an "expert" tells him he is wrong, because we don't have enough information to know exactly which shade of green he will get.
So, an expert wouldn't tell him that he is 'wrong'. You're raising straw men here.
A beginner who is shooting RAW for the first time may very well get flat colors and soft details. Telling him he is wrong is confusing. Clearly, that conflicts with the direct evidence in front of his eyes.
Which person has told a beginner that he's wrong? I think the person being told they were wrong was not the beginner.
From an overview perspective, the data in a raw file does generally correspond to colors. However, it's fair to say that the correspondence is neither exact nor immutable.
Maybe you should learn something about the topic before pronouncing on matters like this. For a start, what a 'colour' is.
 
no reason not to use lossless compressed.
When a Huffman gets corrupted, recovery is close to impossible. With uncompressed formats, on the other hand, the damage is local.

Oddly enough, if the proper backup procedure is in place, that is the only question is the disk size/model and how/when to round-robin the disks, it doesn't matter what is the size of the raw.

But when (and that's mostly how it is, especially in the field - that's why we receive massive recovery requests, and often the only thing we can help with is extraction of embedded JPEGs) the procedure is consumer-level or simply absent, uncompressed files are the safer option.
Now, there is an angle I hadn't thought of.
 
...

I think the point AmazingLight was making was that using the default settings as his processing context, a RAW file can result in a "flat" and/or "soft" image.
What would those 'default settings be'. Until processed a raw file has no defined meaning, in terms of how you would see the image.
The "default" settings are whatever your raw processing software use when you don't otherwise change them.
Which means nothing at all, since you don't know what the raw processing software is, what its designers thought the 'defaults' should be or, indeed, which camera or brand you are using. So, there is no universal 'default' which would justify the statement that 'a RAW (sic) file can result in a "flat" or "soft" image', which is, I'm afraid just non-factual.
I believe that a beginner can in fact open a RAW file in PhotoShop, iPhoto, Afintity Photo, etc., without altering any of the offered settings.

I would call this using the "defaults".

Obviously, he will probably not somewhat different images, depending on which software he uses.

Where we differ is whether it makes sense to talk in generalities about the results.

As the above is a workflow that a beginner may first try when shooting RAW, it seems to me that it does make sense to discuss what can happen when you use default settings.

Whether the default settings in some software does in fact produce "flat" or "soft" images is a discussion that I think is reasonable.
I think your point was that one shouldn't assume any particular context for processing RAW files, and hence it doesn't make sense to talk about what they "look" like. Depending on the processing, they may result in an image that is flat or vibrant, soft or sharp, etc.
No, that wasn't my point. My point was that until processed, a raw file doesn't have any defined human perceptual meaning.
There is a difference between "any defined meaning" and a "well defined meaning".
I qualified it advisedly, because obviously, since you can use a raw file to create a file with a well defined perceptual meaning, there is some kind of link. But the point is, the numbers in the raw file don't define the 'look' of the image without a set of assumptions the processor has to make, which are not in any way 'default'.
Again, our difference boils down to whether or not the software used by a beginner has default settings.
Even without a specific context a raw file will have some associated meaning. Given the embedded metadata, there are areas of the image which will be green, blue, red, etc. Some areas will be darker, and others will be lighter.

What we don't have is an "exact" meaning. Without knowing the particulars of the raw processing, we don't know exactly which shade of green, blue or red we will get. If the particulars are unusual, we might actually get something that isn't green, blue or red.
That amounts to what I said above, clearly since you can derive a perceptually defined link there is some meaning, which is why I qualified the statement as I did. I get the impression now that you're trying to squeeze through that qualification so as not to be wrong. Sure, you can find a route by which what you said isn't complete garbage, but that's actually denying the intention of it, and also ignoring its misinformation potential, which is why I challenged it.
Let's back up a bit. We got here when I said "I think the point AmazingLight was making was that using the default settings as his processing context, a RAW file can result in a "flat" and/or "soft" image."

I stand by that statement. (Other than the typo it should have said "...in his processing...")
 
I am so annoyed shooting in Raw. I don't even know what it does, to be honest. I think it makes editing a lot easier?
Raw affords you more latitude. For starters you can change WB, brightness, saturation, contrast, tonal curves, sharpness, and noise reduction.
I'm not trying to be pedantic, but sometimes using the wrong term really does embed a way of thinking that makes it hard to understand. Raw doesn't allow you to change WB, brightness, saturation, tonal curves etc. It enables you to establish what those should be in the first place.
Okay, then shooting Raw allows you to change your mind about those things, or to experiment with them at your leisure.
I think that is better. I wasn't getting at you, I think the way you said it is reasonable until you begin to think what other people might get from it. A long history of discussions here, when you get played back such explanations as the cause of misconceptions has led me to think maybe that one just needs to be aware of other possible interpretations than your own.
The whole point is that a raw file has no defined white balance (apart from WB preconditioning in some cases),
Just to be clear, I have never seen any difference in a Raw file by changing the camera's WB setting.
Then presumably you haven't used a camera with WB preconditioning.
WB preconditioning is a new term to me. This implies that the raw file is not "raw" but is cooked According to some camera presets. Which cameras might do this? This goes against my understanding of what a raw file should be.
brightness saturation, tonal curves. In fact, the whole false idea that a raw file has some defined 'brightness' is responsible for the whole ISO myth, that somehow as the ISO is turned up this 'brightness' has to be increased (the idea being that 'amplification' increases it).
I never said there is a defined brightness to a Raw file. Indeed, the ISO of the shot is rather malleable, but I wasn't going to tell a "Beginner" that ISO can also be changed (or if you prefer, established). One thing does lead to another, but why clutter up a thread about shooting Raw with a discussion of the "Exposure Triangle?"
I wasn't suggesting that you had. I was just warming to the subject. My apologies if you think it's a diversion. Again, my experience is that this whole web of misconception tends to be terminologically linked.
 

Keyboard shortcuts

Back
Top