One of THE most common complaints I hear, day in, day out, is: There is banding in my footage.
Before you start complaining about banding or other image artefacts ask yourself one very simply, but very important question: Do I know EXACTLY what is happening to my footage within my computer or playback system? As an example, editing on a computer your footage will be starting of at it’s native bit depth. It might then be converted to a different bit depth by the edit or grading software for manipulation. Then that new bit depth signal is passed to the computers graphic card to be displayed. At this point it will possibly be converted to another bit depth as it passes through the GPU and then it will be converted to the bit depth of the computers desktop display. From there you might be passing it down an HDMI cable where another bit depth change might be needed before it finally arrives at your monitor at goodness knows what bit depth.
The two images below are very telling. The first is a photo of a high end TV connected to my MacBook ProRetina via HDMI playing back a 10 bit ProRes file in HD. The bottom picture is exactly the same file being played back out of an Atomos Shogun via HDMI to exactly the same TV. The difference is striking to say the least. Same file, same TV, same resolution. The only difference is the top one is playing back off the computer, the lower from a proper video player. I also know from experience that if I plug in a proper video output device such as a Blackmagic Mini-monitor to the laptops Thunderbolt port I will not see the same artefacts as I do when using the computers built in HDMI.
And this is a not just a quirk of my laptop, my grading suite is exactly the same. If I use the PC’s built in HDMI the pictures suck. Lots of banding and other unwanted artefacts. Play back the same clip via a dedicated, made for video, internal PCI card such as a Decklink card and almost always all of the problems go away. If you use SDI rather than HDMI things tend to be even better.
So don’t skimp on your monitoring path if you really want to know what your footage looks like. Get a proper video card, don’t rely on the computers GPU. Get a decent monitor with an SDI input and try to avoid HDMI for any critical monitoring.
Once upon a time it was really simple. We made TV programmes and videos that would only ever be seen on TV screens. If you lived and worked in a PAL area you would produce programmes at 25fps. If you lived in an NTSC area, most likely 30fps. But today it’s not that simple. For a start the internet allows us to distribute our content globally, across borders. In addition PAL and NTSC only really apply to standard definition television as they are the way the SD signal is broadcast with a PAL frame being larger than an NTSC one and both use non-square pixels. With HD Pal and NTSC does not exist, both are 1280×720 or 1920×1080 and both use square pixels, the only difference between HD in a 50hz country and a 60hz country is the frame rate.
Today with HD we have many different frame rates to choose from. For film like motion we can use 23.98fps or 24fps. For fluid smooth motion we can use 50fps or 60fps. In between sits the familiar 25fps and 30fps (29.97fps) frame rates. Then there is also the option of using interlace or progressive scan. Which do you choose?
If you are producing a show for a broadcaster then normally the broadcaster will tell you which frame rate they need. But what about the rest of us?
There is no single “right” frame rate to use. A lot will depend on your particular application, but there are some things worth considering.
If you are producing content that will be viewed via the internet then you probably want to steer clear of interlace. Most modern TV’s and all computer monitors use progressive scan and the motion in interlaced content does not look good on progressive TVs and monitors. In addition most computer monitors run by default at 60hz. If you show content shot at 25fps or 50fps on a 60hz monitor it will stutter slightly as the computer repeats an uneven number of frames to make 25fps fit into 60Hz. So you might want to think about shooting at 30fps or 60fps for smoother less stuttery motion.
24fps or 23.98fps will also stutter slightly on a 60hz computer screen, but the stutter is very even as 1 frame gets repeated in every 4 frames shown. This is very similar to the “pull-up” that gets added to 24fps movies when shown on 30fps television, so it’s a kind of motion that many viewers are used to seeing anyway. Because it’s a regular stutter pattern it tends to be less noticeable in the irregular conversion from 25fps to 60hz. 25 just doesn’t fit into 60 in a nice even manner. Which brings me to another consideration – If you are looking for a one fits all standard then 24 or 23.98fps might be a wise choice. It works reasonably well via the internet on 60hz monitors. It can easily be converted to 30fps (29.97fps) using the pull-up for television and it’s not too difficult to convert to 25fps simply by speeding it up by 4% (many feature films are shown in 25fps countries simply by being sped up and a pitch shift added to the audio).
So, even if you live and work in a 25fps (Pal) area, depending on how your content will be distributed you might actually want to consider 24, 30 or 60fps for your productions. 25fps or 50fps looks great on a 50hz TV, but with the majority of non broadcast content being viewed on computers, laptops and tablets 24/30/60fps may be a better choice.
What about the “film look”? Well I think it’s obvious to say that 24p or 23.98p will be as close as you can get to the typical cadence and motion seen in most movies. But 25p also looks more or less the same. Even 30p has a hint of the judder that we see in a 24p movie, but 30p is a little smoother. 50p and 60p will give very smooth motion, so if you shoot sports or fast action and you want it to be smooth you may need to use 50/60p. But 50/60p files will be twice the size of 24/25 and 30p files in most cases, so then storage and streaming bandwidth have to be considered. It’s much easier to stream 24p than 60p.
For almost all of the things that I do I shoot at 23.98p, even though I live in a 50hz country. I find this gives me the best overall compatibility. It also means I have the smallest files sizes and the clips will normally stream pretty well. One day I will probably need to consider shooting everything at 60fps, but that seems to be some way off for now, HDR and higher resolutions seem to be what people want right now rather than higher frame rates.
This is a question that comes up time and time again. I’ve been using the F5 and FS7 for almost 5 years. What I’ve discovered in that time is that the one thing that people notice more than anything from these cameras is noise if you get your exposure wrong. In addition it’s much harder to grade a noisy image than a clean one.
Lets take a look at a few key things about how we expose and how the F5/FS7 works (note the same principle applies to most log based cameras, the FS5 also benefits from being exposed brighter than the suggested base settings).
What in the image is important? What will your audience notice first? Mid-range, shadows or highlights?
I would suggest that most audiences first look at the mid range – faces, skin tones, building walls, plants etc. Next they will notice noise and grain or perhaps poor, muddy or murky shadows. The last thing they will notice is a few very brightly highlights such as specular reflections that might be clipped.
The old notion of protecting the highlights comes from traditional gamma curves with a knee or highlight roll off where everything brighter than a piece of white paper (90% white) is compressed into a very small recording range. As a result when shooting with conventional gamma curves ALL of the brighter parts of the image are compromised to some degree, typically showing a lack of contrast and texture, often showing some weird monotone colors. Log is not like that, there is no highlight roll off, so those brighter than white highlights are not compromised in the same way.
In the standard gammas at 0dB the PXW-FS7, like the PMW-F5 is rated at 800 ISO. This gives a good balance between noise and sensitivity. Footage shoot at 0dB/800ISO with the standard gammas or Hypergammas generally looks nice and clean with no obvious noise problems. However when we switch to log the native ISO rating of the cameras becomes 2000 ISO, so to expose “correctly” we need to stop the aperture down by 1.3 stops. This means that compared to 709 and HG1 to HG4, the sensor is being under exposed by 1.3 stops. Less light on the sensor will mean more noise in the final image. 1.3 stops is the equivalent of 9dB. Imagine how Rec709 looks if it is under exposed by 1.3 stops or has to have +9dB of gain added in. Well – thats what log at 2000 ISO will look like.
However log has lots of spare headroom and no highlight compression. So we can choose to expose brighter than the base ISO because pushing that white piece of paper brighter in exposure does not cause it to become compressed.
If you open the aperture back up by 1.3 stops you get back to where you would be with 709 in terms of noise and grain. This would be “rating” the camera at 800 ISO or using 800 EI. Rating the camera at 800EI you still have 4.7 stops of over exposure range, so the only things that will be clipped will in most cases be specular reflections or extreme highlights. There is no TV or monitor in existence that can show these properly, so no matter what you do, they will never be true to life. So don’t worry if you have some clipped highlights, ignore them. Bringing your exposure down to protect these is going to compromise the mid range and they will never look great anyway.
You should also be extremely cautious about ever using an EI higher that 2000. The camera is not becoming more sensitive, people are often misslead by high EI’s into thinking somehow they are capturing more than they really are. If you were to shoot at 4000 EI you will end up with footage 15dB noisier than if you were shooting the same scene using 709 at 800 ISO. That’s a lot of extra noise and you won’t necessarily appreciate just how noisy the footage will be while shooting looking at a small monitor or viewfinder.
I’ve been shooting with the F5 and then the FS7 for almost 5 years and I’ve never found a situation where I going to an EI higher than 800 would have resulted in a better end result. At the same time I’ve seen a lot of 2000 EI footage where noise in the mid range has been an issue, one particular example springs to mind of a high end car shoot where 2000 EI was used but the gloss and shine of the car bodywork is spoilt because it’s noisy, especially the darker coloured cars.
Of course this is just my opinion, based on my own experience, others may differ and the best thing you can do is test for yourself.
The workshops are sponsored by Sony and are free. I’ll be covering a full end to end workflow from composition, to lighting, exposure with different gammas, workflow and post production as well as HDR.
Raw is the unprocessed (or minimally processed) data direct from the sensor. It is just the brightness value for each of the pixels, it is not a color image, but we know which color filter is above each pixel, so we are able to work out the color later. In the computer you take that raw data and convert it into a conventional color video signal defining the gamma curve and colorspace in the computer. This gives you the freedom to choose the gamma and colorspace after the shoot and retains as much of the original sensor information as possible.Of course the captured dynamic and color range is determined by the capabilities of the sensor and we can’t magically get more than the sensor can “see”. The quality of the final image is also dependant on the quality of the debayer process in the computer, but as you have the raw data you can always go back and re-encode the footage with a better quality encoder at a later date. Raw can be compressed or uncompressed. Sony’s 12 bit FS-raw when recorded on an Odyssey or Atomos recorder is normally uncompressed so there are no additional artefacts from compression, but the files are large. The 16 bit raw from a Sony F5 or F55 when recorded on an R5 or R7 is made about 3x smaller through a proprietary algorithm.
ProRes is a conventional compressed color video format. So a ProRes file will already have a pre-determined gamma curve and color space, this is set in the camera through a picture profile, scene file or other similar settings at the time of shooting. The quality of the ProRes file is dependant on the quality of the encoder in the camera or recorder at the time of recording, so there is no way to go back and improve on this or change the gamma/colorspace later. In addition ProRes, like most commonly used codecs is a lossy compressed format, so some (minimal) picture information may be lost in the encoding process and artefacts (again minimal) are added to the image. These cannot easily be removed later, however they should not normally present any serious problems.
It’s important to understand that there are many different types of raw and many different types of ProRes and not all are equal. The FS-raw from the FS5/FS7 is 12 bit linear and 12 bit’s are not really enough for the best possible quality from a 14 stop camera (there are not enough code values so floating point math and/or data rounding has to take place and this effects the shadows and low key areas of the image). You really need 16 bit data for 14 stops of dynamic range with linear raw, so if you are really serious about raw you may want to consider a Sony F5 or F55. ProRes is a pretty decent codec, especially if you use ProResHQ and 10 bit log approaches the quality of 12 bit linear raw but without the huge file sizes. Incidentally there is very little to be gained by going to ProRes 444 when recording the 12 bit raw from an FS5/FS7, you’ll just have bigger files and less record time.
Taking the 12 bit raw from an FS5 and converting it to ProRes in an external recorder has potential problems of it’s own. The quality of the final file will be dependant on the quality of the debayer and encoding process in the recorder, so there may be differences in the end result from different recorders. In addition you have to add a gamma curve at this point so you must be careful to choose the correct gamma curve to minimise concatenation where you add the imperfections of 12 bit linear to the imperfections of the 10 bit encoded file (S-Log2 appears to be the best fit to Sony’s 12 bit linear raw).
Despite the limitations of 12 bit linear, it is normally a noticeable improvement over the FS5’s 8 bit internal UHD recordings, but less of a step up from the 10 bit XAVC that an FS7 can record internally. What it won’t do is allow you to capture anything extra. It won’t improve the dynamic range, won’t give you more color and won’t enhance the low light performance (if anything there will be a slight increase in shadow noise and it may be slightly inferior in under exposed shots). You will have the same dynamic and color range, but recorded with more “bits” (code values to be precise). Linear raw excels at capturing highlight information and what you will find is that compared to log there will be more textures in highlights and brighter parts of your captured scenes. This will become more and more important as HDR screens are better able to show highlights correctly. Current standard dynamic range displays don’t show highlights well, so often the extra highlight data in raw is of little benefit over log. But that’s going to change in the next few years so linear recording with it’s extra highlight information will become more and more important.
Just a reminder to anyone using a viewfinder fitted with an eyepiece, magnifier or loupe not to leave it pointing up at the sun. Every year I see dozens of examples of burnt and damaged LCD screens and OLED displays caused by sunlight entering the viewfinder eyepiece and getting focussed onto the screen and burning or melting it.
It can only take a few seconds for the damage to occur and it’s normally irreversible. Even walking from shot to shot with the camera viewfinder pointed towards the sky can be enough to do damage if the sun is out.
So be careful, cover or cap the viewfinder when you are not using it. Tilt it down when carrying the camera between locations or shots. Don’t turn to chat to someone else on set and leave the VF pointing at the sun. If you are shooting outside on a bright sunny day consider using a comfort shade such as an umbrella or large flag above your shooting position to keep both you and the camera out of the sun.
Damage to the viewfinder can appear as a smudge or dark patch on the screen that does not wipe off. If the cameras was left for a long period it may appear as a dark line across the image. You can also sometimes melt the surround to the LCD or OLED screen.
As well as the viewfinder don’t point your camera directly into the sun. Even an ND filter may not protect the sensor from damage as most regular ND filters allow the infra red wavelengths that do much of the damage straight through. Shutter speed makes no difference to the amount of light hitting the sensor in a video camera, so even at a high shutter speed damage to the cameras sensor or internal ND’s can occur. So be careful when shooting into the sun. Use an IR ND filter and avoid shooting with the aperture wide open, especially with static shots such as time-lapse.
The short answer is it all depends on the camera you are using. With the F55 or F65 then S-Log2/S-Gamut and S-Log3/S-Gamut3 will give you a larger range of colours in your final image than S-Log3/S-Gamut3.cine. But if you have a PMW-F5, PXW-FS7 or PXW-FS5 this is not going to be the case.
What is Gamut?
The word Gamut means the complete range or scale of something. So when we talk about Gamut in a video camera we are talking about dynamic range and color range (colorspace) taken together. Then within the Gamut we can break that down into the dynamic range or brightness range which is determined by the gamma curve and the color range which is determined by the colorspace.
Looking at the current Sony digital cinema cameras you have a choice of 3 different gamuts when the camera is in log mode plus a number of conventional gamuts you get when shooting rec-709, rec-2020 or any other combination of rec-709 color with cinegammas or hypergammas.
Log gamma and gamuts.
But it’s in the log mode where there is much confusion. When shooting with log with the current cameras you have 3 recommended combinations.
The S-log2 and S-log3 gamma curves both capture the same dynamic range – 14 stops, there is no difference in the dynamic range captured.
In terms of the range of colors that can be recorded S-Gamut and S-Gamut3 are the same size and the largest recording colorspaces the cameras have. S-Gamut3.cine is a smaller colourspace but still larger than P3 (digital cinema projection) or rec-709.
But those were all designed for the F55 and F65 cameras that have extremely high quality (expensive) colour filters on their sensors. The reality is that the F5/FS7/FS5 sensor cannot see the full range of any of the S-Gamut colorspaces so in reality you gain very little by using the larger versions. Don’t expect to see a noticeably greater range of colours than any of the other colour modes if you have the F5/FS7/FS5. But all the LUT’s designed for these cameras are based on the S-Gamuts and if you want to mix an FS5 with an F55 in one production it helps to use the same settings so that grading will be easier. It is worth noting at this point that most natural colors do fall within Rec-709, so while it is always nicer to have a bigger color range it isn’t the end of the world for most of what we shoot.
S-Log3 is a great example of what it means to have a bigger recording range than the camera can “see”. S-log3 is based on the Cineon film transfer log gamma curve developed back in the late 1980’s. Cineon was carefully tailored to match film response and designed around 10 bit data (as that was state of the art back then). It allows for around 16 stops of dynamic range. Much later, Arri and many others then adapted Cineon for use in video cameras – The “C” in Arri’s LogC stands for Cineon.
When Sony started doing wide dynamic range cameras they developed their own log gammas starting with S-Log, then S-Log2. These curves are matched very precisely to the way a video sensor captures a scene rather than film. In addition they are matched to the sensors actual capture range, S-Log can record 13 stops as that’s what the sensors in the cameras with S-Log can see. Then S-Log2 is 14 stops as the second generation cameras can all see 14 stops. As a result of being purpose designed for a video sensor, when using S-Log2 you maximise the entire recording range because the sensor is matched to the log which is matched to the record range.
But, these curves drew much criticism from early adopters and colorists because they were very different from the Cineon curve and all the other log curves based on this old school film curve. Colorists didn’t like it because none of their old Cineon LUT’s would work as expected and it was “different”.
In response to this Sony then developed S-Log3 and surprise, surprise – S-log3 is based on Cineon. So S-log3 is based on a 16 stop film transfer curve, but the current cameras can only see 14 stops. What this means is that the top 14% of the gamma curve is never used (that’s where stops 15 and 16 would reside) and as a result s-Log3 tops out at 92% and never gets to the 107% that S-Log2 can reach. If Sony were to release a 16 stop camera then S-Log3 could still be used and then it would reach 107%.
Coming back to colorspace. If you understand that the sensor in the F5/FS7/FS5 cannot see the full colour range that S-Gamut or S-Gamut3 are capable of recording then you will appreciate that like S-log3 (that is larger than the camera can see and therefore part empty) many of the possible code values available in S-Gamut are left empty. This is a waste of data. So from a colourspace point of view the best match when shooting log for these cameras is the slightly smaller colorspace S-Gamut3.cine. But S-Gamut3.cine is meant to be matched with S-Log3 which as we have seen wastes data anyway. If the camera is shooting using a 10 bit codec such as XAVC-I or XAVC-L in HD there are plenty of code values to play with, so a small loss of data has little impact on the final image. But if you are recording with only 8 bit data, for example XAVC-L in UHD then this does become much more of a problem and this is when you will find that S-Gamut with S-Log2 is going to give a better result as S-Log2 was designed for use with a video sensor from day 1 and it maximises the use of what little data you have.
Having done a fair bit of shooting with the new and very nice Fujinon MK 18-55mm E-Mount lens I decided to take a much closer look at the Fujinon Cabrio XK6x20 20 to 120mm T3.5 lens with the servo hand grip.
The price of this lens is very competitive and it can now be found as low as £11K/$16K. Lets not try to pretend that good quality PL mount zooms are cheap, but this is a great price for what is very high quality glass. The 20 to 120mm zoom range is nice and of course it’s truly parfocal there is a back focus adjuster along with macro function.
Like the other similar ENG style PL zooms this lens is quite heavy. The front element of the lens is huge and I’m sure a lot of the weight comes from this big lump of glass. One of the nice things about this lenses baby brother the MK 18-55, is that the 18-55 is really very light, which is great on the smaller cameras like the FS5 or FS7.
The 20-120mm Cabrio exudes quality. The build quality of the lens is wonderful, the witness marks are crisp and well engraved, the servo zoom is silky smooth. The large servo module acts as a handgrip just like traditional ENG lenses and it really comfortable to hold and use this way. But if you don’t need it it can be easily removed leaving the bare bones lens body and saving a little bit of weight. There are the usual 0.8 mod pitch gears on each of the focus zoom and iris rings. Focus ring travel is huge at about 200 degrees and due to the physical size of the lens this is as much as I’d ever want. Even towards infinity there is still a nice range of travel so focussing accurately on distant objects is easy.
But what about the image quality, how does the lens perform in real world situations?
To find out I used it for a shoot in Norway. The shoot was for TV manufacturer Philips. We wanted to obtain some high quality 4K HDR footage to show off the capabilities of a new 4K OLED Ambilight TV. Unfortunately the weather conditions on the shoot were pretty grim most of the time and this made it all the more challenging. But I’m pleased to say that both lenses performed very well despite snow, ice and cold.
One of the great things about having both the high end Cabrio 20-120mm and the budget friendly 18-55mm for the shoot was that the overall look of the images from the FS5 and F5 was the same. Often mixing lenses from different manufacturers results in different looking images giving the colourist more work to do in post. Fujinon now have a range of lenses to suit most budgets from the high end Cabrio 19-90mm T2.9 down through the Cabrio 20-120 T3.5 to the MK 18-55 T2.9.
So what do the images from these lenses look like? I’m afraid I can’t show any of the footage from the Philips shoot yet, I should be able to show it later in the year. Below are a couple of frame grabs to give you an idea of the kind of images you can get. We didn’t shoot the same shots with the F5/XK6x20 and FS5/MK18-55 at the same time, I was the only cinematographer. So I don’t have a side by side comparison from the shoot, but the different scenes shot with each lens/camera combo match really well.
TESTING BOTH LENSES:
In order to better directly compare the two lenses I shot some test shots. The XK6x20 on my F5 and the MK18-55 on my FS7. Both cameras were set to the same settings and hypergamma 3 with the cinema matrix used. The images you will see below have not been touched, this is how they looked straight from the camera. If you click on the picture you should get a link to the full frame 4K image, but do remember this are Jpegs.
I tried to get the same shots with both combinations but you will see some small variations. I apologise for that. To give as fair a comparison as possible I did most of the shots at 20mm and 55mm, but then in addition shot at 18mm on the MK18-55 and 120mm on the XK6X20 so you can see the additional range each lens offers.
First test was of a neighbours Cherry tree in blossom.
The next test was a simple setup shot of a couple of beer bottles on a table with strong sunlight from above and behind to create deep contrast. I wanted to see if either lens showed signs of loosing shadow detail due to the very large, very bright table top introducing flare into the shadows.
My conclusion with the above shots is that there is remarkably little difference between these two lenses. Both perform extremely well. I think the XK6X20 might be marginally sharper at the wide end than the 18-55mm, either that or the slightly better viewfinder of the F5 is allowing me to focus more precisely. In addition I think the bokeh of the more expensive Cabrio is marginally smoother than the 18-55, but again it’s a tiny difference (not as big as the difference in white balance of the two cameras).
Finally a shot of my ugly mug just so you can take a look at some skin tones.
Again very little difference between these lenses which is a good thing. Both perform very well, both produce pleasing images. Sure the XK6X20 20-120mm is more than twice the price of the MK18-55 but then it does offer twice the zoom range and it’s very hard to make fast parfocal lenses with big zoom ranges for large sensors. There will be a companion MK50-135mm lens coming later in the year, so with both the MK lenses you will be able to get the full range of the XK6X20 and a bit more, provided you don’t mind swapping lenses. It’s a tough choice if you have an E-mount Sony camera, which to get? For E-Mount I think the pair of MK lenses will be the way to go. If you have a PL mount camera the XK6X20 has to be a very serious contender. It’s a great all-round cinema zoom lens and a realistic price. Whichever way you do go you won’t be disappointed, these are proper cinema lenses.
I have just return from one of the most challenging shoots I have been involved in. The shoot took place over 5 days in and around Tromso in Norway. The aim was to gather footage to show off the capabilities of a new type of 4K TV from Phillips.
We shot the Northern Lights, we shot dog sledding , snow mobiles, shots of the city and sailing on the fjords. Each part of the shoot had many challenges and a lot of the shoot took place at night and at night the crew slept in cabins, tents and on the yachts. Shooting from the ice and snow covered deck of a yacht in temperatures well below zero is not something I enjoyed. And to top it all off the weather was pretty grim fro most of the shoot. Heavy snow showers, freezing temperatures and towards the end strong winds.
Because image quality is paramount for this project I choses to use the best lenses I could, but at the same time space and time constraints dictated that zoom lenses would be desirable. We were shooting 16 bit raw as well as XAVC class 480 on my PMW-F5 and some pick-up shots in UHD XAVC-L on a PXW-FS5. For the PMW-F5 the primary lens was the Fujinon Cabrio XK6x20, 20-120mm PL zoom and to ensure we had similar looking images from the FS5 I used the new Fujinon XF 18-55mm. I have to say that I’m quite in love with both of these lenses.
The Cabrio 20-120 is a beautiful lens and it’s really nice to have a servo zoom that is truly parfocal. The 20-120 produces really nice images even in the most challenging of conditions and at T3.5 it’s reasonably fast throughout the entire zoom range. This was the lens that I used for the majority of the shoot, in particular for the many night scenes we shot. The E-Mount 18-55 on the FS5 produces images that matched really well with the bigger lens and camera. This is a combination I would love to use on more shoots where the budget will allow.
One particular scene that we had to shoot was particularly challenging. It was a set up shot of a night time arrival of a couple of snowmobiles at a Sami camp site. The Sami people are the indigenous people of Northern Norway and they have a particular style of tent know as a Laavu which is similar to a teepee or wigwam. The idea behind the shot was to have the snow scooters arriving with headlights blazing and for the drivers to then enter the tent lit only by the light of a campfire inside the tent. At the time of the shoot it was snowing heavily and was totally dark. Turn off the lights of the snowmobiles and you could not see a thing.
While modern cameras like the F5 are very sensitive, the light of a campfire inside a tent will not adequately light a scene like this on it’s own. I didn’t want a totally dark background, so I decided that I would subtly light the trees of the forest that we were in to add some drama and give some depth to the background and a sense of being in a forest.
As we were travelling continuously on this shoot there was no space for a large or complex lighting kit and the remote location meant we needed battery powered lights. In addition I knew before we left that there was a chance of bad weather so I needed lights that would work whatever mother nature decided to throw at us.
I decided to take a set of 3 Light & Motion Stella battery powered LED lights. It’s just as well I had the Stella lamps as on top of all the other difficulties of the shoot the weather decided it was not going to play ball. We had to shoot the scene (and much of the shoot) in the middle of a snow storm. Fortunately the Stella lights are completely waterproof, so I didn’t need to worry about rain or snow protection. Just set them up turn them on and use the built in dimmer to set the light output.
To light the scene I set up a Stella Pro 5000 in the woods behind the Sami tent, aimed through the trees and pointed directly towards the camera. I chose to backlight the trees to provide a sense of there being trees rather than lighting them. I felt this would look less lit than throwing a ton of light into the forest from the front and I’m pleased with the result.
The Stella Pro 5000 is very bright for a compact battery operated light, it’s 5000 lumen 120 degree output that is pretty close to what you would get from a 200W HMI, it’s very bright. It has a very high CRI and gives out great quality daylight balanced light. It was positioned so that the light itself was behind the tent on a small bank, about 20m back in the woods. You couldn’t see it in the shot, but the light coming through the trees created shafts of light in the snow and the trees appeared as silhouettes. It added depth and interest to what would have otherwise been a near totally black background.
Then to provide a small amount of light so that we could see the riders of the snow scooters as they walked to the tent I used a Stella 2000. I didn’t really want the light from this lamp to be too obvious as this would really make the scene look “lit”. I didn’t need the full 2000 lumen output so I used the built in dimmer to reduce the output to around 70%.
The third light was a small Stella 1000 and this was placed inside the tent with a scrunched up orange gel. The Stella 1000 would typically be used as a camera top light, but it’s full dimmable and produces a very high light quality, making it suitable for many applications. The creases and folds in the orange gel helped break up the light a little creating a less lit look sympathetic to the fire inside the tent.
It allowed me to increase the illumination in the tent, adding to the light from the fire without it being obvious that the tent interior was lit. For some of the shots I had an assistant sit in the tent, out of shot and slowly move the gel in front of the light to add a little movement to the light to mimic the firelight even better.
At the moment I can’t show you the footage. That will have to wait until after the launch of the TV. But I’m really pleased with the way this scene came out. It’s challenging trying to shoot in the dark, in a blizzard, in temperatures well below freezing. Every aspect of getting this scene was hard. Opening a flight case to get out some kit meant getting snow on everything inside it. Just positioning the light up the woods was tough, the snow was up above my knees as I waded through it. Operating the camera is so much harder when it has a rain cover on it. The viewfinder was constantly misting up as snow fell on it non stop. Seeing the witness marks on the lens is difficult (although thankfully the marks on the Fujinon 20-120 are huge and easy to see).
But sometimes it’s challenges like these that make the job interesting. I know I was cursing and swearing at times trying to make these shots work, but seeing the scene come to life in the grade is all the more rewarding.
I’ll be writing more about the Fujinon 20-120 very soon, so why not subscribe to my blog using the subscribe bottom on the left.
The PXW-FS5 and PXW-Z150 will both get a free firmware update some time around June that will add the ability to shoot using a special gamma curve called “Hybrid Log Gamma” or HLG.
In the case of the FS5 this will be added through an additional picture profile, PP10. As well as HLG the camera will also have the ability to record using Rec2020 color. As a result the camera will become compatible with the new Rec2100 standard for HDR television.
In addition the FS5 will get the ability to change the base ISO for S-Log2 and S-Log3 from 3200 ISO to 2000 ISO. This will help produce cleaner images that are easier to grade. On top of that via a paid firmware update you will be able to shoot continuously at up to 120fps in full HD, no need to use the Super Slow Motion memory cache function.
These are all great upgrades for this little highly versatile camera.
By selecting Picture Profile 10 the camera will shooting using Hybrid Log Gamma. If you were to plug the camera into an HDR TV that supports HLG then what you would see on the TV would be a HDR image with an extended dynamic range. This should give brighter more realistic highlights and a quite noticeable increase in overall contrast compared to SDR (Standard Dynamic Range). There will be no need to grade the footage to get a perfectly watchable vibrant HDR image. The real beauty of HLG (developed by the BBC and NHK) is that it is backwards compatible with normal SDR (Standard Dynamic Range) TV’s. So feed the very same signal into a conventional SDR TV and it will look just fine. Skin tones will be a touch darker than with Rec709 and it won’t be HDR, but it will be perfectly watchable picture and most people won’t realise it’s anything different to normal SDR TV.
So HLG provides a simple very fast, direct HDR workflow that is backwards compatible with SDR TV’s. As a result you don’t need any special monitors to shoot with it, you can just monitor with existing SDR monitors, although it would be beneficial to have an HDR monitor to check the HDR aspect of the signal. HLG isn’t designed to be graded, although a little bit of post production tweaking can be applied, just as with Rec709. Bottom line is it’s quick and easy, no special monitors or skills needed – simples.
If you want the very best possible HDR then you should shoot with S-Log2/S-Log3 or raw and then grade the material in post using an HDR capable monitor. But that takes time and large HDR monitors are not cheap (for a small monitor you could use an Atomos Flame or Inferno). The FS5 will give you the ability to work either way. HLG for simple and quick, S-Log for the best possible image quality.
Hopefully we will see HLG rolled out to other cameras in the near future.
Camera setup, reviews, tutorials and information for pro camcorder users from Alister Chapman.