Tag Archives: FS5

FS5 Eclipse and 3D Northern Lights by Jean Mouette and Thierry Legault.

Here is something a little different.

I few years ago I was privileged to have Jean Mouettee and Thierry Legault join me on one of my Northern Lights tours. They were along to shoot the Aurora on an FS100 (it might have been an FS700) in real time. Sadly we didn’t have the best of Auroras on that particular trip. Theirry is famous for his amazing images of the Sun with the International Space Station passing in front of it.

iss_atlantis_transit2_2010 FS5 Eclipse and 3D Northern Lights by Jean Mouette and Thierry Legault.
Amazing image by Thierry Legault of the ISS passing in front of the Sun.

Well the two of them have been very busy. Working with some special dual A7s camera rigs recording on to a pair of Atomos Shoguns, they have been up in Norway shooting the Northern Lights in 3D. You can read more about their exploits and find out how they did it here: https://www.swsc-journal.org/articles/swsc/abs/2017/01/swsc170015/swsc170015.html

To be able to “see” the Aurora in 3D they needed to place the camera rigs over 6km apart. I did try to take some 3D time-lapse of the Aurora a few years back with cameras 3Km apart, but that was timelapse and I was thwarted by low cloud. Jean and Thierry have gone one better and filmed the Aurora not only in 3D but also in real time. That’s no mean feat!

20170218_233041_rec FS5 Eclipse and 3D Northern Lights by Jean Mouette and Thierry Legault.
One of the two A7s camera rigs used for the real time 3D Aurora project. The next stage will use 4 cameras in each rig for whole sky coverage.

If you want to see the 3D movies take a look at this page: http://www.iap.fr/science/diffusion/aurora3d/aurora3d.html

I’d love to see these projected in a planetarium or other dome venue in 3D. It would be quite an experience.

Jean was also in the US for the total Eclipse in August. He shot the eclipse using an FS5 recording 12 bit raw on a Atomos Shogun. He’s put together a short film of his experience and it really captures the excitement of the event as well as some really spectacular images of the moon moving across the face of the sun. I really shows what a versatile camera the FS5 is.

If you want a chance to see the Northern Lights for yourself why not join me next year for one of my rather special trips to Norway. I still have some spaces. http://www.xdcam-user.com/northern-lights-expeditions-to-norway/

Advertisements

The Pro’s and Con’s of 12 bit linear raw or recording raw to S-Log.

UPDATE: JUST TO BE CLEAR, THERE IS NOTHING WRONG WITH SONY’S 12 BIT LINEAR RAW. BUT YOU REALLY SHOULD BE AWARE OF IT’S LIMITATIONS COMPARED TO 16 BIT RAW OR POSSIBLY EVEN 10 BIT LOG.

This came up in the comments today and it’s something that I get asked about quite a lot.

Sony’s high end cameras, designed for raw – F5, F55, F65 all use 16 bit linear data. This linear data contains an impressively large amount of picture information across the entire range from the darkest shadows to the brightest highlights. This huge amount of data gives footage that can be pushed and pulled in post all over the place. 16 bit raw gives you 65,536 discreet values.

The FS7 and FS5 use 12 bit linear raw. 12 bit data gives you 4096 discreet values, 1/15th of the values, a small fraction of what 16 bit has. This presents a problem as to record 14 stops with linear data you need more than 12 bits.

Not Enough Code Values.

There just aren’t enough code values with only 12 bits (which is why no one else does it). So Sony do some clever math to make it workable. This reduces the amount of tonal steps in in the shadows.  On it’s own this isn’t a huge problem, just make sure you expose brightly to avoid trying to pull to much info out of the shadows and definitely don’t use it for low light. On high key scenes 12 bit raw is very nice indeed, this is where it excels. On low key scenes it can appear very grainy, noisy and shadows often look coarse and lack smooth textures. Expose nice and bright and you will get great highly gradable footage. Expose dark and you will have big problems.

Transcoding can add to the problems.

Where you really can run into problems is if you take 12 bit raw (with it’s reduced shadow data) and convert that to 10 bit log (which has reduced highlight data relative to the scene you are shooting).

What you end up with is 10 bit log with reduced shadow data compared to a straight 10 bit log recording. If you compare the direct 10 bit S-log from an FS7 (or F5/F55) to 10 bit S-log derived from 12 bit raw from an FS5, the FS7 picture will have a little more shadow information while the highlights from both will be similar. So the 10 bit direct log recording from an FS7 will typically be a little better than the 12  bit raw derived log from an FS5 in the shadows (but the raw derived 10bit log will always be better than 8 bit log).

