How Clever is Sony’s Noise Reduction?

Following on from the ongoing discussions about the way the noise reduction on the PXW-FS5 works I’d like to try to answer a few points that have been raised.

Noise reduction is incorporated in to almost every single video camera on the market today. Without it cameras would not be achieving the sensitivity levels that we are becoming accustomed to. Big sensors have helped increase sensitivity, but noise reduction also plays a major part. 4 years ago the typical sensitivity of a video camera was around the equivalent of 300 ISO. Today 1000 ISO is common. The laws of physics have not changed but image processing has.

However image processing has limitations. Noise reduction is a trade off as it typically introduces other artefacts including blurring or softening of the image, smearing of the image when there is motion, posterisation, blockiness or banding.

The more noise you introduce into the image the harder the NR has to work and as a result the worse, or more noticeable the artefacts will become.

Every time you add 6dB of gain (or double the ISO) of a sensor you will also double the underlying noise level, that is a very significant noise increase.

Different sensors will exhibit different noise characteristics. A sensor with a very high pixel count may exhibit finer grain, but may be less sensitive, have aliasing issues, skew issues or heat problems. A sensor with fewer pixels may have coarser grain but be more sensitive have fewer aliasing issues, fewer skew issues and be less prone to overheating. A sensor with an excess of pixels compared to the final image resolution may be easier to noise reduce as the excess sensor resolution can be used during the NR process without degrading the end image, but the high pixel count may introduce some of the other issues listed above.

So to get an image with an acceptable noise level, low skew, a desirable level of sensitivity without overheating is a very fine balancing act. Different cameras will perform differently and each will have strength’s and weaknesses. A Sony A7S has big pixels, so it’s very sensitive and only needs low levels of NR at the base sensitivity compared to say an FS7 with it’s smaller pixels. But the A7S suffers from a lot of image skew that is unacceptable for many types of video production plus there are heat issues when shooting for long periods. Meanwhile the FS7, while less sensitive has very, very low skew levels and no overheating.

But what about the new PXW-FS5? There is much discussion about the noise reduction in this camera. First of all it is a different camera to any other. So it will not perform the same as any other. It uses a different combination of sensor and processing to any other camera on the market.

Does it perform as well as an A7R in low light? Actually it’s not all that different in terms of base sensitivity. What about if you add gain? Well the image quality of both cameras deteriorates when you add gain. Both become noisier and both have more NR artefacts. The A7RII is possibly a better performer in terms of noise and artefacts, maybe due to the higher pixel count allowing the use of a lot of pixel binning. Does this mean that the FS5 is somehow broken or defective? No, it just means that the A7RII has the edge in low light. Do remember that the A7RII suffers from a lot of image skew, really appalling flash band issues and overheats on long shots. Does that mean the A7RII is broken, because after all the FS5 doesn’t have these issues problems. Of course not, these are just limitations of these two very different cameras.

Anyway coming back to the noise reduction. As we can’t actually turn off the NR on the FS5 it’s hard to understand exactly how beneficial it is, even though it does introduce some inevitable artefacts (NR will always have undesirable side effects), especially when you add more than 6dB of gain. But we can get some clues. The edge tearing artefact that can be see on vertical motion at high gain levels appears to simply be noise leaking through the temporal NR when there is a lot of vertical motion, and it’s pretty obvious that there’s actually a lot of noise being hidden.

Why does this only occur in 4K? Well that’s probably because in HD the camera has a surplus of sensor resolution, so different noise reduction processes that soften the image can be used instead of temporal NR as the softening won’t be noticed in HD.

Another clue as to how well the NR works is that if you quickly switch the gain switch from one gain level to another it takes a couple of frames for the temporal NR to catch up so for one or two frames the temporal NR level is reduced (not eliminated just reduced a bit). If you look at these frames it gives some insight into how amazingly effective the temporal NR is and as well as temporal NR the FS5 is also employing spatial NR, so this is only part of the story.

