Remix.run Logo
▲ klodolph a day ago

Yeah. I’m not really a professional here but I would say sensitometry is something of an interest of mine. Take what I’m saying with the appropriate grain of salt.

Your camera has some sensor which records some range of values. The range is a lot wider than your monitor can reproduce and generally follows some curve up to a maximum value, where the highlights clip.

Log is something of a fantasy in that it represents an idealized, mathematical idea of what your camera does, but it does not really correspond to what the sensor does or what the monitor displays. You can convert your video to log, or from log, but the log data itself is only really useful as an intermediate step when post-processing. I don’t think you need to capture in log. I would just go for some “regular” wide like Canon’s Wide DR.

YMMV, I am a little old-school about these things and there is a lot of stuff that I prefer to do in-camera. (Be warned that while doing things in post gives you flexibility to undo your work and change your mind, there are a lot of things you can’t reasonably do in post… even things that seem basic like white balance are better to do with lighting or filters, and if you don’t understand the sensitometry then you can easily end up with footage that you can’t rescue in post.)

▲davidgay a day ago | parent | next [-]

The one thing worth considering here is that the noise is intrinsically (short of a handy laser illuminated scene IIUC) proportional to the sqrt of the illumination level. So we should recored in sqrt for better coding efficiency/range :)

▲weinzierl a day ago | parent | prev | next [-]

"there are a lot of things you can’t reasonably do in post"

I have my own list of these things. Mine is a bit general, including for example the anti-aliasing filter, and polarizers. I'm curious about yours. Would you mind to share?

▲t0bia_s a day ago | parent [-]

Properly lit scene. If you have huge contrast in scene, you cannot reproduce it on common display with attitude of having everything unclipped.

▲weinzierl a day ago | parent [-]

This is probably the most important one.

▲112233 a day ago | parent | prev [-]

I am even less of a professional and this whole field looks exactly like audiophile snake oil peddling. "log" makes total sense because codec cannot encode full precision sensor values (otherwise, just save that!) Any floating point is "log". As long as image carries color space and the mapping LUT, you can convert it into a linear space, which is only thing that makes sense for most operations. Instead, people are taking these "shmony super log8 plus ultra" files, and looking at them directly! they say "log looks flat", they adjust contrast and curves on it, ... How is that making any sense? What "look"? Why is reversing any such LUTs not done automatically? Super weird

▲KaiserPro a day ago | parent | next [-]

log _was_ a compromise. It allowed one to do film scanning at the right level between precision and storage.

cineon, which is where you could argue that log came from, was a 10bit format to represent something that could have easily been 16bit. The compromise was that you kept the precision in the blacks for recovery, but with the ability to actually handle the files on hardware at the time. (bear in mind that realtime 10bit colour playback at 2/4k required a rack full of harddrives up until at least 2010 (see baselight 8 hardware))

I would hope there are 14 and 16 bit formats that come out of the camera that allow you to have some sort of linearish recording. Now that sensors are actually capable of capturing a dynamic range greater than top end film stock. However light isn't linear, so log is actually closer to how we see than linear is.

What ever it is, there are many levels of hidden LUTs to get the camera to record in a way that its meant to. what ever you are doing involves fiddling someone else LUTs

▲adgjlsfhk1 10 hours ago | parent [-]

the downside of 14/16 bit is that cameras are storage bandwidth constrained. Higher bit width directly competes against resolution/framerate

▲112233 2 hours ago | parent [-]

That part makes sense. But why then go and start applying operations that require linear colorspace (contrast, blur and sharpness, brightness, scaling and rotation etc etc) to data that is not in linear colorspace? Like, zero tutorials on "how to grade log" I have seen starting with "first we convert to linear colorspace such as Blah". What is this about? Because it looks totally wild and I assume I am missing something, the punchline.

▲jiggawatts a day ago | parent | prev [-]

Video formats historically did not include gamut information, made wild assumptions, etc.

So when log formats were introduced, you had to know the color space and undo the mapping semi-manually!

DaVinci Resolve — a colourist tool ffs — just got automatic color space detection a couple of versions ago!

Compared to still image photography where color management is the default, videography is insane.