If 4K S-Log is really important to you – get an FS7, F5 or F55.

So I’d much rather have an FS7 (F5 or F55) if I want to shoot UHD or 4K S-log. That’s what these cameras are designed for. But, if you only have an FS5, the raw to log workflow will outperform the limited 8 bit UHD log, so it is still definitely beneficial for FS5 owners to shoot raw and convert it to 10 bit S-Log with an external recorder. But better still record raw, then you really will have a better image.

Raw with the FS7.

On the FS7 the benefits of recording 12 bit raw over 10 bit S-Log are less clear. For bright, well exposed scenes the 12 bit raw will  have a definite  edge. But the files you will create if using an Atomos or Convergent Design recorder are huge compared to the compressed internal recording and that needs to be considered. For low key or under exposed scenes there is no benefit to shooting 12 bit raw you will get nothing extra.

On the FS7 it is not a good idea to take the 12 bit raw output and record it as 10 bit S-Log on an external recorder. While you may have a less compressed codec, you will be compromising the shadows compared to the cameras own internally generated 10 bit log recordings.  In most cases you would be better off simply taking the HDMI output and recording that as it avoids the 12 bit linear shadow bottleneck.

Again though – exposing nice and bright is the key to a good result. Get the data up into the brighter parts of the recording and the raw can be fantastic.

Internal and external log brightness shifts.

When you record S-Log internally on the Sony cameras the recordings use full range data levels to maximise the codec performance. You can use data range (which exceeds the normal video range) as it is assumed the data will be graded and as part of this process restored to video range data for viewing. However when recording on an external recorder the recordings sometimes use full video range rather than data range or if it’s data range don’t have the right metadata. This shouldn’t be a huge problem if the grading software behaves itself and treats each type of content correctly, shifting each to one unified range, but sadly this is rarely the case (especially with Adobe). So not only do the internal and externally recorded images come out with different brightness and contrast, but also LUT’s designed for one don’t work the same with the other. It’s a bit of a minefield to be honest and one of the reason why I prefer to always grade with dedicated grading software like resolve which handles the levels conversions properly (most of the time at least).

What’s the difference between raw and S-Log ProRes – Re: FS5 raw output.

This is a question that comes up a lot.

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.

Raw and the PXW-FS5

This isn’t a “how to” guide. There are many different recorders that can be used to record raw from the FS5 and each would need it’s own user guide. This is an overview of what raw is and how raw recording works to help those that are a bit confused, or not getting the best results.

First of all – you need to have the raw upgrade installed on the FS5 and it must be set to output raw. Then you need a suitable raw recorder. Just taking the regular SDI or HDMI output and recording it on an external recorder is not raw.

Raw is raw data direct from the cameras sensor with very little image processing. It isn’t even a color image, it won’t become color until some external processing, often called “De-Bayer” is done to convert the raw data to a color image.

For raw to work correctly the camera has to be set up just right. On the FS5 you should use Picture Profile 7. Don’t try and use any other profile, don’t try and shoot without a profile. You must use Picture Profile 7 at it’s factory default settings. In addition don’t add any gain or change the ISO from 3200 (2000 ISO from version 4.02 firmware). Even if the scene is a dark one, adding gain will not help and it may in fact degrade the recorded image.

White balance is set using the appropriate SGamut + color temperature preset chosen from within Picture Profile 7, there are only 3 to choose from for S-Gamut, but with a raw workflow you will normally fine tune the white balance in post. No other color matrix or white balance method should be used. Trying to white balance any other way may result in the sensor data being skewed or shifted in a way that makes it hard to deal with later on.

All of the above is done to get the best possible, full dynamic range data off the sensor and out of the camera.

If you are viewing the S-Log2 (ie don’t have viewfinder gamma assist enabled) then the exposure level that Sony recommend is to have a white card at 60%. So consider setting the zebras to 60%. Don’t worry that this may look a bit dark or appear to be a low level, but that’s the level you should start with… More about exposure later on.