I have a couple of frame grabs. One is a frame where the temporal NR is stabilised and doing it’s thing reducing the noise in the picture. This is with +12 dB of gain applied and to be honest it’s a pretty clean looking image for a 4000 ISO shot, imagine adding +24dB gain to an EX1 or PMW-500 to get up to 4000 ISO and what that would look like! The other frame is a frame grabbed as the camera is switching between +6dB to +12dB, so what you are seeing is about 6dB’s worth of temporal noise reduction. Just look at all that very nasty looking noise. Notice the very blocky areas in the shadows, in motion these can be seen to be fluttering from frame to frame as the NR kicks in, it’s really nasty. The noise is having a serious impact on the image resolution. On the far left table leg in the close up you can no longer see the wood grain. Now imagine what at least double if not 3 times that would look like because if you were to shoot at 3200 ISO with the standard gammas without NR, that’s what it’s going to look like. It would almost certainly overload the internal coded resulting in compression artefacts that you won’t see while shooting, only when you play the footage back when quite possibly it’s too late to do anything about it.

So next time you look at a noise reduction artefact do think about just how dreadful the image would look without any NR. We are not talking about seeing a little bit more noise and grain with reduced NR but a blizzard of noise and grain. It’s also worth remembering that all the camera manufacturers are doing this. Also consider what a typical 1/2″ or 2/3″ broadcast camera would look like with +24dB of gain added, it really would be unusable, yet the FS5 can deliver an image at 4000ISO that is really not all that bad. It’s not perfect, it does have some artefacts but really it’s quite remarkable what a camera like this can do thanks to modern noise reduction processes and large sensors.

Stable noise reduction at +12dB gain.
Stable noise reduction at +12dB gain.
Frame grab between +6dB and +12dB gain before the temporal noise reduction has fully kicked in.
Frame grab between +6dB and +12dB gain before the temporal noise reduction has fully kicked in.
FS5 at +12dB gain.
FS5 at +12dB gain.
Single frame during the transition from +6dB gain to +12dB gain before the noise reduction has full kicked in. Notice all the extra noise, now double this if you want an idea of how much noise the NR is dealing with when shooting at 3200 ISO with a standard gamma.
Single frame during the transition from +6dB gain to +12dB gain before the noise reduction has fully kicked in. Notice all the extra noise, now at least double this if you want an idea of how much noise the NR is dealing with when shooting at 3200 ISO with a standard gamma.

Temporal NR: Temporal noise reduction works by taking a single pixel and measuring it’s average output over several frames. Using this average value a correction can be applied to the current frame that helps reduce the instantaneous brightness fluctuations that are seen as noise. However if there is motion in that area this can create nasty local blurring or smearing effects. On option is to include a process that detects motion and locally reduces or eliminates the noise reduction during motion to counter the smear or blurring. Either way motion in the image introduces undesirable artefacts.

 

PXW-FS5 Factory Default Frame Grabs and Video (all at 0dB gain)

In my rush to get this out I made a mistake on one of the captions. The S-Log3 was shot at 3200ISO, not 1000ISO.

 

So here are some frame grabs from video shot today with my FS5. There is no image processing other than the grading of the S-log3 clip and the upscaling of the HD clips to UHD in the video.

Default factory settings or picture profiles were used. The footage was exported from Adobe Premiere CC using Media Encoder at 3840×2160, H264 at 75Mb/s for upload to YouTube and Vimeo. You should be able to download the UHD H264 file from Vimeo.  This is what it looks like out of the box. All the shots were done at the same aperture (f9) and shutter speed (1/50) and the native ISO or 0dB gain used in each case. This means that the S-log3 was around 1.5 stops over exposed, which is about optimum for S-log and an 8 bit codec. As you can see the pictures are low noise with no significant artefacts and no banding in the sky, clouds or any other areas. You can also see that the S-log3 grades really nicely when shot this way and results in a very low noise image. In the video clip I have included some pans and tilts and everything looks perfectly normal to me.

Click on the thumbnails of the still images to go to larger and full resolution UHD and HD frame grabs.

PXW-FS5 frame grab. UHD, factory default settings.
PXW-FS5 frame grab. UHD, factory default settings.
PXW-FS5 UHD Picture Profile 6. Cinegamma 2
PXW-FS5 UHD Picture Profile 6. Cinegamma 2
PXW-FS5 UHD Picture Profile 9, S-log3, ungraded.
PXW-FS5 UHD Picture Profile 9, S-log3, ungraded.
PXW-FS5 UHD Picture Profile 9, S-log3, Graded.
PXW-FS5 UHD Picture Profile 9, S-log3, Graded Shot at 3200 ISO not 1000 ISO as indicated in the caption.

