Follow along with the video below to see how to install our site as a web app on your home screen.
Note: this_feature_currently_requires_accessing_site_using_safari
Monstor Highlight
[/url]Untitled_1.1.16++4 by rand thompson, on Flickr[/IMG]![]()
Alexa Highlight
[/url]Arri highlight_1.1.1+42 by rand thompson, on Flickr[/IMG]![]()
if I keep the same +- depth of field as ALexa the result on Monstro is this.
https://www.dropbox.com/s/peiu3yas6cde7k8/A003_C004_0414ZV.0000000F.R3D?dl=0
"Same Depth of Field'
Monstro
![]()
I don't think it's the issue. Exposure shouldn't be determined by sensor or film size.
BUT, IMHO, it's just that the base iso to have the same DR in the highlights from mid gray and + or - the "same" noise floor is 800 on Alexa and 1600+ on Monstro.
Pat
PAt, but 'if we want to get the same depth of field of a s35 we have to close the diaphragm. So if I have to make a comparison with ALexa or Dragon 5k, I should have the same type of image or as similar as possible.
So at T5.6 on Monstro on Alexa or dragon 5k the diaphragm is more open.
This would lead to having similar high lights or better to say the total DR would be equal from medium gray up.
Or am I wrong?
Ok so if you close the iris to get the same depth of field, do you compensate the exposure by changing the shutter speed or ND filter?
Ok so if you close the iris to get the same depth of field, do you compensate the exposure by changing the shutter speed or ND filter?
I put ND to ALexa.
By doing this I noticed the same depth of field in the image with full frame Monstro.
This deduction led me to say that if we have and want the same depth of field on ALexa s35 and Monstro full frame VV the Highlights are practically at the same breaking point.
As you say, I could at this point raise the ISO to 1600 and close the diaphragm of 1 stop on Monstro or put an ND on ALEXA and open 1 stop . But still Monstro has less noise and more resolution.
I hope I made myself understand eheheh
When making an objective measurement (of any kind), it is helpful to keep that measurement in mind. A general principle of the Scientific Method is to eliminate as many extraneous variables as possible so that the effect of only the most important (hopefully one) is most visible. If you want to measure sensitivity, or noise, or resolution, or contrast, or depth of field, or perspective, or color accuracy, or highlight clipping, or size, or weight, or power consumption, or battery life, or resale value, or ... it is best to set up a test that really shows that makes everything else equal so that the single variable can be evaluated. The more variables you have to look at AT THE SAME TIME, the more you venture from quantitative fact to qualitative narrative.
If it's too distracting to see very different DOF between two imaging systems, using an ND filter to eliminate the DOF variable is a good idea. If the ND itself doesn't disrupt the test in other ways. So first you have to prove that the ND changes exposure but not any other "important" criteria, and once that's done, you can use it to eliminate the DOF difference. If the ND introduces a color shift (either due to IR pollution or some other reason), then it's not necessarily helping your test.
Many years ago some newbies posted a test comparing RED with an EOS 5d2 and found no real differences in image quality. What they really demonstrated was that if you ignore enough variables and then overlook any results that contradict your initial narrative, you can claim anything. A good test is clear in what it's trying to measure (not "I just threw on some lenses to see what would happen"), clear in its methodology, transparent with its data (not "the R3D files are too big to post, but trust me when I say that these thumbnails prove you cannot see a difference"), and faithful in its summary findings (not "the chromatic aberration you see in these tests never bears out in real-world scenarios").