Arri have a little trick in their cameras when shooting log to ProRes that the Sony Log cameras don’t have. When you change the Exposure Index in an Arri camera they modify the position of the exposure mid point and the shape of the Log-C gamma curve. There is actually a different Log-C curve for each EI. When you take this into post it has the benefit that the brightness at each EI will appear similar. But as the curve changes for each EI a different LUT is needed for each exposure if you want something shot at say 800EI to look the same as something shot at 200EI.
With a Sony camera the same S-Log curve is used for each Exposure Index and the LUT brightness is changed so that you end up altering the mid point of the recording as well as the highlight and shadow range. In post each EI will appear to be a different brightness. You can use the same LUT for each EI provided you do an exposure correction prior to adding the LUT or you can use dedicated offset LUT’s for each exposure.
But what you need to remember is that you are always working within a restricted recording range with either system. You can’t go darker than the black recording level or brighter than the highest value the codec can record.
If you do it in camera, as Arri do and change the log curve, at a low EI you seriously constrict the recording range (at 200 EI peak only reaches around 78IRE). This happens because at a low EI you put more light on to the sensor. So to keep the mid range looking a normal brightness in post it must be recorded at at a level that is offset downwards compared to normal. So with all the levels now offset downwards to compensate for the brighter exposure you end up recording your entire capture range with a reduced or compressed recording range. In addition to avoid clipping the blacks at a low EI the shadows are rolled off so you lose some detail and textures in the shadows. You can see the different Log-C curves in this Arri White paper.
Most people choose a low EI for 2 reasons, better signal to noise ratio and improved shadow range. The Arri method gives you the better SNR but while the dynamic range is preserved it’s recorded using less data and in particular the shadow data decreases compared to shooting at the base ISO.
Shoot at a high EI, you put less light on to the sensor. So to maintain similar looking mids in post everything has to be recorded at a higher level. Now you have a problem because the highlights will extend beyond the upper limits of the recording range so Arri have to add a highlight roll off at the top of the Log-C curve. This can present some grading challenges as the curve is now very different to regular Log-C. In addition the highlights are compressed.
Most people choose to shoot at a high EI to extend the highlight range or to work in lower light levels.
The latter is a bit of a pointless exercise with any log camera as the camera sensitivity isn’t actually any different, you are only fooling yourself into thinking it’s is more sensitive and this can result in noisy footage. If you using a high EI to extend the highlight range then really the last thing you want is the extra highlight roll off that Arri have to add at 3200 EI to fit everything in.
One thing here in Arri’s favour is that they can record 12 bit ProRes 444. 12 bits helps mitigate the compressed recording range of low EI’s provided the post workflow is managed correctly.
The beauty of the Sony method is the recording range never changes, so low EI’s and brighter recordings deliver better shadow ranges with more data in the shadows and mids and high EI’s with darker recordings deliver better highlight ranges with no additional data restrictions or additional roll-offs giving the cinematographer more control to choose the exposure mid point without compromise to the data at either end.
But it does mean that post need to be awake and that the shooter needs to communicate with post regarding the brighter/darker looking images. But to be honest if post don’t understand this and recognise what you have done either buy just looking at the footage or checking the metadata what chance is there of post actually doing a decent job of grading your content? This should be fundamental and basic stuff for a colourist/grader. For a colourist/grader to not understand this and how to work with this is like hiring a camera operator that doesn’t know what an ND filter is.
The Sony FS7/FX9/F5/F55/Venice cameras can do something similar to an Arri camera by baking in the S-Log3 LUT. Then in post the exposure will look the same at every EI. BUT you will lose some highlight range at a low EI’s and some shadow range at a high EI’s without gaining any extra range at the opposite end. As a result the total dynamic range does reduce as you move away from the base ISO.
In addition on the Venice, FS7/F5/F55 (and I suspect in a future update the FX9) you can bake in a user LUT to the SxS recordings. If you create a set of S-Log3 to S-Log3 LUT’s with EI offsets included in the LUT you could replicate what Arri do by having an offset and tweaked S-Log3 User LUT for each EI that you want to shoot at. You would not use the cameras EI control you would leave the camera st the base ISO. The LUT’s themselves will include the exposure offset. These will maintain the full dynamic range but just like Arri they will need to roll off the shadows or highlights within the LUT.
But monitoring will be tricky as you won’t have the benefit of a 709 type LUT for monitoring so you you may need to use an external monitor or viewfinder that can apply a LUT to it’s image. The good news is the same LUT would be used in the monitor for every version on the offset S-Log3 LUT that you are baking in as the exposure brightness levels will be the same for each offset.
So here you are a set of 4 S-Log3/S-Gamut3.cine offset LUT’s for those Sony cameras that will take a user LUT. I have named the LUT’s – 2S Down SL3C, 1S Down SL3C, 1S UP SL3C, 2S UP SL3C.
The name means (Number of Stops) (Down or Up) (Slog3.Cine).
So if the cameras base ISO is 2000 (F5/FS7 etc) and you want to shoot at the equivalent of 1000EI, which is 1 stop down from base you would use “1S Down SL3C”.
As always (to date at least) I offer these as a free download available by clicking on the links below. But I always appreciate a contribution if you find them useful and make use of them. 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.
Please feel free to share a link to this page if you wish to share these LUT’s with anyone else or anywhere else. But it’s not OK to to share or host these on other web sites etc.
As noted in my previous post there can be some issues with the way ProRes is recorded on many external monitors as a legal range files rather than Data Range.
Another side effect of this is that LUT’s designed for post production as well as most camera LUT’s don’t work correctly in the monitor. So even when you apply the same LUT in the camera as in the monitor the images look different.
To address this I am providing here 2 sets of LUTs for S-Log3 and SGamut3.cine designed to match the built in s709 and 709(800) Luts included in many Sony cameras. These LUTs are specifically for external recorders and should not be used in camera. When you use these LUT’s the pictures on the monitor should now match the the images in the cameras viewfinder when the built in LUT has been applied.
You will find 3 LUTs of each type. One for the base exposure, one for footage exposed 1 stop brighter (minus1) and one for footage exposed 2 stops brighter than base (minus2).
As always (to date at least) I offer these as a free download available by clicking on the links below. Try them before you decide then 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, tell your friends and send them here. 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.
This comes up again and again, hence why I am writing about it once again.
Raw should never be converted to log before recording if you want any benefit from the raw. You may as well just record the 10 bit log that most cameras are capable of internally. Or take log and output it via the cameras 10 bit output (if it has one) and record that directly on the ProRes recorder. It doesn’t matter how you do it but if you convert between different recording types you will always reduce the image quality and this is as bad a way to do it as you can get. This mainly relates to cameras like the PXW-FS7. The FS5 is different because it’s internal UHD recordings are only 8 bit, so even though the raw is still compromised by converting it to ProRes log, this can still be better than the internal 8 bit log.
S-Log like any other log is a compromise recording format. Log was developed to squash a big dynamic range into the same sized recording bucket as would normally be used for conventional low dynamic range gammas. It does this by discarding a lot of tonal and textural information from everything brighter than 1 stop above middle grey, instead of the amount of data doubling for each stop up you go in exposure, it’s held at a constant amount. Normally this is largely transparent as human vision is less acute in the highlight range, but it is still a compromise.
The idea behind Linear raw is that it should give nothing away, each stop SHOULD contain double the data as the one below. But if you only have 12 bit data that would only allow you to record 11 stops of dynamic range as you would quickly run out of code values. So Sony have to use floating point math or something very similar to reduce the size of each stop by diving down the number of code values each stop has. This has almost no impact on highlights where you start off with 100’s or 1000’s values but in the shadows where a stop may only have 8 or 16 values dividing by 4 means you now only have 2 or 4 tonal levels. So once again this is a compromise recording format. To record a big dynamic range using linear what you really need is 16 bit data.
In summary so far:
S-Log reduces the number of highlight tonal values to fit it a big DR in a normal sized bucket.
Sony’s FSRaw, 12 Bit Linear reduces the number of tonal Values across the entire range to fit it in a compact 12 bit recording bucket, but the assumption is that the recording will be at least 12 bit. The greatest impact of the reduction is in the shadows.
Convert 12 bit linear to 10 bit S-Log and now you are compromising both the highlight range and the shadow range. You have the worst of both, you have 10 bit S-Log but with much less shadow data than the S-log straight from the camera. It’s really not a good thing to do and the internally generated S-Log won’t have shadows compromised in the same way.
If you have even the tiniest bit of under exposure or you attempt to lift the shadows in any way this will accentuate the reduced shadow data and banding is highly likely as the values become stretched even further apart as you bring them up the output gamma range.
If you expose brightly and then reduce the shadows this has the effect of compressing the values closer together or pushing them further down the output curve, closing them together as they go down the output gamma range, this reduces banding. This is one of the reasons why exposing more brightly can often help both log and raw recordings. So a bit of over exposure might help, but any under exposure is really, really going to hurt. Again, you would probably be better off using the internally generated S-Log.
To make matters worse there is also often an issue with S-Log in a ProRes file.
If all that is not enough there is also a big problem in the way ProRes files record S-Log. S-Log should always be recorded as full range data. When you record an internal XAVC file the metadata in the clips tells the edit or grading software that the file is full range. Then when you apply a LUT or do your grading the correct transforms occur and all shadow textures are preserved. But ProRes files are by default treated as legal range files. So when you record full range S-Log inside a ProRes file there is a high likelihood that your edit or grading software will handle the data in the clip incorrectly and this too can lead to problems in the shadows including truncated data, clipping and banding, even though the actual recorded data may be OK. This is purely a metadata issue, grading software such as DaVinci resolve can be forced to treat the ProRes files as full range.
It’s a common problem. You are shooting a performance or event where LED lighting has been used to create dramatic coloured lighting effects. The intense blue from many types of LED stage lights can easily overload the sensor and instead of looking like a nice lighting effect the blue light becomes an ugly splodge of intense blue that spoils the footage.
Well there is a tool hidden away in the paint settings of many recent Sony cameras that can help. It’s called “adaptive matrix”.
When adaptive matrix is enabled, when the camera sees intense blue light such as the light from a blue LED light, the matrix adapts to this and reduces the saturation of the blue colour channel in the problem areas of the image. This can greatly improve the way such lights and lighting look. But be aware that if trying to shoot objects with very bright blue colours, perhaps even a bright blue sky, if you have the adaptive matrix turned on it may desaturate them. Because of this the adaptive matrix is normally turned off by default.
If you want to turn it on, it’s normally found in the cameras paint and matrix settings and it’s simply a case of setting adaptive matrix to on. I recommend that when you don’t actually need it you turn it back off again.
Most of Sony’s broadcast quality cameras produced in the last 5 years have the adaptive matrix function, that includes the FS7, FX9, Z280, Z450, Z750, F5/F55 and many others.
Sony have just released the latest version of their free viewing, copying and transcoding software Catalyst Browse and the more fully featured paid software Catalyst Prepare. These new versions includes support for the PXW-FX9’s metadata based image stabilisation. Hopefully the new Mac versions are also optimised for Catalina.
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:
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.
it, camera base plates are not really very exciting things. But they are very
necessary additions to most peoples kit, especially for any of the full size
super 35mm digital cinema cameras. From Red’s to F55’s to FS7 etc, they will
almost always need some form of base plate at some point.
So what’s different about the Vocas sliding system?
A complete Vocas sliding base plate system comprises two main parts. The first bit attaches to the camera and that will be either a generic flat camera mounting adapter plate or a custom camera mounting plate for cameras that don’t have flat bases, for example the FS7 or Venice where the adapter follows the curve or shape of the bottom of the camera.
The second part is a shoulder mount, shoulder pad or tripod plate or generic flat mounting plate that the camera adapter smoothly and securely slides onto.
One of the first benefits of this system is that you can easily alter the position of the camera relative to the base plate or shoulder pad. This makes balancing the camera on your shoulder or on a tripod much easier. A large red level locks the two sliding parts securely in place and there is a safety release catch that must be pressed if you wish to separate the mounting plate from the base plate, so they can’t come apart by accident. However if you need to move the camera forwards or backwards relative to the mounting plate all you need to do is release the large red locking lever.
Another benefit of the system is that it is very quick to reconfigure if you need to. For example many cinematography accessories are mounted using 19mm rails rather than the lightweight 15mm rails often used with ENG or smaller rigs. Perhaps you have been shooting handheld where a lightweight 15mm setup works better. Using the Vocas sliding system you can have a light weight base plate with a comfortable shoulder pad, 15mm front and rear rails that will clip in and out of a VCT style quick release tripod plate attached to the camera for your handheld shots. Then when you need to go to a bigger lens perhaps and 19mm rods, you simply slide off the 15mm base plate and slide on the Vocas 19mm plate. Quickly transforming the camera into a heavy duty rig that will then attach to an Arri style tripod plate. Need to keep the 19mm rods but now need a shoulder pad? Well that’s easy too as there is a matching shoulder pad for the 19mm base plate. It’s all very quick and very easy.
It also means that if you have multiple cameras all you is a mounting plate on each of your cameras then you can use the same base plate on all your cameras just by sliding it on and off as needed, or swap between lot’s of different types of plates depending on your needs.
If you don’t need a base plate with rods etc and just need a quick way to mount your camera to a tripod then there is also a basic tripod adapter that the camera can be slid directly onto. This gives you a really secure, quick release, low profile mounting system that is free from the wobble that often plagues other quick release mounts. It’s ideal for crash cams, car mounts and car rigs. Or for those situations where you just need something quick and compact. This would also help keep the weight down for use on gimbals or perhaps a stedicam. Need to go back to a shoulder mount or full tripod rig with rods, just slide the camera off the tripod plate and slide it on to your preferred 15mm or 19mm shoulder plate.
Nice touches on the VCT type base plates are the adjustable height rod mounts and also an adjustable tensioner for the rear mounting spigot. Normally on a VCT base plate the rear spigot doesn’t do a great deal to add stability to the system, it just helps to loosely locate the base plate. However Vocas have added the ability to put some tension on to the rear spigot to help pull the camera down onto the VCT plate. This can greatly decrease, if not eliminate the wobble and flex that is all to common with these quick release plates.
really nice touch is that the attachment screws for the mounting plate and an
allen key for adjusting the height of the rod mounts can be stored inside the
base plate so you should never loose them.
Any downsides? Well yes, any 2 part system like this is going to be a little more complex with more parts and a bit more metal than a basic fixed mounting plate, so the sliding base plate ends up a touch heavier than the equivalent fixed position base plate. It’s not a big difference, but it does add a bit of weight. However in most cases I believe it’s worth it. Especially if you are swapping between 15mm and 19mm systems frequently. Being able to quickly and easily re-balance the camera when handheld and you change lenses is very nice.
If you have more than one camera it makes it easier to share different mounting systems between them. So while the initial cost may be a bit more, in the long run you only ever need to add new mounting adapters to keep using all the different base plates you have with extra cameras or new cameras.
As always with Vocas products the quality of the engineering is first class. The parts fit together beautifully. Only high quality materials are used and the finish is very nice. So if you are looking for a really nice base plate for your camera – or cameras – do take a look at the Vocas sliding system. It’s really very well thought out and something that will last for a very long time.
I have a good relationship with the guys at Vocas. I had been shown this system
at various trade shows and it looked interesting, so I approached Vocas for the
loan of a review system so I could write this article.
Camera setup, reviews, tutorials and information for pro camcorder users from Alister Chapman.