Note that even though the S-log3 is 1.5 to 2 stops over exposed the cloud highlights are still well within range after grading. I could probably over exposed by a further stop and still had great looking highlights and even less noise. S-log really like being over exposed. Log is the exact opposite of standard gamma. With standard gamma you shoot protecting your highlights but with log you must shoot to protect your shadows.

PXW-FS5 50Mb/s HD, factory default settings.
PXW-FS5 50Mb/s HD, factory default settings.
PXW-FS5 50Mb/s HD, Picture Profile 5, Cinegamma 3
PXW-FS5 50Mb/s HD, Picture Profile 5, Cinegamma 3

My response to all the FS5 artefact issue complainers.

FS5 artefacts capI’m getting a bit fed up with this. So lets just clear a few things up.

PLEASE ALSO SEE THIS RELATED POST WITH SAMPLE FOOTAGE AND FULL RESOLUTION FRAME GRABS. https://www.xdcam-user.com/?p=4583

SEE SONY’S OFFICIAL STATEMENT ON THIS ISSUE.

Native ISO: The Sony PXW-FS5’s native ISO for the standard gammas and cinegammas is 1000 ISO. It is NOT 3200 ISO. If you shoot with standard or cinegammas at 3200 ISO then you are adding +10dB to +12dB of gain.

+10dB gain = noisy picture. If you add +10db of gain to most cameras the picture will get noisy and grainy, the FS5 is no exception to this. Adding +10db gain also means you will have a +10db noise increase (roughly 300% more noise, a significant increase) or have an increase in noise plus a significant increase in other artefacts as the cameras built in noise reduction has to work much harder. The FS5 does incorporate noise reduction processes and these do introduce a degree of smear when you add more than +6db of gain. At +12db or higher the smear and other artefacts (including a tendency towards banding) becomes quite noticeable, this is a typical artefact of this type of noise reduction and one of the reason why on more advanced cameras like the PMW-F5/F55 you are able to turn it off.

Ultra Compressed: In UHD the XAVC-L codec has a bit rate of 100Mb/s. Uncompressed UHD requires over 3.5Gb/s for decent quality, so you’re looking at a camera with a compression ratio of around 35:1. Is it really all that surprising that there are some compression artefacts? Consider that 35Mb/s is considered the minimum for broadcast quality H264 based HD work and that’s a compression ratio of only 25:1. So we are some way below the normal minimums for broadcast.

8 bit in UHD. UHD XAVC-L is an 8 bit codec. 8 bit codecs don’t deal with noise terribly well as the limited number of shades/steps mean that noise cannot be reproduced with small steps and as a result any noise or grain will often appear quite coarse. So is it any surprise that in UHD the camera exhibits a lot more artefacts than in HD where the codec is 10 bit and much less compressed?

S-log at high ISO’s. Oh come on people, please understand that S-log only does one thing well and that’s maximise dynamic range. If you can’t get a correct exposure or better still a 1 to 2 stop over exposed exposure at the native ISO you really, really shouldn’t be using log. It will be noisy, it will be grainy, it won’t look good and if you record it with XAVC-L in UHD it will look like rubbish as the excessive noise will stress the codec, introduce more artefacts and your exposure mid range will only represented by approx 17 code values or shades. you will have very little data to play with in post and noise and grain will look awful.

External Recorder. Adding an external recorder can really improve the UHD image quality. Again, this shouldn’t come as a surprise. If you use an external ProRes recorder running at 880Mb/s (ProRes HQ) compared to the 100 Mb/s of XAVC-L is it really any surprise that it’s possible to record a better quality image? The FS5 has been designed as a grab and go camera recording on to cheap media. Sure adding an external recorder can increase the image quality, but your media costs go through the roof and most of the grab and go benefits are lost.

