Tag Archives: FS5

Using different gamuts when shooting raw with the PXW-FS5

This topic comes up a lot. Whenever I have been in discussion with those that should know within Sony they have made it clear that the FS-Raw system is designed around S-Log2 for monitoring and post production etc. This stems from the fact that FS-Raw, the 12 bit linear raw from the FS700, FS7 and FS5 was first developed for the FS700 and that camera only had SGamut and S-Log2. S-Log3 didn’t come until a little later.

The idea is that if the camera is set to SGamut + S-Log2 it is optimised for the best possible performance. The raw signal is then passed to the raw recorder where it will be recorded. For a raw recorder that is going to convert the raw to ProRes or DNxHD the recorder converts the raw to S-SGamut + Log2 so that it will match any internal recordings.

Finally in post the grading software would take the FS-Raw and convert it to SGamut + S-Log2 for further grading. By keeping everything as SGamut and S-Log2 throughout the workflow your brightness levels, the look of the image and any LUT’s that you might use will be the same. Internal and external recordings will look the same. And this has been my experience. Use PP7 with SGamut and S-Log2 and the workflow works as expected.

What about the other Gamuts?

However: The FS5 also has SGamut3, SGamut3.cine and S-Log3 available in the picture profiles. When shooting Log many people prefer S-Log3 and SGamut3.cine. Some people find it easier to grade S-Log3 and there are more LUT’s available for S-Log3/SGamut3.cine than for SGamut and S-Log2. So there are many people that like to use PP8 or PP9 for internal S-Log.

However, switching the FS5’s gamma from S-log2 to S-log3 makes no difference to the raw output. And it won’t make your recorder convert the raw to ProRes/DNxHD as S-Log3 if that’s what you are hoping for. But changing the gamut does have an effect on the colors in the image.

But shouldn’t raw be just raw sensor data?

For me this is interesting, because if the camera is recording the raw sensor output, changing the Gamut shouldn’t really change what’s in the raw recording. So the fact that the image changes when you change the Gamut tells me that the camera is doing some form of processing or gain/gamma adjustment to the signal coming from the sensor. So to try and figure out what is happening and whether you should still always stick to SGamut I decided to do a little bit of testing. The testing was only done on an FS5 so the results are only applicable to the FS5. I can’t recall seeing these same changes with the FS7.

DSC Labs Chroma Tru Test Chart.

For the tests I used a DSC Labs Chroma-tru chart as this allows you to see how the colors and contrast in what you record changes both visually and with a vectorscope/waveform. As well as the chart that you shoot, you download a matching reference overlay file that you can superimpose over the clip in post to visually see any differences between the reference overlay and the way the shot has been captured and decoded. It is also possible to place another small reference chart directly in front of the monitor screen if you need to evaluate the monitor or any other aspects of your full end to end production system. It’s a very clever system and I like it because as well as being able to measure differences with scopes you can also see any differences quite clearly without any sophisticated measuring equipment.

Test workflow:

The chart was illuminated with a mix of mostly real daylight and a bit of 5600K daylight balanced light from a Stella LED lamp. I wanted a lot of real daylight to minimise any errors that could creep in from the spectrum of the LED light (The Stellas are very good but you can’t beat real daylight). The camera was set to 2000 ISO. The raw signal was passed from the camera to an Atomos Shogun Inferno where the clips were recorded as both ProRes Raw and also by using the recorders built in conversion to S-Log2 for internal recording as ProRes HQ. I did one pass of correctly exposed clips and a second pass where the clips were under exposed by 1 stop to asses noise levels. The lens was the 18-105mm kit lens, which without the cameras built in lens compensation does show a fair bit of barrel distortion as you will see!

The ProRes clips were evaluated in DaVinci Resolve using the DaVinci Color Managed workflow with the input colorspace set to S-Log2/Sgamut for every clip and output colorspace set to 709. I also had to set the input range of the ProRes clips to Full Range as this is what S-Log2 files always are. If I didn’t change the input range to Full Range the clips exhibited clipped and crushed black after conversion to 709, this confirms that the clips recorded by the Shogun were Full Range – which follows the S-Log specifications.

I did also take a look at the clips in Adobe Premiere and saw very similar results to Resolve.