This raw data is then passed down the SDI cable to the external recorder. The external recorder will then process it, turn it into a color signal (de-bayer) and add a gamma curve so that it can be viewed on the recorders screen. Exactly what it will look like on the monitor screen will depend on how the recorder is set up. IF the recorder is set to show S-Log2, then the recorders screen and the FS5’s LCD should look similar. However you might find that it looks very different to what you are seeing on the FS5’s LCD screen. This is not unexpected. If the recorder is setup to convert the raw to Rec-709 for display then the image on the recorder will be brighter and show more contrast, in fact it should look “normal”.

Under the surface however, the external raw recorder is going to be doing one of two things (normally at least). It’s either going to be recording the raw data coming from the camera as it is, in other words as raw. Or it will be converting the raw data to S-Log2 and recording it as a conventional ProRes or DNxHR video file. Either way when you bring this footage in to post production it will normally appear as a flat, low contrast S-Log2 image rather than a bright, contrasty rec-709 image. So understand that the footage will normally need to be graded or have some other changes made to it to look nice.

Recording the actual raw data will give you the best possible information that you can get from the FS5 to work with in post production. The downside is that the files will be huge and will take a fair amount of processing power to work with. Recording a ProRes or DNxHR video file with S-Log2 gamma is second best. You are throwing away a bit of image quality (going from 12 bit linear down to 10 bit log) but the files should still be superior to the 8 bit UHD internal recordings or even an external recording done via the HDMI which is also limited to 8 bit in UHD.

Most raw recorders have the ability to add a LUT – Look Up Table – to the image viewed on the screen. The purpose of the LUT is to convert the S-Log2/raw to a conventional gamma such as Rec-709 so that the picture looks normal. If you are using a LUT then the normal way to do things is to view the normal looking picture on the recorders screen while the recorder continues to record S-Log2 or raw. This is useful as the image on the screen looks normal so it is easier to judge exposure. With a 709 LUT you would expose the picture so that the image on the recorders screen looks as bright as normal, skin tones would be the usual 70% (ish) and white would be 90%.

There is a further option and that is to “bake in the LUT”. This means that instead of just using the LUT to help with monitoring and exposure you actually record the image that you see on the recorders screen. This might be useful if you don’t have any time for grading, but… and it’s a big BUT…. you are now no longer recording S-log2 or raw. You will no longer have the post production grading flexibility that raw or S-Log2 provide and for me at least this really does defeat the whole point of recording raw.

Exposure: Raw will not help you in low light. Raw needs to be exposed brightly (there are some data limitations in the shadows with 12 bit linear raw compared to 16 bit raw and possibly even 10 bit log). If viewing S-Log2 then Sony’s recommendation is to have a white card or white piece of paper at 60%. I consider that to be the absolute minimum level you can get away with. The best results will normally be achieved if you can expose that white card or piece of paper at around 70% to 75% (when looking at an S-Log2 image). Skin tones would be around 55%. If you expose like this you may need to use a different LUT on the recorder to ensure the picture doesn’t look over exposed on the recorders monitor screen. Most of the recorders include LUT’s that have offsets for brighter exposures to allow for this. Then in post production you will also want a LUT with an exposure offset to apply to the S-Log2 recordings. You can use the search function (top right) to find my free LUT sets and download them. Exposing that bit brighter helps get around the shadow data limitations of 12 bit linear raw and pushes the image up into the highlights where there is more data.

SEE ALSO: https://www.sony.co.uk/pro/article/broadcast-products-FS5-raw-shooting-tips

 

PXW-FS5 Native ISO’s

This is as much for my benefit as yours as I can never remember what the native ISO (0dB) is for each of the gamma curves in the FS5.

Standard 1000 ISO
Still 800 ISO
Cinegamma 1  800 ISO
Cinegamma 2  640 ISO
Cinegamma 3  1000 ISO
Cinegamma 4  1000 ISO
ITU709 1000 ISO
ITU709(800) 3200 ISO
S-Log2 3200 ISO
S-Log3 3200 ISO

Using dB and setting it to 0dB really is so much easier with this camera!

Webinar Recordings.

In case you missed the webinars I presented yesterday here are recordings of the 2 afternoon sessions. The first one on HDR, what is it and what does it mean for you. The second is a question and answers session on Sony’s large sensor cameras, from the FS5 to the F55. There were quite a few a6300 and A7s questions thrown in there too!

Hopefully I will be able to find a sponsor that will be able to make these a regular event.

 

More info on CMOS sensor grid artefacts.