So when you see a test of XAVC-L with a standard gamma at 3200 ISO being recorded using an 8 bit,  35:1 codec don’t be surprised to see a noisy, grainy image with compression artefacts from all the extra work the codec is having to do to deal with the noise that comes from adding +10db gain. The same for low light log footage at 6400 ISO. This is not the best way to use a camera like this. It’s not clever and anyone can make even a straight forward scene look like rubbish by shooting this way. I don’t know what people are trying to say or achieve when they post a bunch of high gain clips with headline titles like “The FS5 codec is broken” or “FS5 un-usable in UHD” without even considering what it is that they are actually looking at. AT 3200 ISO with standard gammas the camera noise reduction circuits are working overtime to try and clean up the image. This results in the introduction of other artefacts such as edge tearing or smear. Stick that into a super compressed codec and it is not going to be a perfect image. 50Mb/s HD at 60fps is also very highly compressed and will also exhibit artefacts.

As I have written in other articles, the use of ISO with video cameras appears to be miss-leading many people into thinking that a camera will produce a noise free image at all kinds of ridiculous sensitivities as they often focus on the wrong ISO rating or simply believe that it’s possible to have very high sensitivities without noise. Sadly this is not the case. I don’t think people would be surprised to see noise and grain at +10dB gain, but sadly dB’s of gain isn’t hip, cool or make you sound like a film cameraman. No, ISO is much cooler sounding, but is confusing the c**p out of people that don’t really understand how it works in relation to a video camera. Also the use of log for low light is just nuts, it’s entirely the wrong type of gamma to use, especially with a sub optimum codec.

The FS5 is not simply a shrunk down FS7. It is a very different camera. You should not be expecting FS7 performance in UHD, the UHD version of XAVC-L codec is very different to the XAVC-I available in the FS7. The image processing is also different (do remember the FS5 consumes 1/2 the power of an FS7).

It is possible that over future firmware updates Sony may be able to fine tune the codec and noise reduction circuits to work a little better. It’s also possible that we may see improvements in the decoders used to decode the codec (remember the decoder is just as important as the encoder), so possibly things may get improved a little. But don’t expect miracles. Squeezing UHD into a highly compressed 8 bit codec and recording it 100% reliably on off the shelf SD cards will always be a challenge. Even at the correct native ISO’s, at 0dB gain, there will be some artefacts. But start adding in gain and yes, you will start to see more noise and more artefacts.

The FS5 is a great little camera, I really enjoy shooting with mine and I think the results I am getting are great. I know that I can get a technically better 4K/UHD image from my FS7 or F5, but sometimes it’s not just about getting the best technical quality. The FS5 allows me to shoot more freely, it’s a breeze to carry around or travel with, I can throw it on a gimbal, on the end of a microphone boom pole, chuck it and a bunch of lenses in a small back-pack, it’s fun to use! As a result I’m getting shots that I just can’t get with the FS7 or F5.

Just how terrible is the FS5’s image quality? Take a look at my Falcon video and judge for yourself.

Northern Lights 2016: I still have 2 places left on my February expedition to Norway to the Finnmarksvidda, land of the Sami people and the Northern Lights. Full details here.

2 Places Remain for Norway 2016!

Aurora over a Fjord in Tromso.
Aurora over a Fjord in Tromso.

Unbelievably I still have two places left for my Northern Lights trip in February. Normally these tours sell out well in advance, but I’ve had a number of cancellations, re-bookings and other changes that mean that there are still 2 places left. These trips really are a big, exciting adventure. We stay in at an amazing location miles from the nearest town and only accessible by snow scooter. We go ice fishing, cook out in a Sami tent, go dog sledding, snowmobiling and enjoy traditional saunas. The sun is still very active and the Aurora has been amazing this winter. It probably won’t be this good in 2017 and then we will go into the low side of the 11 year sunspot cycle, so it could be a long wait for the next big show. Full details are here: https://www.xdcam-user.com/northern-lights-expeditions-to-norway/

PXW-FS5 Firmware Version 1.1 Released.

Sony have released the version 1.1 firmware update for the PXW-FS5 which allows you to output 4K over the HDMI while recording 4K on the SD cards. However it does appear that at the moment at least it is impossible to output 4K, Record internal 4K AND have a picture on the LCD or EVF. Lets hope this gets resolved later in time. It also adds auto focus face detection in 4K. Click on the link below to go to the download page:

http://www.sony.co.uk/pro/support/software/SW_122115_PSG/1

Video Camera Noise, ISO and Sensitivity.

It’s amazing how poorly this is understood. I’m also rather surprised at some peoples expectations when it comes to noise in shadow areas of video images.

