I had bit more complex post about this later somewhere but any such math would be pretty useless practically because the value is inverted anyway.
But “absolute” EV values are not used in photography either…for at least two decades, since inception of digital cameras.
EV is primarily used as “offset” ( i.e “+2 EV” meaning two stops more light ), not as absolute table value (i.e “2 EV” being exact number resulting from combination of shutter and focal length normalized per ISO).
Why would you even need this? The full settings (Sensor size, ISO, Shutter, Focal Length) are identical between Corona and cameras. None of my cameras (Sony Alpha 7r series) have option to input absolute EV value, it’s long abandoned concept.
I am of opinion that Corona should go full way and allow EV modification even in full settings, so that is it absolutely identical to how digital cameras work. You set your settings (f-stop, shutter, iso..) and still have option to use EV as offset.
I’ll make that a request when I’ll remember.
@Juraj I recorded a short video in response to your question, but also to better illustrate why I posed this question in the first place (watch x1.25-1.5 speed).
EDIT: really sorry if I mispronounced your name(?)
If you want simple exposure to match photographic exposure by default, then set EV to -4.5 (or whatever you find appropriate) and save render settings as defaults. As Juraj already explained, there’s very good reason why simple exposure is set as it is and i really don’t see a reason why it should be changed. In fact i would be pretty upset if it would.
@Romullus Right, and your suggestion is a good one, although I am still curious what the conversion formula might be. I think it’s clear enough that -4.5 approaches a visually similar result, but if we follow the typical exposure formula:
I understand cjwidd’s request and the idea behind it. I will contact our devs to find out if there is some simple way to swap between EV and photographic values. My concern right now is that the photographic exposure is controlled by 3 parameters, so it appears to me that there will be actually an infinite number of possible combinations giving exactly the same EV equivalent. I guess providing a few examples, or locking two specific values at their defaults (e.g. shutter speed 1/50s and F 16) and providing the third one (ISO) would be enough here.
I don’t have any exact info yet, but here is how I started. Maybe someone has time and courage to take it further:
Created a scene with 0 black background
Placed a Corona Camera
Placed a plane
Painted the plane with Corona Color set to pure white plugged into self-illumination slot, self-illumination intensity set to 1
Used a secret spell to remove gamma 2.2
Rendered
This way we can read RGB values from the plane. Simple EV set to 0 gives Tonemapped sRGB 1, meaning that the surface has 1 Watt per steradian per square meter. Great.
So I tried with various simple EV values vs RGB and with various ISO settings vs RGB. I left shutter speed and f at 1 to simplify things.
I stored the results in Excel and drew a graph with extrapolation and showing the function which is used to draw the graphs.
Here is what I got:
EV = 1.4427LN(RGB)
ISO = 0.1757RGB
It is still guesswork, but it more or less works.
Now, with this, you can enter any RGB value and it will print the EV and ISO values for you. We would like to have EV<>ISO conversion, but I am simply too stupid for this.
I am sharing my XLS file “as is”, without any instructions.
The table you are interested in is the lowest one titled “ev and iso based on rgb”.
Scratch that, unless you want to have a for fun exercise. See the post below. evs2.xlsx (21.6 KB)
Here is an XLS where you can enter the fstop, shutter speed, and ISO values, and it will print the corresponding Corona EV. I doesn’t work the other way around, though. Photographic-to-CoronaEV.xlsx (11.9 KB)
That spreadsheet is cool thanks Maru!
Juraj posted a thing a while back (which i think he referenced above) that i found pretty interesting and is now basically how i set up every scene because its so formulaic and works every time.
This is exactly the type of thinking I was trying to address in the ‘Plz Halp’ thread. The idea of artistic freedom implies an unconstrained question; if you are a beginner, you do not know what the reasonable limitations are and that can lead to confusion.
As an interpretation, it might follow like this:
Step 0: add sun / sky
Step 1: adjust to ‘desired’ brightness
…
At that instant the formula is derailed because, as a beginner, what (visually) constitutes desired brightness?
At the same time, an inversion of that logic (Step 2), “It ends up being obviously realistic value: F8-F16” points to a range of conceivable values that help to constrain the question.
I’m not trying to castigate the very helpful suggestions that were being put forward in the quoted example, but I am vaguely asserting that there is a (sort of) quantitative approach to implementing photorealism in CG. When we use subjective terms to describe photorealism, we lose track of the question.
Inb4: ‘artistic freedom is what make great images’ → I’m not talking about artistic choices that make an image emotional or worthwhile. I’m talking about the qualities of an image that make it indistinguishable, or nearly indistinguishable, from a photograph.
Photorealism surely has to be subjective because its not measurable in itself. There isnt a metric for photorealism. But there are metrics for camera settings and physically based workflows that are ‘known good’ and produce consistent results. Outside of that, is where the sujective questions start like ‘how bright should it be’ or ‘are my shadows too dark’ etc. I think the best we can do is to build a physically plausible foundation in a scene and then do the art within those restrictions.
I don’t think there is a way to talk about photorealism without it being subjective.
Probably not - at least not in some constructive or meaningful way. That being said, what Ludvik points out in the ‘Time to ditch sRGB…’ - about how it would be better if the viewport camera defaulted to photographic emulation - would probably help alleviate some of the confusion.