For our DR peepers: Sony A7000 - rumored 15,5 stops DR

neuroanatomist said:
msm said:
Oh ok so when you fall below "Screen DR" or a SNR of 1 all of a sudden all information dissapears in Neuro land? ::)

This is not how things work in statistics. It is not how sensors work in the real world either. And fortunately it is easy to test, here is a couple of pictures for you, one is ETTR'ed (not a single pixel clipped according to rawdigger) and the other is underexposed 16 stops (where all information would be lost according to you) and then pushed.

Apparently you don't understand the meaning of the word "range". It seems you think dynamic range represents a static set of values distributed around metered 'middle gray'.

At least you have succeeded in proving one thing...your lack of comprehension and knowledge regarding this topic. Great job!

I have proven you wrong with practical examples several times already and here you are trying to weasel yourself out again with a straw man argument. Well done! ::)

Time to look into that mirror troll.
 
Upvote 0
jrista said:
neuroanatomist said:
Yes, it's quite a good trick to have DR "in mid 14's" when your camera has a 14-bit ADC. Hail to the almighty DxO Biased Scores, and kudos to those that revel in that BS. ::)

It's actually the compression algorithm. Also technically speaking, it isn't actually RAW. However, cRAW applies a tone curve to the data coming off the sensor before it black clips and compresses. It's actually the same thing they do with the A7s, and will probably do with future cameras. They take a greater dynamic range than their bit depth and use a mathematical curve to compress it into a smaller space. Same thing we do with our RAW editors.