First of all, all video camera sensors produce noise. There will always be noise to some degree and this is typically most visible in the darker parts of the image because if your actual image brightness is 5% and your noise is 5% the noise is as big as the desired signal. In the highlights the same noise is still there, but when the brightness is 80% and the noise is 5% the noise is much, much less obvious.

ISO: What is ISO with a video camera? On it’s own it’s actually a fairly meaningless term. Why? Well because a camera manufacturer can declare more or less any ISO they choose as the cameras sensitivity. There is no set standard. It’s up to the camera manufacturer to pick an ISO number that gives a reasonably bright image with an acceptable amount of noise. But what is acceptable noise? Again there is no standard, so ISO ratings should be ignored unless you also know what the signal to noise ratio is at that ISO. For decades video camera sensitivity was rated in db. The sensitivity  is measured at 0db in terms of the aperture needed to correctly expose a 90% white card  at 2000 lux. This is very precise and easily repeatable. The signal to noise ratio is then also measured at the unity (0db) gain point and from this you can actually get a really good understanding of how that camera will perform, not just sensitivity, but more importantly how much noise at the nominal native sensitivity.

But now, because it’s fashionable and makes us sound like film camera operators it’s all about ISO. But ISO on it’s own doesn’t really tell us anything useful. Take a Sony FS7 or F5. In standard gamma at 0db the ISO rating is 800 ISO. But when you switch to S-Log it becomes 2000 ISO (but you are still at 0db). Have you ever noticed that the image doesn’t get brighter even though you are increasing the ISO? The ISO is increased because what is actually happens is that you gain the ability to record a little over 1 stop further into the shadows as you are now using more of the sensors low range (which is normally well below the black level chosen for 709) with the side effect of also seeing a little more than twice as much more noise (1 stop = 6db = double). The camera isn’t actually becoming any noisier, but because your using a lower sensor range you will see more noise in the shadows, noise that in normal gammas goes unseen. It’s really important that you understand this as it explains why S-log looks very noisy in the deepest shadows compared to standard gammas.

Native sensitivity… again this is open to a bit of wriggle room by the camera manufacturer. With a camera shooting log, generally it is a case of mapping the entire sensor capture range from black to white to the zero to 100% recording range. Normally this is done using as little gain as possible as gain adds noise. But as noise reduction processes get better, including on sensor noise reduction, camera manufacturers have some space to move the mapping of the sensor to the recording up and down a bit. Sadly or us, high ISO’s sell cameras. So camera manufacturer’s like to have cameras with high ISO’s because people look at the ISO rating, but ignore the signal to noise figure. The end result is cameras with high ISO’s (because it sounds cool) but with less than optimum signal to noise ratios. It would probably be better for all of us if we started paying much more attention to the signal to noise ratios of cameras, not just the ISO. That may help prevent manufacturers from bring out cameras with ridiculously high native ISO’s that are noisy and frankly far from what we need, which is a good low noise base sensitivity.

The next issue is that people appear to expect to be able to magically pull something out of nothing. If you have areas of deep shadow in your image you can’t magically pull out details and textures from those areas without significantly increasing the noise in those parts of the picture. You can’t do it and you shouldn’t be trying to do it. If you have an 8 bit camera the noise in the shadows will be really coarse, you try to stretch those levels, even by a tiny bit, it’s going to get ugly fast (the same with 12 bit linear raw too). What’s the answer…. LIGHT IT PROPERLY OR EXPOSE IT BRIGHTER.

We appear to have lost the ability to light or expose properly. If you want detail in your shadows either expose them brighter or throw some light in there, then take the levels down in post. Remember it’s all about contrast ratios. Faces are normally 1.5 stops above middle grey and 3.5 stops above our dark shadow range. So if you want a lot of textures in your deep shadows expose the entire scene brighter, not just the foreground but the background and shadows too. If you expose faces at +4.5 above black. Mid grey will still be -1.5 stops below those skin tones and your shadows will still be 3.5 stops below your faces. the contrast ratio remains the same if you increase the overall light level, so now everything will be 1 stop brighter. Then take the levels down by 1 stop in post and bingo, you noise levels are cut in half and your shadows look so much better and might actually now contain some useable picture information.