Cameras with bayer CMOS sensors can in certain circumstances suffer from an image artefact that appears as a grid pattern across the image. The actual artefact is normally the result of red and blue pixels that are brighter than they should be which gives a magenta type flare effect. However sometimes re-scaling an image containing this artefact can result in what looks like a grid type pattern as some pixels may be dropped or added together during the re scaling and this makes the artefact show up as a grip superimposed over the image.

grid-pattern-1024x576 More info on CMOS sensor grid artefacts.
Grid type artefact.

The cause of this artefact is most likely off-axis light somehow falling on the sensor. This off axis light could come from an internal reflection within the camera or the lens. It’s known that with the F5/F55 and FS7 cameras that a very strong light source that is just out of shot, just above or below the image frame can in some circumstances with some lenses result in this artefact. But this problem can occur with almost any CMOS Bayer camera, it’s not just a Sony problem.

The cure is actually very simple, use a flag or lens hood to prevent off axis light from entering the lens. This is best practice anyway.

So what’s going on, why does it happen?sony-grid-artefact-explained More info on CMOS sensor grid artefacts.

When white light falls on a bayer sensor it passes through color filters before hitting the pixel that measures the light level. The color filters are slightly above the pixels. For white light the amount of light that passes through each color filter is different.  I don’t know the actual ratios of the different colors, it will vary from sensor to sensor, but green is the predominant color with red and blue being considerably lower, I’ve used some made up values to illustrate what is going on, these are not the true values, but should illustrate the point.

In the illustration above when the blue pixel see’s 10%, green see 70% and red 20%, after processing the output would be white. If the light falling on the sensor is on axis, ie coming directly, straight through the lens then everything is fine.

But if somehow the light falls on the sensor off axis at an oblique angle then it is possible that the light that passes through the blue filter may fall on the green pixel, or the light from the green filter may fall on the red pixel etc. So instead of nice white light the sensor pixels would think they are seeing light with an unusually high red and blue component. If you viewed the image pixel for pixel it would have very bright red pixels, bright blue pixels and dark green pixels. When combined together instead of white you would get Pink or Blue. This is the kind of pattern that can result in the grid type artefact seen on many CMOS bayer sensors when there are problems with off axis light.

This is a very rare problem and only occurs in certain circumstances. But when it does occur it can spoil an otherwise good shot. It happens more with full frame lenses than with lenses designed for super 35mm or APSC and wide angles tend to be the biggest offenders as their wide Field of View  (FoV) allows light to enter the optical path at acute angles. It’s a problem with DSLR lenses designed for large 4:3 shaped sensors rather than the various wide screen format that we shoot video in today. All that extra light above and below the desired widescreen frame, if it isn’t prevented from entering the lens has to go somewhere. Unfortunately once it enters the cameras optical path it can be reflected off things like the very edge of the optical low pass filter, the ND filters or the face of the sensor itself.

The cure is very simple and should be standard practice anyway. Use a sun shade, matte box or other flag to prevent light from out of the frame entering the lens. This will prevent this problem from happening and it will also reduce flare and maximise contrast. Those expensive matte boxes that we all like to dress up our cameras with really can help when used and adjusted correctly.

I have found that adding a simple mask in front of the lens or using a matte box such as any of the Vocas matte boxes with eyebrows will eliminate the issue. Many matte boxes will have the ability to be fitted with a 16:9 or 2.40:1 mask ( also know as Mattes hence the name Matte Box) ahead of the filter trays. It’s one of the key reason why Matte Boxes were developed.

IMG_1022 More info on CMOS sensor grid artefacts.
Note the clamp inside the hood for holding a mask in front of the filters on this Vocas MB216 Matte Box. Not also how the Matte Box’s aperture is 16:9 rather than square to help cut out of frame light.
SMB-1_mpa_04-1024x576 More info on CMOS sensor grid artefacts.
Arri Matte Box with Matte selection.

You should also try to make sure the size of the matte box you use is appropriate to the FOV of the lenses that you are using. An excessively large Matte Box isn’t going to cut as much light as a correctly sized one.  I made a number of screw on masks for my lenses by taking a clear glass or UV filter and adding a couple of strips of black electrical tape to the rear of the filter to produce a mask for the top and bottom of the lens. With zoom lenses if you make this mask such that it can’t be seen in the shot at the wide end the mask is effective throughout the entire zoom range.

f5-f55-mask More info on CMOS sensor grid artefacts.

Many cinema lenses include a mask for 17:9 or a similar wide screen aperture inside the lens.