The thing with Sony cameras is they have the data fidelity to actually do that. The data precision in their RAW files may only be 12 bit, however in terms of usable information they still deliver stops more than any Canon camera. You can hate DXO all you want (I don't like most of what they do either), but the real world results are all you should need to understand that bit depth and usable information are not synonymous.

The thing I don't get is why Sony doesn't just go strait to 16-bit RAW. In digging around with their SDK lately, I think Sony has some strange data bottlenecks somewhere in their readout pipeline. They have a number of cases where they restrict the sensor readout to 12 bits even, and it always seems to be throughput related. If at some point they resolve those issues, I'd be willing to bet Sony puts the first 16-bit RAW consumer camera on the market.

Regarding the rumored A7000, yes it's certainly possible to map higher DR from on-sensor HDR down into a lower bit depth file (assuming the rumors are true). As you state, it won't be RAW data at that point, but Sony doesn't seem to care much about that anyway. It certainly breaks the long-standing common practice of using an ADC that can fully encompass the DR from the sensor. Maybe it's common to compress/map wider analog data down prior to digitizing it in other fields e.g. audio, I'm not sure.

Regarding the more recent discussion in this thread regarding current cameras, it has nothing to do with in-camera mapping/compression, and everything to do with DxO's downsampling the files to 8 MP. AFAIK, no current dSLR/MILC can record >14-stops of DR at capture (but for example the Red Epic Dragon can, and it uses a 16-bit ADC).
 
Upvote 0
msm said:
I have proven you wrong with practical examples several times already and here you are trying to weasel yourself out again with a straw man argument.

You've proven 'with practical examples several times' that current dSLRs/MILCs (e.g. D750, a7R) can capture more than 14-stops of DR present in the scene being imaged? If you truly believe that, I feel sorry for you.
 
Upvote 0
neuroanatomist said:
msm said:
I have proven you wrong with practical examples several times already and here you are trying to weasel yourself out again with a straw man argument.

You've proven 'with practical examples several times' that current dSLRs/MILCs (e.g. D750, a7R) can capture more than 14-stops of DR present in the scene being imaged? If you truly believe that, I feel sorry for you.

DR has precise definitions in mathemathical terms, do yourself a favour and stop your pathethic attempts at trying to make it something it isn't.

For instance how do you decide if a sensor "can capture more than 14-stops of DR present in the scene being imaged"? Your personal opinion? If you can't even make a precise definition that is just completely ridiculous waste of time. it is like discussing with a child who just changes the meaning of things as it suits him/her.
 
Upvote 0
msm said:
neuroanatomist said:
msm said:
I have proven you wrong with practical examples several times already and here you are trying to weasel yourself out again with a straw man argument.

You've proven 'with practical examples several times' that current dSLRs/MILCs (e.g. D750, a7R) can capture more than 14-stops of DR present in the scene being imaged? If you truly believe that, I feel sorry for you.

DR has precise definitions in mathemathical terms, do yourself a favour and stop your pathethic attempts at trying to make it something it isn't.

For instance how do you decide if a sensor "can capture more than 14-stops of DR present in the scene being imaged"? Your personal opinion? If you can't even make a precise definition that is just completely ridiculous waste of time. it is like discussing with a child who just changes the meaning of things as it suits him/her.

I know how to define DR. Your error is in defining it for only one part of the system (the digital file) rather than considering the (more relevant for photography) definition in terms of the subject being imaged.

Forest : trees :: scene : pixels.

Light meter for scene, image analysis for captured image. Alternatively, an example was provided by 3kramd5 a couple of pages back, that need only involve a light bulb and a sheet of canvas. Too complex for you?

Yes, your ridiculous intransigence and lack of comprehension makes further discussion on this issue a complete waste of my time. If ignorance is bliss, you must be a very happy person!
 
Upvote 0
neuroanatomist said:
msm said:
neuroanatomist said:
msm said:
I have proven you wrong with practical examples several times already and here you are trying to weasel yourself out again with a straw man argument.

You've proven 'with practical examples several times' that current dSLRs/MILCs (e.g. D750, a7R) can capture more than 14-stops of DR present in the scene being imaged? If you truly believe that, I feel sorry for you.

DR has precise definitions in mathemathical terms, do yourself a favour and stop your pathethic attempts at trying to make it something it isn't.

For instance how do you decide if a sensor "can capture more than 14-stops of DR present in the scene being imaged"? Your personal opinion? If you can't even make a precise definition that is just completely ridiculous waste of time. it is like discussing with a child who just changes the meaning of things as it suits him/her.

I know how to define DR. Your error is in defining it for only one part of the system (the digital file) rather than considering the (more relevant for photography) definition in terms of the subject being imaged.

Forest : trees :: scene : pixels.

Light meter for scene, image analysis for captured image. Alternatively, an example was provided by 3kramd5 a couple of pages back, that need only involve a light bulb and a sheet of canvas. Too complex for you?

Yes, your ridiculous intransigence and lack of comprehension makes further discussion on this issue a complete waste of my time. If ignorance is bliss, you must be a very happy person!

Is this what passes as a scientific definition for you? Can be implemented infinite number of ways leading to whatever conclusion you want.

If you really want to go there then we can just make unscientific criterions like "being able to capture enough data to enable a person with normal eye sight to unmistakenly read 2 rows of text consisting of 5 letters each". Then I have already demonstrated that the a7r easily has more than 16stops of DR!
 
Upvote 0
neuroanatomist said:
jrista said:
neuroanatomist said:
Yes, it's quite a good trick to have DR "in mid 14's" when your camera has a 14-bit ADC. Hail to the almighty DxO Biased Scores, and kudos to those that revel in that BS. ::)

It's actually the compression algorithm. Also technically speaking, it isn't actually RAW. However, cRAW applies a tone curve to the data coming off the sensor before it black clips and compresses. It's actually the same thing they do with the A7s, and will probably do with future cameras. They take a greater dynamic range than their bit depth and use a mathematical curve to compress it into a smaller space. Same thing we do with our RAW editors.

The thing with Sony cameras is they have the data fidelity to actually do that. The data precision in their RAW files may only be 12 bit, however in terms of usable information they still deliver stops more than any Canon camera. You can hate DXO all you want (I don't like most of what they do either), but the real world results are all you should need to understand that bit depth and usable information are not synonymous.

The thing I don't get is why Sony doesn't just go strait to 16-bit RAW. In digging around with their SDK lately, I think Sony has some strange data bottlenecks somewhere in their readout pipeline. They have a number of cases where they restrict the sensor readout to 12 bits even, and it always seems to be throughput related. If at some point they resolve those issues, I'd be willing to bet Sony puts the first 16-bit RAW consumer camera on the market.

Regarding the rumored A7000, yes it's certainly possible to map higher DR from on-sensor HDR down into a lower bit depth file (assuming the rumors are true). As you state, it won't be RAW data at that point, but Sony doesn't seem to care much about that anyway. It certainly breaks the long-standing common practice of using an ADC that can fully encompass the DR from the sensor. Maybe it's common to compress/map wider analog data down prior to digitizing it in other fields e.g. audio, I'm not sure.

Regarding the more recent discussion in this thread regarding current cameras, it has nothing to do with in-camera mapping/compression, and everything to do with DxO's downsampling the files to 8 MP. AFAIK, no current dSLR/MILC can record >14-stops of DR at capture (but for example the Red Epic Dragon can, and it uses a 16-bit ADC).

You know I don't like DXO any more than anyone else. Their persistent attempts to box all of the complexity of sensor IQ into a single scalar number is as annoying as ever. That said, all they are doing is normalizing. Normalization should be a well understood concept, especially by someone such as yourself, given how many times it's been explained on these forums.

Personally, outside of a pure comparison context, I don't believe the numbers spit out by 8mp normalized results tell us much about what we'll experience when actually editing a RAW file in a program like lightroom. I believe that Screen DR (non-normalized DR) tell us that, since that is the per-pixel DR of the RAW data that we are literally working with. Another issue I have with DXO's Print DR is that,while they call it a "measurement", it is absolutely nothing of the sort. It is a purely extrapolated number, acquired by running another DR value through a simple mathematical formula. It's the purely theoretical maximum DR that the camera might achieve if it had perfect noise characteristics. It does not account for actual noise characteristics, because it is not an actual measurement...it's an extrapolation from an actual measurement (which so happens to be Screen DR).

The fact that DXO does not make that clear, and worse the fact that they utilize their Print DR numbers as THE DR numbers, has lead a significant percentage of the photography community regurgitating numbers like 14.8 stops of DR as actual real-world DR. Assuming all of those people are downsampling all of their photos to 8 megapixels, then they may well indeed be getting 14.8 stops, or 14.5 stops, or 14.2 stops or whatever it is for the camera they use. If they are keeping their data RAW, or worse, printing at even larger sizes than native, then they are decidedly NOT getting the theoretical maximum potential DR.

Sadly, I do not believe that actually downsampling images and actually measuring them would paint Canon in any better light. Canon has worse noise characteristics than the competition, so actual Print DR measures for Canon would probably end up worse than the extrapolated Print DR "measures" that DXO uses now. I spend a lot of time working at the noise floor with astrophotography. I run FFT's on individual subs and integrations every so often. Canon data doesn't even come close to exhibiting a gaussian distribution of noise. Sony cameras are closer, but their compression limits how close they can get. Nikon D800 data with the black point hack actually has the closest to gaussian representation, but even they aren't purely gaussian. A clean, pure gaussian noise profile would result in ideal downsampling results, while the non-gaussian noise profile of Canon data is going to result in less than ideal downsampling results. I don't believe any ILC currently on the market could actually achieve exactly the Print DR that DXO lists, although I think the D800 & D810 probably get closer than anything else.

As for recording more than 14 stops of DR "at capture". Depending on exactly what you mean there, it's possible. Assuming "at capture" means in the analog signal on the sensor, then if you had a sensor with, say, an 80,000e- FWC and 3e- read noise. The dynamic range of the analog signal is 14.75 stops of DR. With a strait ADC conversion using a 14-bit ADC, you would have to clip that to 14 stops in some way. Alternatively, you could compress the dynamic range, preserving the original bounds of the information it represented by combining some of the information with less precision. Lower precision, same range of information. That's what cRAW does...applies a curve that compresses the sensor DR into a tighter range, then digitizes it.

Conversely, if you have a sensor with 80,000e- and 25e- RN, then your dynamic range is 11.68 stops. Your analog signal doesn't have enough tonality to even use 12 bits, so storing the signal in 14 bit data is really just wasteful. It could affect camera design in other ways...larger numbers use more bandwidth, thus potentially limiting your maximum throughput, putting a cap on frame rate, etc. Canon could easily be using 12-bit data, and we wouldn't be losing a thing. We wouldn't be able to represents steps of noise as accurately, but we certainly wouldn't be losing tonality. Because of the higher read noise, the sensor isn't capable of delivering more than 14 stops of DR, so compressing the signal makes no sense.

If Canon delivers a 5D IV with an 80ke- FWC and 5e- RN, on the other hand, they would have 14.01 stops of DR, and at that point, they would be able to fully utilize the bit depth of their ADCs. They still wouldn't need to compress the original sensor information to fit the bit depth of the ADC, but they would at least be able to use all of it.

Bandwidth is, IMO, the primary reason Sony hasn't gone to 16 bit ADC yet. They seem to be borderline on 14 bit as it is, but since their sensors do deliver at the very least more than 13 stops of DR, they are able to utilize a 14 bit ADC unit. If it wasn't for any kind of throughput bottlenecks, then I suspect Sony would already be using 16 bit ADCs. One of the reasons Exmor has lower noise is because their ADC units are column parallel, which allows them to be run at a lower frequency. It is entirely possible that running them at a higher frequency to handle 16-bit conversion introduces more noise, which would diminish dynamic range. I'm not sure. Either way, what Sony is doing, compressing the original signal before conversion, is the best way to preserve the information their sensors are capable of delivering, even if it costs some precision. In practical use, the loss of precision doesn't seem to be a huge issue. It might result in some posterization of smooth gradients at the low and high ranges of the signal, where linearity may drop. Again, in practice, it seems that photon shot noise is generally high enough that posterization isn't a big problem outside of extreme circumstances.
 
Upvote 0
jrista said:
You know I don't like DXO any more than anyone else. Their persistent attempts to box all of the complexity of sensor IQ into a single scalar number is as annoying as ever. That said, all they are doing is normalizing. Normalization should be a well understood concept, especially by someone such as yourself,

Personally, outside of a pure comparison context, I don't believe the numbers spit out by 8mp normalized results tell us much about what we'll experience when actually editing a RAW file in a program like lightroom. I believe that Screen DR (non-normalized DR) tell us that, since that is the per-pixel DR of the RAW data that we are literally working with.

Certainly I inderstand normalization and its utility, given that I compare datasets across platforms routinely. In the case of "print DR," it seems that we agree...it's a comparison shopping tool (and I'd add that for some, it's a bragging rights tool). As you say, "screen DR" is what matters when considering an individual RAW file from a photographic standpoint, as opposed to comparing sensors.

jrista said:
The fact that DXO does not make that clear, and worse the fact that they utilize their Print DR numbers as THE DR numbers, has lead a significant percentage of the photography community regurgitating numbers like 14.8 stops of DR as actual real-world DR.

Exactly the point I made earlier in the thread, when I pointed out a camera magazine's statement concerning 'capturing all the tones in a scene' and stating the D610's DR has been measured at up to 14.4 stops. A patently false statement that someone inexplicably argued to support.


jrista said:
As for recording more than 14 stops of DR "at capture". Depending on exactly what you mean there, it's possible. Assuming "at capture" means in the analog signal on the sensor, then if you had a sensor with, say, an 80,000e- FWC and 3e- read noise. The dynamic range of the analog signal is 14.75 stops of DR. With a strait ADC conversion using a 14-bit ADC, you would have to clip that to 14 stops in some way. Alternatively, you could compress the dynamic range, preserving the original bounds of the information it represented by combining some of the information with less precision. Lower precision, same range of information. That's what cRAW does...applies a curve that compresses the sensor DR into a tighter range, then digitizes it.

Yes, it's theoretically possible. But to reiterate, the discussion was about specifics and current cameras, such as the "fact" that the D750 can capture 14.5 stops of DR. Given a FWC of 81608 e- and read noise of 5.5 e-, that's clearly not the case (as shown by DxO's screen DR measurement). But some people – well, one person – apparently can't seem to come to grips with the fact that a screen DR of 13.9 stops means information in a scene that exceeds that range will be lost and unrecoverable. I suspect you can explain it more effectively if you choose, but I wouldn't bother.
 
Upvote 0
jrista said:
As for recording more than 14 stops of DR "at capture". Depending on exactly what you mean there...

Seems like we should be able to come up with an agreement about what it means. I propose that capture consists of everything between and inclusive of the light hitting the sensor, and the digitized data being written.
 
Upvote 0
3kramd5 said:
jrista said:
As for recording more than 14 stops of DR "at capture". Depending on exactly what you mean there...

Seems like we should be able to come up with an agreement about what it means. I propose that capture consists of everything between and inclusive of the light hitting the sensor, and the digitized data being written.

I don't know that it is that simple. Sensors currently still accumulate analog signals. Signals that are represented by an electric charge. Cameras ultimately produce digital signals, signals that are represented by bits stored as integral numbers. Analong signals and digital signals have similarities, but they also have key differences.

There is also the fact that the readout pipeline is where noise gets added to the signal, and the native dynamic range of the sensor can be reduced.

Furthermore, if dynamic range compression is being used somewhere in the readout pipeline, precision may be lost, but information can be preserved. So, if a sensor is capable of 15.5 stops of dynamic range, that 15.5 stops of information in an actual signal is compressed into 14 stops, or even 12 stops, at an early stage in the readout pipeline, then how much dynamic range do you have?

Not a simple question. You may have as little as 12 bits of precision, but in my experience you can have considerably more usable information than that. Sony cameras lossy compress their information. That's probably the thing I like LEAST about their cameras, it's kind of a big deal for me to have truely raw data. However in practice, somehow, despite the most precise bit of information in every 32 pixel block of pixels in an ARW being 11 bits, I can still push up orders of magnitude more information from the shadows in an A7r or A7s than I can with any Canon camera.

So...I don't think things are just as simple as: If it's bigger than the bit depth of the ADC, it simply can't be. That just doesn't jive with reality. It doesn't jive with what I can do with the data from an Alpha camera, let alone from something like the D810 (which does NOT lossy compress the data).

Precision vs. usable information. Sony is reducing their precision...a lot in some cases, more than I think they should. However that does not seem to cost them the information...and that's really what matters in the end.

Anything else...it's all just playing games, semantics, reasons to perpetuate a pointless argument for...well, it seems forever.

These days, it's become fairly simple to me. These days, what I care about are the actual results. I don't always need 14 stops or 15 stops or 16 stops of dynamic range. However when I DO need more...my Canon cameras are only giving me 11 stops. I then have to resort to something more complex, such as multi-frame capture and HDR blending...assuming I even have that option. I can't count the number of times I've ETTRed with my 5D III on a day with wonkey light...nailed exposure on one frame in a burst only to have it come out slightly OOF, then have the next frame shot be perfectly in focus yet two thirds of a stop brighter and clip my highlights because a cloud moved and the sun popped out. ETTR is essential with a Canon camera if you wish to preserve all the information you can, especially when shooting birds with both bright and dark feathers...and it's also a major risk. If I had 12 stops or more of DR, I could just keep the exposure a safe 1 stop from the clipping point, and just never have to worry. If I had 14 stops of DR, I could push the shadows on those darker feathers, and they would not only be barely usable...they would be pristine! I wouldn't always need the full 14 stops...but having more than eleven? INVALUABLE.
 
Upvote 0
Great contribution Jon (JRista). I always love reading your posts. They are very informative (quite technical but not over technical). You are a real asset to Canon Rumors. I must say too your website is a delight. There are alot of posters here from who you hear alot of technical details and complaints about sharpness or dynamic range or how bad Canon are. They don't show too much of their work.
I can see from your photos you are pushing the technical limits of the camera gear in both wildlife and the stunning astrophotography. Keep up the good work. It's inspiring.
 
Upvote 0
jrista said:
3kramd5 said:
jrista said:
As for recording more than 14 stops of DR "at capture". Depending on exactly what you mean there...

Seems like we should be able to come up with an agreement about what it means. I propose that capture consists of everything between and inclusive of the light hitting the sensor, and the digitized data being written.

I don't know that it is that simple. Sensors currently still accumulate analog signals. Signals that are represented by an electric charge. Cameras ultimately produce digital signals, signals that are represented by bits stored as integral numbers. Analong signals and digital signals have similarities, but they also have key differences.

Of course, but you and I can't do anything with charge. We can only use what is ultimately produced.


jrista said:
There is also the fact that the readout pipeline is where noise gets added to the signal, and the native dynamic range of the sensor can be reduced.

Indeed, and since we can't ever store the data without reading it out, it seems logical to include the entire signal chain in the process of capture.

jrista said:
Furthermore, if dynamic range compression is being used somewhere in the readout pipeline, precision may be lost, but information can be preserved. So, if a sensor is capable of 15.5 stops of dynamic range, that 15.5 stops of information in an actual signal is compressed into 14 stops, or even 12 stops, at an early stage in the readout pipeline, then how much dynamic range do you have?

Whatever it is compressed to. If the data is made non-linear before being filed, that is included. If it's noise-reduced before being filed, that's included.

It's all well and good to consider the resulting generation of charge as capturing photons, but perhaps outside of a laboratory subassy, nobody can use that charge until it's digitized and filed.

jrista said:
Not a simple question. You may have as little as 12 bits of precision, but in my experience you can have considerably more usable information than that. Sony cameras lossy compress their information. That's probably the thing I like LEAST about their cameras, it's kind of a big deal for me to have truely raw data. However in practice, somehow, despite the most precise bit of information in every 32 pixel block of pixels in an ARW being 11 bits, I can still push up orders of magnitude more information from the shadows in an A7r or A7s than I can with any Canon camera.

Yah, I've not seen any issues with my A7R's lossy compression. I would certainly like the option to store a lossless RAW with the A7R2, but the compression artifacts I've seen in rawdigger's analysis haven't manifested to my knowledge in any of my shots with the platform.

jrista said:
These days, it's become fairly simple to me. These days, what I care about are the actual results.

Concur, and going back to the beginning of this reply, hence my suggestion that we define capture as the entire process of converting photons to charge, reading, amplifying, digitizing those data, and writing files. The files are the results. :)
 
Upvote 0
neuroanatomist said:
But some people – well, one person – apparently can't seem to come to grips with the fact that a screen DR of 13.9 stops means information in a scene that exceeds that range will be lost and unrecoverable. I suspect you can explain it more effectively if you choose, but I wouldn't bother.

Yes please looking forward to seeing that explanation. Particularly want to see the explanation of how I was able to recover information from a 16 stop underexposed image from my A7R, considering it has a "screen DR" of less than 13 stops and "information in a scene that exceeds that range will be lost and unrecoverable". ;D
 
Upvote 0
msm said:
neuroanatomist said:
But some people – well, one person – apparently can't seem to come to grips with the fact that a screen DR of 13.9 stops means information in a scene that exceeds that range will be lost and unrecoverable. I suspect you can explain it more effectively if you choose, but I wouldn't bother.

Yes please looking forward to seeing that explanation. Particularly want to see the explanation of how I was able to recover information from a 16 stop underexposed image from my A7R, considering it has a "screen DR" of less than 13 stops and "information in a scene that exceeds that range will be lost and unrecoverable". ;D

Pointless as stated, but I have about one minute while my coffee brews so once more into the breach...

What do you need explained? The fact that a range has both lower and upper bounds? The fact that DR is a measure of the difference between those bounds? The fact that your 'proof':

index.php


...is so ridiculously far from simultaneously exceeding both of those bounds that it would be funny as a joke, but is just pathetic for your intent? The fact that the bounds of the range are defined by physics (FWC and read noise in e-), and not by any relationship to your camera's arbitrary algorithm for selecting a matrix-metered exposure on which your claim of a 16-stop underexposure is based?

I could go on, but as I stated...it's pointless, and my coffee is ready.
 
Upvote 0
neuroanatomist said:
msm said:
neuroanatomist said:
But some people – well, one person – apparently can't seem to come to grips with the fact that a screen DR of 13.9 stops means information in a scene that exceeds that range will be lost and unrecoverable. I suspect you can explain it more effectively if you choose, but I wouldn't bother.

Yes please looking forward to seeing that explanation. Particularly want to see the explanation of how I was able to recover information from a 16 stop underexposed image from my A7R, considering it has a "screen DR" of less than 13 stops and "information in a scene that exceeds that range will be lost and unrecoverable". ;D

Pointless as stated, but I have about one minute while my coffee brews so once more into the breach...

What do you need explained? The fact that a range has both lower and upper bounds? The fact that DR is a measure of the difference between those bounds? The fact that your 'proof':

index.php


...is so ridiculously far from simultaneously exceeding both of those bounds that it would be funny as a joke, but is just pathetic for your intent? The fact that the bounds of the range are defined by physics (FWC and read noise in e-), and not by any relationship to your camera's arbitrary algorithm for selecting a matrix-metered exposure on which your claim of a 16-stop underexposure is based?

I could go on, but as I stated...it's pointless, and my coffee is ready.

Metering has absolutely nothing to do with this. My basis for claiming 16 stops underexposure is simple, rawdigger shows me the brightest pixels in the exposure are near clipping in a 8 seconds exposure (but not a single pixel is clipped). Then I take another exposure at 1/8000s while keeping everything else the same (aperture, ISO, lighting). Going from 8 seconds to 1/8000 is lowering the exposure 16 stops, simple. So yeah you are right your post was completely pointless, but please share your vast expertise in physics etc and explain how all information suddenly is lost when you go below a SNR of 1. ;D
 
Upvote 0
News flash: changing the exposure conditions (shutter speed or aperture) changes the absolute luminance values over which the dynamic range is distributed. Is shifting the range synonymous with expanding it? Here's a novel thought...I wonder...if one could somehow take two different exposures and blend them...somehow...maybe that would improve DR? :o
 
Upvote 0
neuroanatomist said:
News flash: changing the exposure conditions (shutter speed or aperture) changes the absolute luminance values over which the dynamic range is distributed. Is shifting the range synonymous with expanding it? Here's a novel thought...I wonder...if one could somehow take two different exposures and blend them...somehow...maybe that would improve DR? :o

bracketing to increase DR always has issues
 
Upvote 0
emko said:
neuroanatomist said:
News flash: changing the exposure conditions (shutter speed or aperture) changes the absolute luminance values over which the dynamic range is distributed. Is shifting the range synonymous with expanding it? Here's a novel thought...I wonder...if one could somehow take two different exposures and blend them...somehow...maybe that would improve DR? :o

bracketing to increase DR always has issues

It was a nice idea, or so I thought...in retrospect, though, an unnecessary one. No need to bracket, just get an a7R...it can capture >16 stops of DR. That fact was proven by msm a few posts back. Well, at least his a7R can capture >16 stops of DR...I have no idea what the rest of the world is doing wrong that limits their a7R sensors to the laws of physics, I guess they just don't understand. ::)
 
Upvote 0
3kramd5 said:
jrista said:
These days, it's become fairly simple to me. These days, what I care about are the actual results.

Concur, and going back to the beginning of this reply, hence my suggestion that we define capture as the entire process of converting photons to charge, reading, amplifying, digitizing those data, and writing files. The files are the results. :)

Here is where the discrepancy lies, though. With a maximum precision of 11 bits in the two most precise values stores in a cRAW block (the rest are 7-bit offsets from those two)...how much DR do you have? There are some hardliners who would say you don't have more than 11 stops...however in practice that is clearly not the case. The sensor may be capable of 14 stops, or 15 stops, or 16 stops...and that original DR is being compressed to fit within a lower precision data file. The sensor itself might indeed be capable of 15 stops. Will hardliners accept that?

There is also the simple fact that dynamic range is really just a hardware thing. The term dynamic range is applied to RAW image files as a matter of course these days...however fundamentally, I don't think that is valid. A RAW image file has a signal to noise ratio...but it does not have dynamic range. The RAW image IS the signal, and that signal came off the sensor, which has dynamic range.

It's just not a simple situation anymore. :P Camera companies are employing different and alternative ideas in the way they process the data on the camera hardware and firmware. Some of them are clearly preserving more information, despite the fact that they are using less precision to store it. I wish it really was just as simple as 14 bit ADC, 14 bit file, max 14 stops of DR. I wish it was just as simple as Sony moving to a 16 bit ADC in the A7000 and storing their 15.5 stops of DR without compression or anything else as-is in a 16-bit data file. I would so much prefer that. But...it's just not that simple anymore.
 
Upvote 0
Well again outside of a subassy lab environment with specialty equipment (which sensor fab houses likely have and use to acceptance test production articles), the files are the best you can do. So it's good enough in my mind to treat the camera as a black box.

And sure, I'm talking about the output of the signal chain, not DR of the system, strictly speaking.
 
Upvote 0