To follow on from this I recommend reading this: https://www.xdcam-user.com/2015/03/what-is-exposure/

Deeper Understanding Of Log Gamma. Experiments with a Waveform Display.

I started writing this as an explanation of why I often choose not to use log for low light. But instead it’s ended up as an experiment you can try for yourself if you have a waveform monitor that will hopefully allow you to better understand the differences between log and standard gamma. Get a waveform display hooked up to your log camera and try this for yourself.

S-Log and other log gammas are wonderful things, but they are not the be-all and end-all of video gammas. They are designed for one specific purpose and that is to give cameras using conventional YCbCr or RGB recording methods the ability to record the greatest possible dynamic range with a limited amount of data, as a result there are some compromises made when using log. Unlike conventional gammas with a knee or gammas such as hypergammas and cinegammas, log gammas do not normally have any highlight roll off, but do have a shadow roll-off. Once you get above middle grey log gammas normally record every stop with almost exactly the same amount of data, right up to the clipping point where they hard clip. Below middle grey there is a roll off of data per stop as you go down towards the black clip point (as there is naturally less information in the shadows this is expected). So in many respects log gammas are almost the reverse of standard gammas. The highlight roll off that you may believe that you see with log is often just the natural way that real world highlights roll off anyway, after all there isn’t an infinite amount of light floating around (thank goodness). Or that apparent roll off is simply a display or LUT limitation.

An experiment for you to try.

Click on the chart to go to larger versions that you can download. Display it full screen on you computer and use it as a test chart. You may need to de-focus the camera slightly to avoid aliasing from the screens pixels.
Click on the chart to go to larger versions that you can download. Display it full screen on your computer and use it as a test chart. You may need to de-focus the camera slightly to avoid aliasing from the screens pixels.

If you have a waveform display and a grey scale chart you can actually see this behaviour. If you don’t have a chart use the grey scale posted here full screen on your computer monitor. Start with a conventional gamma, preferably REC-709. Point the camera at the chart and gradually open up the aperture. With normal gammas as you open the aperture you will see the steps between each grey bar open up and the steps spread apart until you reach the knee point, typically at 90% (assuming the knee is ON which is the default for most cameras).  Once you hit the knee all those steps rapidly squash back together again.

What you are seeing on the waveform is conventional gamma behaviour where for each stop you go up in exposure you almost double the amount of data recorded, thus capturing the real world very accurately (although only within a limited range). Once you hit the knee everything is compressed together to increase the dynamic range using only a very small recording range, leaving the shadows and all important mid range well recorded. It’s this highlight compression that gives video the “video look”, washed out highlights with no contrast that look electronic.

If you repeat the same exercise with a hypergamma or cinegamma once again in the lower and mid range you will see the steps stretch apart on the waveform as you increase the exposure. But once you get to about 65-70% they stop stretching apart and now start to squeeze together. This is the highlight roll off of the hypergamma/cinegamma doing it’s thing. Once again compressing the highlights to get a greater dynamic range but doing this in a progressive gradual manner that tends to look much nicer than the hard knee. Even though this does look better than 709 + Knee in the vast majority of cases, we are still compressing the highlights, still throwing away a lot of data or highlight picture information that can never be recovered in post production no matter what you do.

Conventional video = Protect Your Highlights.

So in the conventional video world we are taught as cameramen to “protect the highlights”. Never overexpose because it looks bad and even grading won’t help a lot. If anything we will often err on the side of caution and expose a little low to avoid highlight issues. If you are using a Hypergamma or Cinegamma you really need to be careful with skin tones to keep them below that 65-70% beginning of the highlight roll off.

Now repeat the same experiment with Slog2 or S-log3. S-log2 is best for the experiment as it shows what is going on most clearly. Before you do it though mark middle grey on your waveform display with a piece of tape or similar. Middle grey for S-log2 is 32% (41% for S-log3).

Now open up the aperture and watch those steps between the grey scale bars. Below middle grey, as with the standard gammas you will see the gap between each bar open up. But take careful note of what happens above middle grey. Once you get above middle grey and all the way to the clip point the gap between each step remains the same.

So what’s happening now?

