This is something a lot of people have been asking for. An extension or relocation cable that allows you to place devices that will be connected to a camera via the MI Shoe away from the shoe itself.
But in order to get the MI Shoe relocation cable you have to buy the whole XLR-K3M XLR adapter kit, you can’t get the cable on it’s own. This is a shame as I would like to use the cable with my UWP-D series radio mics. I’m not a fan of having the radio mic receiver right on top of the handle as it tends to stick out and get in the way when you put the camera into most camera bags. But, I don’t really need the XLR adapter.
Anyway, here’s a link to the XLR-K3M for those that really need that cable (or the new XLR adapter).
A completely useless bit of trivia for you is that the “E” in E-mount stands for eighteen. 18mm is the E-mount flange back distance. That’s the distance between the sensor and the face of the lens mount. The fact the e-mount is only 18mm while most other DSLR systems have a flange back distance of around 40mm means thare are 20mm or more in hand that can be used for adapters to go between the camera body and 3rd party lenses with different mounts.
Here’s a little table of some common flange back distances:
|Sony FZ (F3/F5/F55)||19mm||1mm|
|Nikon F Mount||46.5mm||28.5mm|
|Sony A, Minolta||44.5mm||26.5mm|
There is a video on YouTube right now where the author claims that the Sony Alpha cameras don’t record correctly internally when shooting S-Log2 or S-Log3. The information contained in this video is highly miss-leading and the conclusion that the problem is with the way Sony record internally is incorrect. There really isn’t anything wrong with the way Sony do their recordings. Neither is there anything wrong with the HDMI output. While centered around the Alpha cameras the information below is also important for anyone that records S-Log2 or S-log3 externally with any other camera.
Some background: Within the video world there are 2 primary ranges that can be used to record a video signal.
Legal Range uses code value 16 for black and code value 235 for white (anything above CV235 is classed as a super-white and these can still be recorded but considered to be beyond 100%).
Full or Data Range uses code value 0 for black and code value 255 for white or 100%.
Most cameras and most video systems are based on legal range. ProRes recordings are almost always legal range. Most Sony cameras use legal range and do include super-whites for some of the curves such as Cinegammas or Hypergammas to gain a bit more dynamic range. The vast majority of video recordings use legal range. So most software defaults to legal range.
But very, very importantly – S-log2 and S-log is always full/data range.
Most of the time this doesn’t cause any issues. When you record internally in the camera the internal recordings have metadata that tells the playback, editing or grading software that the S-Log files have been recorded using full range. Because of this metadata the software will play the files back and process them at the correct levels. However if you record the S-Log with an external recorder the recorder doesn’t always know that what it is getting is full range and not legal range, it just records it, as it is, exactly as it comes out of the camera. That then causes a problem later on because the externally recorded file doesn’t have the right metadata to ensure that the full range S-Log material is handled correctly and most software will default to legal range if it knows no different.
Lets have a look at what happens when you import an internally recorded S-Log2 .mp4 file from a Sony A7S into Adobe Premiere:
A few things to note here. One is Adobe’s somewhat funky scopes where the 8 bit code values don’t line up with the normally used IRE values used for video productions. Normally 8 bit code value 235 would be 100IRE or 100%, but for some reason Adobe have code value 255 lined up with 100%. My suspicion is that the scope % scale is not video % or IRE but instead RGB%. This is really confusing. A further complication is that Adobe have code value 0 as black, again, I think, but am not sure that this is RGB code value 0. In the world of video Black should be code value 16. But the scopes appear to work such that 0 is black and that 100 is full scale video out. Anything above 100 and below 0 will be clipped in any file you render out.
Looking at the scopes in the screen grab above, the top step on the grey scale chart is around code value 252. That is the code value you would expect it to be, that lines up just nicely with where the peak of an S-Log2 recording should be. This all looks correct, nothing goes above 100 or below 0 so nothing will be clipped.
So now lets look at an external ProRes recording, recorded at exactly the same time as the internal recording and see what Premier does with that:
OK, so we can see straight away something isn’t quite right here. In an 8 bit recording it should be impossible to have a code value higher that 255, but the scopes are suggesting that the recording has a peak code value of something around CV275. That is impossible, so alarm bells should be ringing. Something is not quite right here. In addition the S-Log2 appears to be going above 100, so that means if I were to simply export this as a new file, the top of the recording will be clipped and it won’t match the original. This is very clearly not right.
Now lets take a look at what happens in Adobe Premiere when you apply Sony’s standard S-Log2 to Rec-709 LUT to a correctly exposed internal recording:
This all looks good and as expected. Blacks are sitting down just above the 0 line (which I think we can safely assume is black) and the whites of the picture are around code value 230 or 90, whatever that means. But they are certainly nice and bright and are not in the range that will be clipped. So I can believe this as being more or less correct and as expected.
So next I’m going to add the same standard LUT to the external recording to see what happens.
OK, this is clearly not right. Our blacks now go below the 0 line and they look clipped. The highlights don’t look totally out of place, but clearly there is something going very, very wrong when we this normal LUT to this correctly exposed external recording. There is no way our blacks should be going below zero and they look crushed/clipped. The internal recording didn’t behave like this. So what is going on with the external recording?
To try and figure this out lets take a look at the same files in DaVinci Resolve. For a start I trust the scopes in Resolve much more and it is a far better programme for managing different types of files. First we will look at the internal S-Log2 recording:
Once again the levels of the internal S-Log2 recordings look absolutely fine. Our peak is around code value 1010 which would be 252 in 8 bit. Right where the brightest bits of an S-log2 file should be. Now lets take a look at the external recording.
If you compare the two screen grabs above you can see that the levels are exactly the same. Our peak level is around CV1010/CV252, just where it should be and the blacks look the same also. The internal and external recordings have the same levels and look the same. There is no difference (other then perhaps less compression and fewer artefacts in the ProRes file). There is nothing wrong with either of these recordings and certainly nothing wrong with the way Sony record S-Log2 internally. This is absolutely what I expect to see.
BUT – I’ve been a little bit sneaky here. As I knew that the external recording was a full range recording I told DaVinci Resolve to treat it as a full range recording. In the media bin I right clicked on the clip and under “clip attributes” I changed the input range from “auto” to “full”. If you don’t do this DaVinci Resolve will assume the ProRes file to be legal range and it will scale the clip incorrectly in the same way as Premiere does. But if you tell Resolve the clip is full range then it is handled correctly.
This is what it looks like if you allow Resolve to guess at what range the S-Log2 full range clip is by leaving the input range setting to “auto”:
In the above image we can see how in Resolve the clip becomes clipped because in a legal range recording anything over CV235/CV940 would be an illegal super white. Resolve is scaling the clip and pushing anything in the original file that was above CV235/CV940 off the top of the scale. The scaling is incorrect because Resolve doesn’t know the clip is supposed to be full range and therefore not scaled. If we compare this to what Premiere did with the external recording it’s actually very similar. Premiere also scaled the clip, only Premiere will show all those “illegal” levels above it’s 100 line instead of clipping then as Resolve does. That’s why Premiere can have those “impossible” 8 bit code values going up to CV275.
Just to be complete here, I did also test the internal .mp4 recordings in Resolve switching between “auto” and “full” range and in both cases the levels stayed exactly the same. This shows that Resolve is correctly handling the internally record full range S-Log as full range.
What about if you add a LUT? Well you MUST tell Resolve to treat the S-Log2 ProRes clip as a full range clip otherwise the LUT will not be right, if your footage is S-Log3 you also have to tell Resolve that it is full range:
Both the internal and external recordings are actually exactly the same. Both have the same levels, both use FULL range. There is absolutely nothing wrong with Sony’s internal recordings. The problem stems from the way most software will assume that the ProRes files are legal range. But if it’s an S-Log2 or S-Log3 recording it will in fact be full (data) range. Handling a full range clip as legal range means that highlights will be too high/bright or clipped and blacks will be crushed. So it’s really important that your software handles the footage correctly. If you are shooting using S-Log3 this problem is harder to spot as S-Log3 has a peak recording level that is well with the legal range, so you often won’t realise it’s being scaled incorrectly as it won’t necessarily look clip. If you use LUT’s and your ProRes clips look crushed or highlights look clipped you need to check that the input scaling is correct. It’s really important to get this right.
Why is there no difference between the levels when you shoot with a Cinegamma? Well when you shoot with a cinegamma the internal recordings are legal range so the internal recordings get treated as legal range and so do the external recordings, so they don’t appear to be different (In the YouTube video that led to this post the author discovers that if you record with a normal profile first and then switch to a log profile while recording the internal and external files will match. But this is because now the internal recording has the incorrect metadata, so it too gets scaled incorrectly, so both the internal and external files are now wrong – but the the same).
Once again: There is nothing wrong with the internal recordings. The problem is with the way the external recordings are being handled. The external recordings haven’t been recorded incorrectly, they have been recorded as they should be. The problem is the edit software is incorrectly interpreting the external recordings. The external recordings don’t have the necessary metadata to mark the files as full range because the recorder is external to the camera and doesn’t know what it’s being sent by the camera. This is a common problem when using external recorders.
What can we do in Premiere to make Premiere work right with these files?
You don’t need to do anything in Premiere for the internal .mp4 recordings. They are handled correctly but Premiere isn’t handling the full/data range ProRes files correctly.
My approach for this has always been to use the legacy fast color corrector filter to transform the input range to the required output range. If you apply the fast color corrector filter to a clip you can use the input and output level sliders to set the input and output range. In this case we need to set the output black level to CV16 (as that is legal range black) and we need to set output white to CV235 to match legal range white. If you do this you will then see that the external recording appears to have almost exactly the same values as the internal recording. However there is some non-linearity in the transform, it’s not quite perfect. So if anyone knows of a better way to do this do please let me know.
Now when you apply a LUT the picture and the levels are more or less what you would expect and almost identical to the internal recordings. I say almost because there is a slight hue shift. I don’t know where the hue shift comes from. In Resolve the internal and external recordings look pretty much identical and there is no hue shift. In Premiere they are not quite the same. The hue is slightly different and I don’t know why. My recommendation – use Resolve, it’s so much better for anything that needs any form of grading or color correction.
I’m sitting here in the UK, Its February and it almost 20c (68f). Very nice indeed for the UK this time of year. Just a couple of weeks ago I was in Northern Norway, up above the arctic circle running one of my annual Northern Lights adventure tours. The weather there was very different. At no time did the temperature get above -15c(5f) and for most of the trip it was around -24c(-11f) both during the day and during the night.
Now, you might consider me a sadist when I say this, but for my Northern Lights trips I normally want it to be -20c or colder. The reason being that when it’s very cold like this we normally get beautifully clear skies. And we need clear skies to see the Aurora.
After many years of taking a full size video camera up to Norway I decided to go light this year and just take my trusty A7S and A6300 cameras. We get around on snow scooters and on sledges towed behind the snow scooters. This can make lugging around a larger camera tricky and there are times when you just can’t take a big camera. But in order to get the very best from these cameras I also decided to take an Atomos Ninja V.
The Ninja V is the first of a new generation of recorders and monitors from Atomos. It’s much smaller than the Shogun range of recorders making it a better size and weight match for smaller cameras and DSLR’s. It has a very, very nice 5″ screen with a maximum brightness of 1000 Nits. The 1000 Nit output and Atomos’s clever way of driving it means it can display both SDR and HDR images depending on how it is set up. A key difference between the Shogun and the Ninja devices is that the Shoguns have both SDI inputs and HDMI inputs while the Ninja only has an HDMI input. But if your using this with a DSLR than only has an HDMI output, as I was, the lack of SDI connectors is not a problem.
The build quality of the Ninja V is really good. Most of the body is made of aluminium. The rear part where the slots for the SSD and battery are is made from plastic, but it appears to be a good high quality and tough plastic. A new feature is an “AtomX” expansion port tucked inside the battery compartment. The expansion port allow different modules to be attached to the Ninja V to add functionality such a video over IP (ethernet) using the Newtek NDI protocol for live streaming or to turn the Ninja V into an IP connected monitor. There is also an AtomX sync module that allows you to wirelessly synchronise timecode and control multiple Ninja V”s on a single network and to use Bluetooth remote control. You can find out more about the AtomX modules here https://www.atomos.com/AtomX
Anyway – back to Norway. We were very lucky with the weather, and with the Northern Lights. On the first night at the cabins we stay at the Aurora put on a pretty good display. I was shooting with my Sony A7S with a Sigma Art 20mm f1.4 lens. I was shooting a mix of time-lapse, in which case I simply record the raw frames in the camera on it’s internal SD cards as well as real time video.
The Northern Lights are only rarely very bright. Most of the time they are fairly dim. So I was using the Sigma lens wide open, shooting at 24fps and with the shutter at 1/24th. The adjusting the cameras ISO to get a nice bright image. At times this did mean I was using some very high ISO’s with a lot of gain. Shooting like this is going to put a lot of strain on any codec. But the Long GOP XAVC-S codec used in the A7S is going to be very hard pushed to not introduce a lot of additional artefacts. In addition my older original A7S can only record HD internally.
By using the Ninja V I was able to record video of the Northern Lights in 4K using the ProRes codec. I used ProRes HQ and ProResHQ uses much less compression than XAVC-S. So even though both the internal recordings and the external recordings are limited to 8 bit (due to the cameras HDMI output limitations rather than any limitation of the Ninja) the ProRes recordings are far more robust and will noise reduce in post much better than the XAVC-S.
When you’re working outside for extended periods and it’s -27c(-17f) it’s tough on the gear and tough on you. When shooting the Aurora my camera are outside all night, exposed to the cold. Typical problems include frost and ice on the front element of the lens. The moisture from your own body can easily freeze onto the lens if you stand close to the camera. If you look at the lens to check it for frost and breath out you will leave it coated in ice.
Wires and cables that are soft and flexible in normal temperatures become as stiff as steel rods and can crack and fracture if you try to bend them. All batteries will loose some of their capacity. Very small batteries are worst affected. Larger batteries tend to fair a bit better, but there is a tremendous difference between the way most cheap budget batteries behave in the cold to good quality brand name batteries. For this reason I power my complete setup from a single PAG PAGLink V-Mount battery. The PAGlink batteries are great for all sorts of different applications, but for these trips a big benefit is that a small plug type charger can be used to charge many PAGlink batteries by stacking the batteries together. Then to power multiple devices I use the clip-on PAG Power hub plate to provide 5V for the camera battery adapters that I use, 12V for the lens heaters I use and another 12V feed for the Ninja V.
After more than a few minutes outside the camera kit itself will have become extremely cold. If you then take that kit inside into a nice warm cabin the warm moist air in the cabin will condense onto the cold camera body. Because the camera body will be extremely cold this will then freeze. Before you know it the camera kit is covered in ice. What you can’t see is that it’s likely that there will also be some ice and moisture inside the camera. It can take hours to warm the camera back up again and get it dried out properly. Bagging the camera before you take it indoors can help, but taking the camera in and out many times over the coarse of a shoot like this can cause a lot of damage. So I prefer to leave all the camera kit outside for the duration of the trip.
This means that when you come to fire it up you are often trying to switch on an absolutely frozen camera. In the past I have had problems with cold recorders that wouldn’t start up. But I’m pleased to report that the Ninja V always came to life no matter how cold it was. Whenever I pressed the record button it went into record. Operating the touch screen in the cold was not an issue. In fact using touch screen gloves, the Ninja was really easy to use. Pressing small fiddly buttons isn’t easy, even with thin gloves, but the touch screen turned out really easy to work with.
A big change on the Ninja V over previous models is the operating system. The new operating system looks really good and is quite logically laid out. Gone is the old AtomHDR slider that changes the brightness of the screen when in HDR. This is replaced with dedicated viewing modes for Native, 709, PQ HDR and HLG HDR and viewing via a LUT. I prefer the new fixed HDR modes over the Atom HDR slider modes as it eliminates the uncertainty that can sometimes creep in when you use a slider to change the brightness of the display. In my case, when shooting during the day using S-Log2 I would simply select S-Log2 as the source and then use PQ to display an HDR image on the screen. At night when shooting the Aurora I used Rec-709.
The Ninja V can take the same size 2.5″ SSD caddies as the current Shogun recorders. So I was able to use the SSD’s that I already own. However to keep the size of the recorder down it has been designed around a new slightly shorty SSD form factor called SSDMini. When you use a standard size 2.5″ SSD it does stick out from the side of the recorder by about 25mm. If you use an SSDMini it doesn’t stick out at all. SSDMini’s are currently being manufactured by Angelbird and Sony. They have the same sata connector as regular 2.5″ SSD’s and the SSDMini’s can also be used on the larger Atomos Shoguns.
By the time we were ready to leave Norway we had seen the Northern Lights on 3 different nights. By day we had seen some beautiful sunrises as well as other optical effects like sun dogs caused by the light from the sun being refracted by ice crystals in the air. The Atomos Ninja V had impressed me hugely. It just worked perfectly despite the extreme cold. It allowed me to record at higher quality than would have been possible without it and turned out to be easy to operate. What more can you want really?
Fancy joining me on one of these trips? Follow the link to find out more: http://www.xdcam-user.com/northern-lights-expeditions-to-norway/
— And why do Sony cameras look the way they do?
It all about the color science.
“Color Science” is one of those currently in fashion phrases that gets thrown around all over the place today. First of all – what the heck is color science anyway? Simply put it’s how the camera sees the colors in a scene, mixes them together, records them – and then how your editing or grading software interprets what is in the recording and finally how the TV or other display device turns the digital values it receives back into a color image. It’s a combination of optical filters such as the low pass filter, color filters, sensor properties, how the sensor is read out and how the signals are electronically processed both in the camera, by your edit/grading system and by the display device. It is no one single thing, and it’s important to understand that your edit process also contributes to the overall color science.
Color Science is something we have been doing since the very first color cameras, it’s not anything new. However us end users now have a much greater ability to modify that color science thanks to better post production tools and in camera adjustments such as picture profiles or scene files.
Recently, Sony cameras have sometimes been seen by some as having less advanced or poor color science compared to cameras from some other manufacturers. Is this really the case? For Sony part of the color science issue is that historically Sony have deliberately designed their newest cameras to match previous generations of cameras so that a large organisation with multiple cameras can use new cameras without having them look radically different to their old ones. It has always been like this and all the manufacturers do this, Panasonic cameras have a certain look as do Canon etc. New and old Panasonics tend to look the same as do old and new Canon’s, but the Canon’s look different to the Panasonics which look different to the Sony’s.
Sony have a very long heritage in broadcast TV and that’s how their cameras look out of the box, like Rec-709 TV cameras with colors that are similar to the tube cameras they were producing 20 years ago. Sony’s broadcast color science is really very accurate – point one at a test chart such as a Chroma DuMonde and you’ll see highly repeatable, consistent and accurate color reproduction with all the vectors on a vector scope falling exactly where they should, including the skin tone line.
On the one hand this is great if you are that big multi-camera business wanting to add new cameras to old ones without problems, where you want your latest ENG or self-shooters cameras to have the same colors as your perhaps older studio cameras so that any video inserts into a studio show cut in and out smoothly with a consistent look.
But on the other hand it’s not so good if you are a one man band shooter that wants something that looks different. Plus accurate is not always “pretty” and you can’t get away from the fact that the pictures look like Rec-709 television pictures in a new world of digital cinematography where TV is perhaps seen as bad and the holy grail is now a very different kind of look that is more stylised and much less true to life.
So Sony have been a bit stuck. The standard look you get when you apply any of the standard off-the shelf S-Log3 or S-Log2 LUT’s will by design be based on the Sony color science of old, so you get the Sony look. Most edit and grading applications are using transforms for S-Log2/3 based on Sony’s old standard Rec-709 look to maintain this consistency of look. This isn’t a mistake. It’s by design, it’s a Sony camera so it’s supposed to look like other Sony cameras, not different.
But for many this isn’t what they want. They want a camera that looks different, perhaps the “film look” – whatever that is?
Recently we have seen two new cameras from Sony that out of the box look very different from all the others. Sony’s high end Venice camera and the lower cost FS5 MKII. The FS5 MKII in particular proves that it’s possible to have a very different look with Sony’s existing colour filters and sensors. The FS5 MK II has exactly the same sensor with exactly the same electronics as the MK I. The only difference is in the way the RGB data from the sensor is being processed and mixed together (determined by the different firmware in the Mk1 and mk2) to create the final output.
The sensors Sony manufacture and use are very good at capturing color. Sony sensors are found in cameras from many different manufacturers. The recording systems in the Sony cameras do a fine job of recording those colors as data within the files the camera records as data with different code values representing what the sensor saw. Take that data into almost any half decent grading software and you can change the way it looks by modifying the data values. In post production I can turn almost any color I want into any other color. It’s really up to us as to how we translate the code values in the files into the colors we see on the screen, especially when recording using Log or raw. A 3D LUT can change tones and hues very easily by shifting and modifying the code values. So really there is no reason why you have to have the Sony 709 look.
My Venice emulation LUT’s will make S-Log3 from an FS5 or FS7 look quite different to the old Sony Broadcast look. I also have LUT’s for Sony cameras that emulate different Fuji and Kodak film stocks, apply one of these and it really looks nothing like a Sony broadcast camera. Another alternative is to use a color managed workflow such as ACES which will attempt to make just about every camera on the market look the same applying the ACES film style look and highlight roll-off.
We have seen it time and time again where Sony footage has been graded well and it then becomes all but impossible to identify what camera shot it. If you have Netflix take a look at “The Crown” shot on Sony’s F55 (which has the same default Sony look as the FS5 MK1, FS7 etc). Most people find it hard to believe the Crown was shot with a Sony because it has not even the slightest hint of the old Sony broadcast look.
If you use default settings, standard LUT’s etc it will look like a Sony, it’s supposed to! But you have the freedom to choose from a vast range of alternative looks or better still create your own looks and styles with your own grading choices.
But for many this can prove tricky as often they will start with a standard Sony LUT or standard Sony transform. So the image they start with has the old Sony look. When you start to grade or adjust this it can sometimes look wrong because you have perhaps become used to the original Sony image and then anything else just doesn’t seem right, because it’s not what you are used to. In addition if you add a LUT and then grade, elements of the LUT’s look may be hard to remove, things like the highlight roll off will be hard baked into the material, so you need to do need to think carefully about how you use LUT’s. So try to break away from standard LUT’s. Try ACES or try some other starting point for your grade.
Going forward I think it is likely that we will see the new Venice look become standard across all of the Cinema style cameras from Sony, but it will take time for this to trickle down into all the grading and editing software that currently uses transforms for s-Log2/3 that are based on the old Sony Rec-709 broadcast look. But if you grade your footage for yourself you can create just about any look you want.
I released my first version of the Venice Look LUT’s a few weeks ago and they have been a big hit. Overall most people seem to like them and get some great results. I’ve seen quite a few good looking videos produced using them.
I have received some feedback though that some people feel that the LUT’s may be crushing the blacks a bit too much for them, personally I think the deep shadows gives quite a film like look. However in response to that feedback I created an additional LUT set that keeps the blacks slightly higher. This can make grading a little easier, especially in FCP-X. You will find these new version 3 LUT’s here in the packages below – but please read on…..
While I was at it I also created another set of LUTs with a minus green offset. The idea behind these was that they can be used for material shot under lights with a green tint such as many LED or fluorescent light fixtures. Playing with these “-G1” LUT’s I have decided that I really like the slightly warmer and even less “Sony” look that these versions of the LUT’s give when shooting under “normal” lighting. So do please give them a try for a warmer look for skin tones both with LED/Fluorescent lighting and also with full spectrum lighting such as tungsten and sunlight.
Taking that a step further I have also included an even stronger minus green offset in a further -G2 set of LUT’s. So between the 3 sets of LUT’s offered in this download you should be able to find a set for most types of lighting with a variety of skin tone renditions.
Included in the LUT sets are LUTs for grading (with exposure offsets), LUT’s for Small HD monitors and the Zacuto Gratical. The grading LUT’s can also be used in other monitors and devices such as the Atomos recorder/monitors.
As always (to date at least) I offer these as a free download available by clicking on the links below. However a lot of work goes into creating and hosting these. I feel that this LUT set is worth $25.00 and would really appreciate that being paid if you find the LUT’s useful. But I will let you pay what you feel is fair, all contributions are greatly appreciated and it really does help keep this website up and running. If you can’t afford to pay, then just download the LUT’s and enjoy using them. If in the future you should choose to use them on a paying project, please remember where you got them and come back and make a contribution. More contributions means more LUT offerings in the future. I’m currently working on a couple of different film stock emulations based combined with the Venice look highlight rendition.
Please feel free to share a link to this page if you wish to share these LUT’s with anyone else or anywhere else.
To make a contribution please use the drop down menu here, there are several contribution levels to choose from.
There are two different LUT sets. One set is for S-Log3 and S-Gamut3.cine. The other set is for S-Log2 and SGamut. Please only download what you need to save my bandwidth!
Typically if you are shooting with 8 bit, for example with an FS5 in UHD or an A7S, A7R etc, then I recommend you use S-Log2 with SGamut. For most other cameras that have 10 bit recording then I recommend S-Log3 and SGamut3.cine.
Here are the links to my Venice Look Version 3 LUT’s. Including the minus green offset LUTs. Make sure you choose the right version and once you have downloaded them please read the README file included within the package.
I got a request for a set of Rec-709 Venice Look LUT’s – So here they are. I’m not expecting miracles from these, you will be starting with a much reduced dynamic range by shooting with Rec-709, but try them if you wish. I make no promises as to how well they will or will not work!
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:
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.
Hello all. So after numerous problems for some people trying to download the official Sony s709 LUT for Venice, I decided to create my own Venice Look LUT’s. These LUT’s have been created using image matching techniques plus some small tweaks and adjustments to make the LUT’s work well with the 14 stop cameras.
Venice is a 15 stop camera with a new sensor and as a result the official s709 LUT’s are not quite right for the current 14 stop cameras like the FS5, PMW-F55, FS7 and even the A7 series. So the LUT that I have created is slightly different to allow for this.
The end result is a LUT that gets you really close to the way Venice looks. It won’t magically turn your FS5 into a Venice, there is something very, very nice about the way Venice handles the extremes of it’s dynamic range, plus Venice has Sony’s best colour filters (similar to the F55 and F65). So Venice will always be that one very nice step up. But these LUT’s should get you close to the default Venice 709 look. This LUT should NOT be used with Venice as it this LUT is restricted to 14 stops.
Of course do remember that the default look and indeed the official s709 LUT was designed as a first pass look. An instant viewing output for a DIT or for on set viewing. It is not really meant to be the final finished look. It would be normal to grade the Venice material, perhaps from scratch rather than using the s709 LUT for the final output. But, s709 is what comes out of the cameras SDI connectors if you use the default LUT/Look. This is what this LUT set mimics, with some tweaks for the lower cost cameras.
This is one of the largest and most comprehensive LUT sets I have ever created. There are versions designed specifically for grading in Resolve or other grading suites. The bulk of the LUT’s are designed to be used with S-Log3 and SGamut3.cine. There are monitoring versions with offsets for use in monitors such as the Atomos range. I have created a set with offsets for both the Zacuto and Small HD viewfinders and monitors and finally I have also created sets of LUT’s for use with S-Log2 so users of the original A7s or those that wish to shoot with S-Log2 on an 8 bit camera are not left out.
The LUT’s work best with the PMW-F55 as this has the closest native color to the Venice camera, but I think they work really well on the rest of the Sony range.
If you find the LUT’S useful, please consider buying me a beer or a coffee using the “Buy Now” button below. There are different drink options depending on what you feel is fair, it takes time to prepare these and there are costs associated with hosting the files. I’m not paid to run this website and every little bit helps and is greatly appreciated.
If you don’t wish to buy me a coffee, that’s cool. But please don’t host the files elsewhere. Feel free to link back here and share the link, but please don’t distribute these anywhere else.
Here’s the link to the zip file containing the my Venice Look LUT set:
If you are new to XDCAM-USER.COM please take a look around at the various tutorials, guides, tips and tricks that are hosted here. Click on the green search button at the top right to open a search window or follow the links in the drop down menus at the top of the page. Thanks for visiting!
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.