I will do a separate report on my findings with the ProRes Raw in FCP as soon as I get time to check out the ProRes raw files properly.

So, what did I find?

In the images below the reference file has been overlaid on the very center of the clip. It can be a little hard to see. In a perfect system it would be impossible to see. But you can never capture the full contrast of the chart 1:1 and all cameras exhibit some color response imperfections. But the closer the center overlay is to the captured chart, the more accurate the system is. Note you can click on any of the capture examples to view a larger version.

Digi-ChromaMatch-Lt Using different gamuts when shooting raw with the PXW-FS5
This is the reference file (by the time it gets posted on my website as a jpeg I would no longer guarantee the colors etc. But when you look at the images below you will see this superimposed over the center of the clips.

Below is Picture Profile 6 (PP6) SGamut with S-Log2. It’s pretty good match. The camera didn’t quite capture the full contrast of the chart and that’s to be expected, reflections etc make it very difficult to get perfect blacks and shadow areas. But color wise it looks quite reasonable although the light blue’s are a little weak/pink.

SGamut_1.1.1 Using different gamuts when shooting raw with the PXW-FS5
SGamut and S-Log2

Below is Picture Profile 7 (PP7) SGamut3 with S-Log3. Straight away we can see that even though the camera was set to S-log3, the contrast is the same in the S-Log2 color managed workflow proving that the gamma of the recording is actually ProRes recording from the Shogun is S-log2, confirming what we already know which is that changing the log curve in the camera makes no difference to the raw recording and no difference to the raw to ProRes conversion in the recorder.

Note the extra noise in the greens. The greens appear to have more color, but they also appear a little darker. If you reduce the brightness of a color without altering the saturation the color appears to be deeper and I think that is what is happening here, it is a lightness change rather than just a saturation change. There is also more noise in the darker bars, grey and black really are quite noisy. Light blues have the same weak/pink appearance and there is a distinct green tint to the white, grey and black bars.

SGamut32_1.5.1 Using different gamuts when shooting raw with the PXW-FS5
SGamut3 with S-Log3

Below is when the camera was set to SGamut3.cine with S-Log3. Again we can see that the recording gamma is obviously S-Log2. The greens are still a touch stronger looking but now there is less noise in the greens. Cyan and reds are slightly lighter than SGamut and yellows appear a bit darker. This is also a little more noisy overall than SGamut, but not as bad as SGamut3. When you play the 3 clips, overall SGamut has the least noise, SGamut3.cine is next and then SGamut3 is clearly the noisiest. As with SGamut there is a distinct green tint to the white, grey and black bars.

SGamut3cine2_1.6.1 Using different gamuts when shooting raw with the PXW-FS5
SGamut3.cine with S-Log3

So that’s what the images look like, what do the scopes tell us. Again I will start with SGamut and we can see that the color response is pretty accurate. This suggests that Atomos do a good job of converting the raw to S-Log2/SGamut before it’s recorded and confirms what we already know which is this is that this is clearly how the system is designed to work. Note how the Red strip falls very close to the R box on the 2x vectorscope, yello almost in Y, green very close to G, Blue almost in B. Magenta isn’t so clever and this probably explains why the pinky blues at the top of the chart are not quite right. Do remember that all these test were done with the preset white balance so it’s not surprising to see some small offsets as the white balance won’t have been absolutely perfect. But that imperfection will be the same across all of my test examples.

Screenshot-2019-03-06-at-12.23.31 Using different gamuts when shooting raw with the PXW-FS5
SGamut + S-Log2

Below is SGamut3. The first thing I noticed was all the extra noise on the right side of the waveform where the greens are. The waveform also shows the difference in lightness compared to SGamut with different colors being reproduced at different brightness levels. The greens are being reproduced at a slightly lower luma level and this is probably why the greens appear more saturated. Also notice how much more fuzzy the vectorscope is, this is due to some extra chroma noise. There is a bit more red and magenta is closer to it’s target box, but all the other key colors are further from their boxes. Yellow and Green and Cyan are all a long way from their target boxes. Overall the color is much less accurate than SGamut and there is more chroma noise.

Screenshot-2019-03-06-at-12.23.53 Using different gamuts when shooting raw with the PXW-FS5

And finally below is SGamut3.cine. There is less noise on the green side of the waveform than SGamut and SGamut3 but we still have a slightly lower luma level for green, making green appear more saturated. Again overall color accuracy is not as good as SGamut. But the vector scope is still quite fuzzy due to chroma noise.

Screenshot-2019-03-06-at-12.24.24 Using different gamuts when shooting raw with the PXW-FS5

Under Exposure:

I just want to show you a couple of under exposed examples. These have had the under exposure corrected in post. Below is SGamut and as you can see it is a bit noisy when under exposed. That shouldn’t be a surprise, under expose and you will get noisy pictures.

SGamut_1.1.1-1 Using different gamuts when shooting raw with the PXW-FS5
SGamut with S-Log2 1 stop under (exposure corrected in post)

Below is SGamut3 and you can really see how much noisier this is than SGamut. I recommend clicking on the images to see a full screen version. You will see that as well as the noise in the greens there is more chroma noise in the blacks and greys. There also seems to be a stronger shift towards blue/green in the whites/greys in the under exposed SGamut3.

SGamut3_1.2.1 Using different gamuts when shooting raw with the PXW-FS5
SGamut3 with S-Log3 1 stop under (exposure corrected in post)

Conclusions:

Clearly changing the gamut makes a difference to the raw output signal. In theory this shouldn’t really happen. Raw is supposed to be the unprocessed sensor output. But these test show that there is a fair bit of processing going on in the FS5 before the raw is output. It’s already known that the white balance is baked in. This is quite easy to do as changing the white balance is largely just a matter of changing the gain on the pixels that represent red and blue relative to green. This can be done before the image is converted to a color image.

What I believe I am seeing in this test is something more complex than that. I’m seeing changes in the luminance and gain levels of different colors relative to each other. So what I suspect is happening is that the camera is making some independent adjustments to the gamma of the Red, Blue and Green pixels before the raw signal is output. This is probably a hang over from adjustments that need to be made when recording S-Log2 and S-Log3 internally rather than something being done to deliberately adjust the raw output. But I didn’t design the camera so I can’t be sure that this is really the case. Only Sony would know the truth.

Does it matter?

Yes and no. If you have been using SGamut3.cine and have been getting the results you want, then, no it doesn’t really matter. I would probably avoid SGamut3. It really is very noisy in the greens and shadows compared to the other two. I would be a little concerned by the green tint in the parts of the image that should be colour free in both SGamut3 and SGamut3.cine. That would make grading a little tougher than it should be.

So my advice remains unchanged and continues to match Sony’s recommendation. This is that you should use PP7 with SGamut and S-Log2 when outputting raw. That doesn’t mean you can’t use the other Gamuts and your milage may vary, but these tests do for me at least confirm my reasons for sticking with PP7.

Both Premiere and Resolve show the same behaviour. Next I want to take a look at what happens in FCP with the ProRes Raw clips. This could prove interesting as FCP decodes and converts the FS-Raw to S-Log3 and SGamut3.cine rather than S-Log2/Sgamut by default. Whether this will make any difference I don’t know. What I do know is that having a recorder that’s converting to S-Log2 for display and software that converts to S-Log3 is very confusing as you need different LUT’s for post and the recorder if you want to use LUT’s for your monitoring. But FCP will have to wait for another day. I have paying work to do first.

Advertisements

Recording the slow motion S&Q output of an FS5 to a normal external recorder (not raw).

This has been asked a couple of times. How do I record the slow motion S&Q output of my PXW-FS5 to an external recorder if I don’t have the raw option or don’t want to use raw.

Well it is possible and it’s quite easy to do. You can do it with either an SDI or HDMI recorder, both will work. The example here is for the new Atomos Ninja V recorder, but the basic idea is the same for most recorders.

Just to be absolutely clear this isn’t a magic trick to give you raw with a conventional non raw recorder. But it will allow you to take advantage of the higher quality codec (normally ProRes) in the external recorder.

Oh and by the way – The Ninja V is a great external monitor and recorder if you don’t want raw or you need something smaller than the Inferno.

So here’s how you do it:

In the camera menu and “Rec Set” – set the file format to XAVC HD and the Rec Format to 1080/50p or 1080/60p it MUST be 50p or 60p for this to work correctly.

DSC_0340 Recording the slow motion S&Q output of an FS5 to a normal external recorder (not raw).


In “Video Out” select the HDMI (for the Ninja, if you recorder has SDI then this works with SDI too).

DSC_0339 Recording the slow motion S&Q output of an FS5 to a normal external recorder (not raw).

Set the SDI/HDMI to 1080p/480i or 1080p/560i it MUST be p not i

Set HDMI TC Output to ON

Set SDI/HDMI Rec Control to ON

DSC_0338 Recording the slow motion S&Q output of an FS5 to a normal external recorder (not raw).

Connect the Ninja (or other recorder) via HDMI and on the Ninja under the input settings set the record trigger to HDMI – ON. If you are using a recorder with SDI you should have similar options for the SDI input.

DSC_0342 Recording the slow motion S&Q output of an FS5 to a normal external recorder (not raw).

So now what will happen is when you use the S&Q mode at 100fps or higher the camera will act as normally, you will still need a SD card in the camera. But when the camera copies the slow motion footage from the internal buffer to the SD card the external recorder will automatically go into record at the same time and record the output stream of the buffer. Once the buffer stream stops, the recorder will stop.

The resulting file will be 50p/60p. So if you want to use it in a 24/25/30p project and get the full slow-mo benefit you will need to tell the edit software to treat the file as a 24/25/30p file to match the other clips in your project. Typically this is done by right clicking on the clip and using the “interpret footage” function to set the frame rate to match the frame rate of your project or other footage.

And that’s it. It’s pretty simple to do and you can improve the quality of your files over the internal recordings, although I have to say you’ll be hard pushed to see any difference in most cases as the XAVC is already pretty good.

Why I Choose To Shoot ProRes Raw with the FS5

This is a much discussed topic right now, so as I promised in my last article about this, I have put together a video. Unfortunately YouTube’s compression masks many of the differences between the UHD XAVC and the ProRes Raw, but you can still see them, especially on the waveform scopes.

To really appreciate the difference you should watch the video on a large screen at at high quality, preferably 4K.

PXW-FS5 Screen Protector updated images.

Here are some updated pictures of the screen protector for the FS5 that I sell via Shapeways. It’s not an exciting product, it’s just a clip on plastic cover that protects the LCD panel from damage when you are not using the camera. I travel a lot with my camera and the unprotected LCD screen is very vulnerable and could easily get scratched or worse still smashed. Arriving for a shoot and finding the FS5’s LCD screen smashed would be a disaster!

If you want one for yourself you can order them through my Shapeways store: https://www.shapeways.com/shops/alisterchapman

AJC05188 PXW-FS5 Screen Protector updated images.
PXW-FS5 screen protector front view.

AJC05190 PXW-FS5 Screen Protector updated images.
PXW-FS5 screen protection cover clipped on to the LCD screen.

AJC05192 PXW-FS5 Screen Protector updated images.
PXW-FS5 clip on screen saver attached to the LCD.

What are the benefits of ProRes Raw with the PXW-FS5?

There has been a lot of discussion recently and few videos posted that perhaps give the impression that if you shoot with S-Log2 on an FS5 and compare it to raw shot on the FS5 there is very little difference.

Many of the points raised in the videos are correct. ProRes raw won’t give you any more dynamic range. It won’t improve the cameras low light performance. There are features such as automatic lens aberration correction applied when shooting internally which isn’t applied when shooting raw.  Plus it’s true that shooting ProRes raw requires an external recorder that makes the diminutive little FS5 much more bulky.

So why in that case shoot ProRes Raw?

Frankly, if all you are doing is producing videos that will be compressed to within an inch of their life for YouTube, S-Log2 can do an excellent job when exposed well, it can be graded and can produce a nice image.

But if you are trying to produce the highest quality images possible then well shot ProRes raw will give you more data to work with in post production with fewer compression artefacts than the internal 8 bit UHD XAVC.

I was looking at some shots that I did in preparation for my recent webinar on ProRes raw earlier today and at first glance there isn’t perhaps much difference between the UHD 8 bit XAVC S-Log2 files and the ProRes raw files that were shot within seconds of each other. But look more closely and there are some important differences, especially if skin tones are important too you.

Skin tones sit half way between middle grey and white and typically span around 2 to 3 stops. So with S-Log 2 and an 8 bit recording a face would span around 24 to 34 IRE and have a somewhere between 24 and 35 code values – Yes, that’s right, maybe as few as 24 shades in each of the R, G and B channels. If you apply a basic LUT to this and then view it on a typical 8 bit monitor it will probably look OK.

But compare that to 12 bit linear raw recording and the same face with 2 to 3 stops across it will have anywhere up to 10 to 20 times as many code values ( somewhere around 250 – 500 code values depending on exactly how it’s exposed) . Apply the same LUT as for the S-Log2 and on the surface it looks pretty much the same – or does it?

Look closely and you will see more texture in the 12 bit raw. If you are lucky enough to have a 10 bit monitor the differences are even more apparent. Sure, it isn’t an in-your-face night and day difference but the 12 bit skin tones look less like plastic and much more real, they just look nicer, especially if it’s someone with a good complexion.

In addition looking at my test material I am also seeing some mpeg compression artefacts on the skin tones in the 8 bit XAVC that has a smoothing effect on the skin tones, reducing some of the subtle textures and adding to the slightly un-real, video look.

The other deal with a lack of code values and H624 compression  is banding. Take 8 bit S-Log2 and start boosting the contrast in a sky scene, perhaps to bring out some cloud details and you will start to see banding and stair stepping if you are not very careful. You will also see it across wall and other textureless surfaces. You can even see this on your grading suite waveform scopes in many cases. You won’t get this with well exposed 12 bit linear raw (for any normal grading at least).

None of these are huge deals perhaps. But what is it that makes a great picture? Take Sony’s Venice or the Arri Alexa as examples. We know these to be great cameras that produce excellent images. But what is it that makes the images so good? The short answer is that it is a combination of a wide range of factors, each done as well as is possible. Good DR, good colour, good skin tones etc. So what you want to record is whatever the sensor in your camera can deliver as well as you can. 8 bit UHD compressed to only 100Mb/s is not really that great. 12 bit raw will give you more textures in the mid range and highlights. It does have some limitations in the shadows, but that is easily overcome with a nice bright exposure and printing down in post.

And it’s not just about image quality.

Don’t forget that ProRes Raw makes shooting at 4K DCI possible. If you hope to ever release your work for cinema display, perhaps on the festival circuit, you are going to be much better off shooting in the cinema DCI 4K standard rather than the UHD TV standard. It also allows you to shoot 60fps in 4K (I’m in the middle of a very big 4K 60p project right now). Want to shoot even faster – well with ProRes Raw you can, you can shoot at up to 120fps in 4K. So there are many other benefits to the raw option on the FS5 and recording to ProRes raw on a Shogun Inferno.

There is also the acceptability of 8 bit UHD. No broadcaster that I know of will ever consider 8 bit UHD unless there is absolutely no other way to get the material. You are far more likely to be able to get them to accept 12 bit raw.

Future proofing is another consideration. I am sure that ProRes raw decoders will improve and support in other applications will eventually come. By going back to your raw sensor data with better software you may be able to gain better image quality from your footage in the future. With Log you are already somewhat limited as the bulk of the image processing has already been done and is baked into the footage.

It’s late on Friday afternoon here in the UK and I’ve promised to spend some time with the family this evening. So no videos today. But next week I’ll post some of the examples I’ve been looking at so that you can see where ProRes raw elevates the image quality possible from the FS5.

Using an FS5 to shoot in low light – what can I do?

The PXW-FS5 is a pretty good camera overall. Compared to cameras from 6 or 7 years ago it’s actually pretty sensitive. The exposure rating of 800 ISO for the standard rec-709 picture profile tells us that it is a little more than twice as sensitive as most old school shoulder cams. But it also suggests that it is only around half as sensitive as the king of low light, the Sony A7S. The A7S is so sensitive because it’s sensor is 1.5x bigger than the sensor in the FS5 and as a result the pixels in the A7S are almost twice the size, so are able to capture more light.

So what can you do if shooting in low light? 

The most important thing to do is to make the optical system as efficient as possible. You want to capture as much of the available light as you can and squeeze it down onto the FS5’s sensor. If you take a fast full frame lens and use it in conjunction with a Speed Booster type adapter you will end up with similar performance to using the same lens, without the speed booster on an A7S.

This is because the lens has a fixed light gathering capability. Use it on an A7S and all of the captured light is passed to all of those big pixels on the sensor. The light is split evenly across 4K’s worth of pixels.

Use it on an FS5 with a speedbooster and the same thing happens, all of the light is compressed down, which makes it brighter and all of this now brighter light falls on 4K’s worth of pixels. The smaller pixels are about half as sensitive, but now the light is twice as bright, so the end result is similar.

metabones_mb_spom_m43_bm3_speed_booster_ultra_0_71x_1259766-1024x1024 Using an FS5 to shoot in low light - what can I do?
A speedbooster adapter such as the Metabones makes a huge difference in low light. But you MUST use a full frame lens.

The biggest performance gains are to be had from using a very fast lens and then making sure all the light from the lens is used, none wasted. Anything slower than f2.8 will be a waste. If you are thinking of using the Sony f4 lens for very low light… well frankly you may as well not bother. The lens is THE most important factor in low light. When I go up to Norway to shoot the Aurora I use f1.4 and f1.8 lenses.

What about Picture Profiles?

The standard picture profile isn’t a bad choice for low light but you might want to look at using cinegamma 3. Although with a low light, low contrast scene none of the picture profiles will be significantly different from the others with the exception of PP2, PP7, PP8 or PP9. None of the profiles make the camera more sensitive, the sensitivity is governed by the sensor itself and all the profiles do is alter the way gain is distributed across the image.

PP2 will crush your shadows giving less to work with in post. The log curves in PP7,8,9 will roll off the darkest parts of the image, again giving you less in post. So I would probably avoid these.

For color I suggest using the Pro colour matrix. This works well for most situations and it will help limit the noise levels as it keeps the saturation fairly low keeping the noisy blue channel in check.

Gain or ISO?

I recommend you set the camera to gain rather than ISO as the ISO’s for each each gamma curve are different, so it can be difficult to understand how much gain is being added, especially if you are switching between gamma curves. Use gain and you will have a good idea of the noise levels as every time you add +6dB the image becomes one stop brighter and you double the noise in the image, +12 dB is 2 stops brighter and 4x noisier than 0dB etc. ISO is an exposure rating, it is not a sensitivity measurement. But don’t use too much gain or too high an ISO as this will affect you ability to use some of the very good post production noise reduction tools that are available.

Noise and Noise Reduction.

If shooting in very low light then you are quite probably going to want to use some noise reduction tools in post production. “Neat Video” works very well at cleaning up a noisy image as do the various NR tools in the paid versions of DaVinci Resolve.  These post production  tools work best when the noise is clean. By that I mean well defined. When using any of the 709 or Cinegamma curves a bit of gain can be used, but I wouldn’t go above 12dB as above this the NR starts to introduce a lot of smear and this than makes it hard for any post production NR processes like Neat Video to do a decent job without the image turning into a blurry mess. So don’t go crazy with the gain or use very high ISO’s as the post production NR won’t work as well on footage that already has a lot of in camera NR applied.

And if you can add a little light-

If you are adding any light use a daylight balanced light where you can. Video cameras are least sensitive in the blue channel. If you use a tungsten light which is predominantly warm/red to get a good white balance you have to increase the gain of the cameras least sensitive and as a result most noisy blue channel. This will add more noise than if you use a daylight balance light as for daylight you need less gain in the noisy blue channel.

There is no miracle cure for shooting in very low light levels. But with the right lens and a speedbooster the FS5 can do a very good job. But just in case yo haven’t worked it out already, I’ll say it one more time: The lens is the most important bit! Beyond this your next step would be adding an image intensifier for that green night vision look.

Mac Driver For Sony Alpha and PXW-FS5 firmware updates. USB Firmware driver for High Sierra.

If like me you use a Mac computer and are using the High Sierra OS then if you want to upgrade your camera you will need this supplemental driver from Sony:

https://support.d-imaging.sony.co.jp/mac/driver/1013/en/index.html

This is for any Sony camera that is upgraded via a direct USB connection between the computer and the camera, so that includes cameras like the A7s, A7r, A6300 and the rest of the Sony Alpha series. It is also for many of the PXW video cameras including the PXW-FS5. You don’t need it for cameras like the PMW-F55 or PXW-FS7 where the update is done by placing the upgrade file on an SD card.

Without this driver the upgrade software will install and all appears to be working OK. Except you can’t get a good USB connection between the camera and the mac computer and the upgrade will fail.

Free ProRes Raw and Sony Venice Webinars

I will be doing a couple of free interactive Webinars with Visual Impact in July. The first is on ProRes Raw looking at what it is, the equipment you will need and how to shoot with it.

http://www.visuals.co.uk/events/events.php?event=eid11028-839

The second is about my practical experiences shooting with a Sony Venice using the version 2 firmware.

http://www.visuals.co.uk/events/events.php?event=eid14021-841

Both webinars will feature a Q&A session where you will be able to ask questions online. You will find the full details about both webinars by following the links above, including how to register. The webinars are free but registration is required to obtain the login details for the events.

 

Why is the white balance limited to 3 presets when using S-Log2, S-Log3 or raw?

This seems to be a source of frustration for many people shooting  raw or using S-Log2 or S-Log3 on a Sony camera. When shooting log and raw you should also be using a matching S-Gamut colour gamut if you want to get the best from the camera and this ties you into one of 3 preset white balances.

With a PXW-FS7, PMW-F5 or F55 it is possible to use custom mode to select a different colour space to mix with S-Log2 or S-Log3 and then have a variable white balance. With the Alpha cameras, PXW cameras such as the FS5 you can choose any Gamut you want in the picture profiles, but I don’t recommend this. For a start, if you don’t use one of the S-Gamuts you will be limited to Rec-709 Gamut, so you won’t be recording  the cameras full colour range. Also in custom mode there are some other things like noise reduction that you really don’t want when shooting S-log2/3 (it can cause banding).

So why is the S-Gamut white balance fixed to the 3 presets for daylight, fluorescent and tungsten? The main reason is to ensure you get the cameras full dynamic range in each colour. White balance is a gain function, it adjusts the gain of the red, green and blue channels so that white objects appear white under differing light sources. So if the light source lacks blue light – making the pictures look excessively warm – you add extra gain to the blue channel to compensate.

But the problem with this is that gain affects dynamic range. When shooting log (or raw) the camera needs to operate the sensor at the optimum gain level to squeeze the highest possible dynamic range from the it. Changing the gain in just one colour channel to shift the white balance could result in a reduction of dynamic range in the channel. This could manifest itself as colours in one channel that clip sooner than the others. This can be really hard to deal with in post production and can show up as things like bright clouds with a colour cast that isn’t in the rest of the picture.

Another potential issue is that because of the way silicon sensors work the blue channel is almost always noisier than the red and green. So you want to keep the gain in the blue channel as low as possible to prevent the pictures getting too noisy. This is particularly important when shooting log as you won’t see your end result until after the images have been graded. So manually shifting the gain of the blue channel in camera to correct the white balance could lead to footage that ends up noisier than you would expect.

So – Sony chose to fix the white balance to 3 carefully tuned presets designed to avoid this situation and maximise the dynamic range. After all, when shooting log or raw it is expected that the footage will be graded anyway, so the white balance will normally be adjusted as part of the post production process.

There are some people that advocate adjusting the FS5’s white balance via the picture profile settings, personally I don’t recommend this or feel that it’s necessary. But yes, you can do this, but just keep a very close eye on your highlights and if you can use monitor with RGB parade to make sure you have equal recording levels for your whites without one colour channel clipping ahead of the others. Also apply a LUT in the monitor that is close to your desired output so that you can keep an eye on the noise levels.

In summary – the white balance is preset to ensure you don’t encounter problems later on. You should be able to fully adjust and fine tune your white balance in post production to a far greater degree than is possible in camera anyway, so don’t worry if the WB is a touch off when shooting.

The only exception to this is the new Sony Venice. Venice has enough dynamic range and enough internal processing power to allow you to make a wide range of white balance adjustments in camera. Hopefully we will see some of this flexibility trickle down to the next generations of lower cost Sony digital cinema cameras.

PXW-FS5 II Secret Sauce and Venice Colour Science.

At NAB 2018 a very hot topic is the launch of the FS5 II. The FS5 II is an update on the existing FS5 that includes the FS Raw output option and the HFR option as standard. So out of the box this means that this camera will be a great match to an Atomos Inferno to take advantage of the new Apple ProRes Raw codec.

Just like the FS5 the FS5 II can shoot using a range of different gamma curves including Rec-709, HLG, S-Log2  and S-Log3. So  for those more involved projects where image control is paramount you can shoot in log (or raw)  then take the footage into your favourite grading software and create whatever look you wish. You can tweak and tune your skin tones, play with the highlight roll off and create that Hollywood blockbuster look – with both the FS5 and the FS5 II. There is no change to this other than the addition of FS-Raw as standard on the FS5 II.

The big change, is to the cameras default colour science.

FS5II-1-1024x564 PXW-FS5 II Secret Sauce and Venice Colour Science.
New color science from the Sony PXW-FS5 II

Ever since I started shooting on Sony cameras, which was a very long time ago, they have always looked a certain way. If you point a Sony camera at a Rec-709 test chart you will find that the colours are actually quite accurate, the color patches on the chart lining up with the target boxes on a vector scope. All Sony cameras look this way so that if you use several different cameras on the same project they should at least look very similar, even if one of those cameras is a few years old.  But this look and standard was establish many years ago when camera and TV technology was nowhere near as advanced as it is today.

in addition, sometimes accurate isn’t pretty. Television display technology has come a long way in recent years. Digital broadcasting combined with good quality LCD and OLED displays now mean that we are able to see a wider range of colours and a larger dynamic range. Viewers expectations are changing, we all want prettier images.

When Sony launched the high end Venice digital cinema camera a bold step was taken, which was to break away from the standard Sony look and instead develop a new, modern, “pretty” look. A lot of research was done with both cinematographers and viewers trying to figure out what makes a pretty picture. Over several months I’ve watched Pablo, Sony’s colourist at the Digital Motion Picture Center at Pinewood studios develop new LUT’s with this new look for the Venice camera. It hasn’t been easy, but it looks really nice and is quite a departure from that standard Sony look.

The FS5 II includes many aspects of this new look. It isn’t just a change to the colours it is also a change to the default gamma curve that introduces a silky smooth highlight roll off that extends the dynamic range well beyond that normally possible with a conventional Rec-709 gamma curve. A lot of time was spent looking at how this new gamma behaves when shooting people and faces. In particular those troublesome highlights that you get on a nose or cheek that’s catching the light. You know – those pesky highlights that just don’t normally look nice on a video camera.

So as well as rolling off the brightness of these highlights in a smooth way, the color also subtly washes out to prevent the highlight color bloom that can be a video give away. This isn’t easy to do. Any colorist will tell you that getting bright skin tone highlights to look nice is tough. You bring down the brightness and it looks wrong because you loose too much contrast. De-saturate too much and it looks wrong as it just becomes a white blob. Finding the right balance of extended dynamic range with good contrast, plus a pleasing roll-off without a complete white-out is difficult enough to do in a grading suite where you can tweak and tune the settings for each shot. Coming up with a profile that will work over a vast range of shooting scenarios with no adjustment is even tougher. But it looks to me as though the engineers at Sony have really done a very nice job in the FS5 II.

Going forwards from here I would expect to see, or at least like to see, most of Sony’s future cameras have this new colour science. But this is a big step for Sony to break away from decades of one look and every camera looking more or less the same.  But do remember this change is primarily to the default, “standard” gamma look. It does not effect the FS5 II’s log or raw recordings. There is also going to have to be a set of LUT’s to go with this new color science so that those shooting with with a mix of the baked in look and S-log or raw can make all the footage match. In addition users of other S-Log cameras will want to be able to make their cameras match. I see no reason why this won’t be possible via a LUT or set of LUT’s, within the limitations of each cameras sensor technology.

There has been a lot of people that seem unhappy with the FS5 II. I think many people want a Sony Venice for the price of an FS5. Let’s be realistic, that isn’t going to happen. 10 bit recording in UHD would be nice, but that would need higher bit rates to avoid motion artefacts which would then need faster and more expensive media. If you want higher image quality in UHD or 4K DCI do consider an Atomos recorder and the new ProRes Raw codec. The files are barely any bigger than ProRes HQ, but offer 12 bit quality.

Given that the price of the FS5 II is going to be pretty much the same or maybe even a little lower than the regular FS5 (before you even add any options), I am not sure why so many people are complaining. The FS5-II takes a great little camera, makes it even better and costs even less.