Well this is the S-log curve recording each stop above middle grey with the same amount of data. In addition there is NO highlight roll off. Even the very brightest step just below clipping will be same size as the one just above middle grey. In practice what this means is that it doesn’t make a great deal of difference where you expose for example skin tones, provided they are above middle grey and below clipping. After grading it will look more or less the same. In addition it means that that very brightest stop contains a lot of great, useable picture information. Compare that to Rec-709 or the Cinegammas/Hypergammas where the brightest  stops are all squashed together and contain almost no contrast or picture information.

Now add in to the equation what is going on in the shadows. Log has less data in the shadows than standard gammas because you are recording a greater overall dynamic range, so each stop is recorded with overall less data.

Standard Gammas = More shadow data per stop, much less highlight data = Need to protect highlights.

Log= Less shadow data per stop, much more highlight data = Need to protect shadows.

Hopefully now you can see that with S-log we need to flip the way we shoot from protecting highlights to protecting shadows. When you shoot with conventional gammas most people expose so the mid range is OK, then take a look at the highlights to make sure they are not too bright and largely ignore whats going on in the shadows. With Log you need to do the opposite. Expose the mid range and then check the shadows to make sure they are not too dark. You can ignore the highlights.

Yes, thats’ right, when shooting log: IGNORE the highlights!

Cinegamma highlight roll off. Note how the tree branches in the highlights look strangled and ugly due to the lack of highlight data, hence "protect your highlights".
Cinegamma highlight roll off. Note how the tree branches in the highlights look strangled and ugly due to the lack of highlight data, hence “protect your highlights”.
Graded S-Log2. Note how nice the same tree branches look because there is a lot of data in the highlights, but the shadows are a little crunchy. Hence: protect your shadows.
Graded S-Log2. Note how nice the same tree branches look because there is a lot of data in the highlights, but the shadows are a little crunchy. Hence: protect your shadows.

For a start you monitor or viewfinder isn’t going to be able to accurately reproduce the highlights as bright as they are . So typically they will look a lot more over exposed than they really are. In addition there is a ton of data in those highlights that you will be able to extract in the grade. But most importantly if you do underexpose your mid range will suffer, it will get noisy and your shadows will look terrible because there will be no data to work with.

When I shoot with log I always over expose by at least 1 stop above the manufacturer recommended levels. If you are using S-log2 or S-log3 that can be achieved by setting zebras to 70% and then checking that you are JUST starting to see zebras on something white in your shot such as a white shirt or piece of paper. If your camera has CineEI use an EI that is half of the cameras native ISO (I use 1000 or 800 EI for my FS7 or F5).

I hope these experiments with a grey scale and waveform help you understand what is going on with you gamma curves. One thing I will add is that while controlled over exposure is beneficial it can lead to some issues with grading. That’s because most LUT’s are designed for “correct” exposure so will typically look over exposed. Another issue is that if you simply reduce the gain level in post to compensate than the graded footage looks flat and washed out. This is because you are applying a linear correction to log footage. Fo a long tome I struggled to get pleasing results from over exposed log footage. The secret is to either use LUT’s that are offset to compensate for over exposure or to de-log the footage prior to grading using an S-Curve. I’ll cover both of these in a later article.

Chart showing S-Log2 and S-Log3 plotted against f-stops and code values.
Chart showing S-Log2 and S-Log3 plotted against f-stops and code values.

 

 

 

 

 

 

 

 

 

What about shooting in low light?

OK, now lets imagine we are shooting a dark or low light scene. It’s dark enough that even if we open the aperture all the way the brightest parts of the scene (ignoring things like street lights) do not reach clipping (92% with S-Log3 or 109% with S-Log2). This means two things. 1: The scene has a dynamic range less than 14 stops and 2: We are not utilising all of the recording data available to us. We are wasting data.

Log exposed so that the scene fills the entire curve puts around 100 code values (or luma shades) per stop above middle grey for S-log2 and 75 code values for S-Log3 with a 10 bit codec. If your codec is only 8 bit then that becomes 25 for S-log2 and 19 code values for S-Log3. And that’s ONLY if you are recording a signal that fills the full range from black clip to white clip.

3 stops below middle grey there is very little data, about thirty 10 bit code values for S-Log2 and about 45 for S-log3. Once again if the codec is 8 bit you have much less, about 7 for S-Log2 and about 11 for S-log2. As a result the darker parts of your recorded scene will be recorded with very little data and very few shades. This impacts how much you can grade the image in post as there is very little picture information in the darker parts of the shot and noise tends to look quite coarse as it is only recorded with a limited number of steps or levels (this is particularly true of 8 bit codecs and an area where 8 bit recordings can be problematic).

So what happens if we use a standard gamma curve?

Lets say we now shoot the same scene with a standard gamma curve, perhaps REC-709. One point to note with Sony cameras like the FS5, FS7, F5/F55 etc is that the standard gammas normally have a native ISO one to two stops lower than S-Log. That’s because the standard gammas ignore the darkest couple of stops that are recorded when in log. After all there is very little really useable picture information down there in all the noise.

Now our limited dynamic range scene will be filling much more of our recording range. So straight away we have more data per stop because we are utilising a bigger portion of the recording range. In addition because our recorded levels will be higher in our recording range there will be more data per stop, typically double the data especially in the darker parts of the recorded image. This means than any noise is recorded more accurately which results in smoother looking noise. It also means there is more data available for any post production manipulation.

But what about those dark scenes with problem highlights such as street lights?

This an area where Cinegammas or Hypergammas are very useful. The problem highlights like strret lights normally only make up a very small part of your your overall scene. So unless you are shooting for HDR display it’s a huge waste to use S-log just to bring some highlights into range as you make big compromises to the rest of the image and you’ll never be able to show them accurately in the finished image anyway as they will exceed the dynamic range of the TV display.  Instead for these situations a Hypergamma or Cinegamma works well because below about 70% exposure Hypergammas and cinegammas are very similar to Rec-709 so you will have lots of data in the shadows and mid range where you really need it. The highlights will be up in the highlight roll off area where the data levels or number of recorded shades are rolled off. So the highlights still get recorded, perhaps without clipping, but you are only giving away a small amount of data to do this. The highlights possibly won’t look quite as nice as if recorded with log, but they are typically only a small part of the scene and the rest of the scene especially the shadows and mid tones will end up looking much better as the noise will be smoother and there will be more data in that all important mid-range.

 

The Falcon. PXW-FS5 short film.

Filmed and edited in 2 day as part of the PXW-FS5 launch event in Dubai this short film shows off some of the features of the FS5. Many shots make use of the Supers Slow Motion mode, shooting at 240fps. Others take advantage of the cameras lightweight where we mounted the camera on a DJI Romin M gimbal. The time-lapse shots were done using S&Q motion shooting at 1fps, often with a 1 second shutter. I used a mix of Cinegamma 3 and S-Log2 for the shoot depending on the required dynamic range. Lenses used include Zeiss Loxia 35mm and 50mm. A sigma 18-250mm (canon mount), the Sony 18-105mm and a Sigma 18-35mm Art lens on a cheap Fotga E-Mount to Canon tilt adapter. I will follow this up with a behind the scenes video in a week or so.

USA Workshop Tour. December 2015.

965437_547020302056401_894467613_oI’m going to be in the US at the end of December holding a number of  2 hour seminars and full day workshops. The 2 hour seminars are being sponsored by Sony and will give an overview of how to get the very best from the Sony PMW-F5 and PMW-F55 cameras.

As well as these seminars (which will be well worth attending) I am also running some in depth full day workshops on gamma, colorspace and log aimed at anyone that really wants to know how to get the very best from their cameras, whether that’s an FS5, FS7 or F5/F55. The S-Log Demystified workshops will be in-depth and limited in numbers so plenty of time to answer any questions and help every attendee individually. These workshops will be interesting, informative and really help people get the very best from their cameras when shooting with S-log or even with other log gamma curves. They will include hints and tips that make using log really easy, explain why log works so well and teach you how to adapt your exposure techniques to get the best possible log footage. I promise you will learn a lot. Earlybird rates are available for the AbelCine workshops.

December 11th, Omega Broadcast, Austin, Texas.  2 hour Seminars. 

December 14th, AbelCine, Los Angeles. Full day intensive workshop.

December 16th, Minneapolis, Z-Systems Inc. 5pm to 8pm inc 2 hour seminar.

December 18th, AbelCine, Chicago. Full day intensive workshop. 

December 21st, AbelCine, New York. Full day intensive workshop.