Whites, Super Whites and other Bits and bobs.

Do you know how your NLE is handling your video, are you whites white or whiter than white or does this sound like a washing powder add?

In the analog world you shot within the legal range of black to 100% white. It was simple, easy to understand and pretty straight forward. White was white at 100% and that was that. With digital video it all gets a lot more complicated, especially as we now start to move to greater and greater bit depths and the use of extended range recording with fancy gamma curves becomes more common. In addition computers get used more and more for not just editing but also as the final viewing device for many videos and this brings additional issues of it’s own.

First lets look at some key numbers:

8 bit data gives you 256 possible values 0 to 255.

10 bit data gives you 1024 possible values, 0 to 1023.

Computers use bit 0 to represent black and bit 255 or 1023 to represent peak white.

But video is quite different and this is where things get messy:

With 8 bit video the first 16 bits are used for sync and other data. Zero or black is always bit 16 and peak white or 100% white is always bit 235, so the traditional legal black to white range is 16 to 235, only 219 bits of data. Now in order to get a better looking image with more recording range many cameras take advantage of the bits above 235. Anything above 235 is “super white” or whiter than white in video terms, more than 100%. Cinegammas and Hypergammas take advantage of this extra range, but it’s not without it’s issues, there’s no free lunch.

10 bit video normally uses bit 64 as black and 940 as peak white. With SMPTE 10-bit extended range you can go down to bit 4 for undershoot and you can go up to bit 1019 for overshoots but the legal range is still 64-940. So black is always bit 64 and peak white always bit 940. Anything below 64 is a super black or blacker than black and anything above 940 is brighter than peak white or super white.

At the moment the big problem with 10 bit extended (SMPTE 274M 8.12) and also 8 bit that uses the extra bits above 235  is that some codecs and most software still expects to see the original legal range so anything recorded beyond that range, particularly below range can get truncated or clipped. If it is converted to RGB or you add an RGB filter or layer in your NLE it will almost certainly get clipped as the computer will take the 100% video range (16-235) and convert it to the 100% computer RGB range (0-255). So you run the risk of loosing your super whites altogether. Encoding to another codec can also lead to clipping. FCP and most NLE’s will display super blacks and super whites as these fall within the full 8 or 10 bit ranges used by computer graphics, but further encoding can be problematic as you can’t always be sure whether the conversion will use the full recorded range or just the black to white range. Baselight for example will only unpack the legal range from a codec so you need to bring the codec into legal range before going in to baselight. So as we can see it’s important to be sure that your workflow is not truncating or clipping your recorded range back to the nominal legal or 100% range.

On the other hand if you are doing stuff  where the full 0 to 255 (1023) are used then you often need to use the illegal video levels above 100% white to get whites to look white and not bright grey!  There are so many different standards across different platforms that it’s a complete nightmare. Arri with Alexa for example won’t allow you to record extanded range using ProRes because of these issues, while the Alexa HDSDi output will output extended range.

This is also an issues when using computer monitors for monitoring in the edit suite. When you look at this web page or any computer graphics white is set at bit 255 or 1023 (a lot will depend on the gamma that the monitor is set to). But that would be a super white or illegal white for video. As a result “in-range” or legal range videos when viewed on a computer monitor often look dull as the whites will be less bright than the computers own whites. The temptation therefore is to grade the video to make the whites look as bright as the computers whites which leads to illegal levels, clipping, or smply an image that does not look right on a TV or video monitor. You really need to be very careful to ensure that if you shoot using extended range that your workflow keeps that extended range intact and then you need to remember to legalise you video back to within legal range if it’s going to be broadcast.

Comparison clips to download.

Here is a set of 3 clips in the native formats taken with a Sony VG10, Canon t2i (550D) and sony F3.

CLICK HERE for the zip file containing the native fies (canon .mov, sony .mts and Sony BPAV folder) or click here to watch on vimeo. If you are going to watch on vimeo I would strongly urge you to take a look at the full size frame grabs below before coming to any conclusions.

I used the same Nikon 50mm f1.8 lens on all 3 cameras (MTF F3 adapter, cheap E-Mount adapter and cheap Nikon to Canon adapter). I had the lens at f8-f11 for all three cameras and used the shutter to control exposure or in the case of the F3 the ND filters. All were set to preset white, 5600k, the sky was visually white with flat hazy cloud. The VG10 was at factory default, the t2i was default except for Highlight Tone Priority which was ON and the F3 default with the exception of Cinegamma 1 being chosen.

PLEASE PLEASE PLEASE Don’t link directly to the download file, instead link to this page. Feel free to host the clips, just remember they are my copyright so include a link back here or a note in any text of where they originated.

PLEASE make a donation of whatever amount you feel appropriate if you find these clips helpful, to help cover my hosting fees if you choose to take advantage of these otherwise free clips. It’s a 340Mb download. As of May 9th, 122 people have downloaded the clips, that’s 41Gb of web bandwidth, yet not one person has made a donation. Come on guys and gals, if you want me to  make clips available to download, help me out.

Below are some frame grabs from the 3 cameras. If you click on the pictures a couple of times they will open full size in a new window. All 3 cameras do a pretty decent job overall. However both the VG10 and t2i have issue with aliasing on the brickwork of the far building. I know the idea with these cameras is to use a shallow DoF so often the background will be soft, but not everything will be like that all the time. There are also more compression artefacts from both the t2i and in particular VG10 (the barbed wire at the beginning of the pan looks pretty nasty). At least with the VG10 you can take the HDMI output and record that externally. Clearly the best pictures are from the F3, but then it is considerably more expensive than the others. It is interesting to note the distinctly yellow colorimetry of the F3. I do have matrix settings to reduce this, but I did not use them during this assessment.
Also note how much wider the FoV is with both the Canon t2i and even more so the F3. Clearly these cameras have larger sensors than the VG10, the largest being the F3’s Super35 sized sensor. This was another surprise, I had assumed the Canon and F3 sensors to be much closer in size than this. Remember that all three used the same lens and the shots were done from exactly the same place.
You can also view the clips on Vimeo http://vimeo.com/23315260
NEX-VG10
t2i -550D
PMW-F3

 

Focal length conversion factor should apply to the camera not the lens.

I was asked in some post comments whether the a 50mm PL mount lens would give a wider picture than a 50mm DSLR lens. This confusion comes about I believe because of all the talk about focal length conversion factors. I don’t think this concept is well understood by some people as the implication is that somehow the lens is changing when its used on different cameras, when in fact it’s the camera that is different, not the lens.

It is important to understand that a 50mm lens will always be a 50mm lens. That is it’s focal length. It is determined by the shape of the glass elements and no matter what camera you put it on it will still be a 50mm lens. A 50mm DSLR lens has the same focal length as a 50mm PL mount and as a 50mm 2/3″ broadcast lens. In addition the lens focuses a set distance behind the rear element, agin the distance between the rear element and where it focuses does not change when it’s put on different cameras, so an adapter or spacer must be used to keep the designed distance between the lens and sensor, this distance is called the “flange back”.

The key thing is that it’s not the lens or it’s focal length that changes when you swap between different cameras. It is the size of the sensor that changes.

Imagine a projector shining an image on a screen so that the picture fills the screen. The projector is our “lens”. Without changing anything on the projector what happens if you move the screen closer or further away from the projector? The image projected on the screen will go in and out of focus, so that’s not good, we must keep the projector to screen distance constant, just like the lens to sensor distance (flange back) for any given lens remains constant.

What happens if we make the screen smaller? Well the image remains the same size but we see less of it as some of the image falls of the edge of the screen. If our projected picture was that of a wide landscape then on the reduced screen size what would now be seen would not appear less wide as we are now only seeing the middle part of the picture. The width of the view would be decreased, in other words the FIELD OF VIEW HAS NARROWED. The focal length has not changed.

This is what is happening inside cameras with different size sensors, the lens isn’t changing, just how much of the lenses projected image is falling on or off the sensor.

So the multiplication factor should be considered more accurately as being applied to the camera, not the lens and the multiplication factor changes the field of view, not the focal length.

So whether it is a PL mount lens, a Nikon or Canon DSLR lens or a Fujinon video lens, if it’s a 50mm lens then it’s a 50mm lens and the focal length is the same for all. However the field of view (width and height of the viewed image) will depend on the size of the sensor. So a 50mm PL lens will give the same field of view as a 50mm DSLR lens (no matter what camera the lens was designed for) on the same video camera.

The only other thing to consider is that lenses are designed to work with certain sizes of sensor. A lens designed for a full frame 35mm sensor will completely cover that size of sensor as well as any sensor smaller than that. On the other hand a 2/3? broadcast lens will only cover a 2/3? sensor, so if you try to use it on a larger sensor the image will not fill the frame.
The sensors in the Sony F3 and FS100 are “Super 35mm”. That is about the same size as APS-C. So lenses designed for Full frame 35mm can be used as well as lenses designed for 35mm cine film (35mm PL) and lenses designed for APS-C DSLR’s such as the Nikon DX series and Canon EF-S.

See also http://www.abelcine.com/fov/

 

Storm Chasing and Video Production Workshop.

Shooting a Supercell Storm

Just a reminder that I am running a documentary production workshop between the 7th and 15th of June. Based out of Denver, USA this will be an amazing adventure, road-trip and intensive workshop all rolled into one week. Only 3 places remain at just $1,500 USD per person, plus accommodation. Please see this page for full details. This year is a La Nina year, so we can expect more storms and tornadoes than on average years. May and June are the peak months for severe storms in the USA. We have seen in the past week the power of these storms. One important note is that the storms that killed so many people last week were travelling at 50 to 60 mph across the ground. One of the reasons for chasing in June is that the storms tend to move much more slowly, often only 20 mph so there are far more opportunities to stop and shoot. In addition the weather systems move onto the wide open plains of Colorado, Nebraska and the Dakotas giving incredible vistas.

3D Workshop at Samy’s Camera (Fairfax store) LA. Also Cinegear appearance.

I shall be in LA with the Genus Hurricane Rig for Cinegear at the beginning of June. Then on June the 5th and 6th I am running a two day 3D workshop where you can gain full certified Hurricane Rig accreditation. The normal fee for the full two days is $500 USD however if you purchase a hurricane rig between now and then the course is free and you get the option to do the second day hurricane rig accreditation workshop again for free. If you just want to attend the first day and the intro to 3D workshop then you can attend for just $50. Make any purchases at Samy’s totalling $500 or more and the day is free. Lunch will be provided and it should be a lot of fun as well as an interesting insight into the world of S3D. See http://www.samys.com for more details.

35mm World Workshops at Haydock Park (UK) on May 12th.

I’m presenting a couple of 35mm world sessions at the BPV Northern Expo at Haydock Park on May 12th. These are free sessions, around 90mins each. They will focus on the Sony F3 and FS100, but will also touch on the f65 and f35. The aim is to take a look at the pro’s and con’s of shooting with a camera with a Super35mm sensor as well as to give an understanding of which cameras are appropriate for which jobs. Hopefully we will have an interesting discussion session at the end of each workshop and the chance to get hands on the FS100 and F3. More details here: http://www.bpv.org.uk/

Updated notes for FS100 – F3 Video Review.

To see the video scroll down to the next blog entry.

The main aim of the shoot was to see how the FS100 held up against the F3. We shot on a bright sunny day by the River Thames and again in the evening in a typically lit living room. There were no big surprises. The FS100 is remarkably close to the F3. You would have no problems cutting between the two of them in a project.
I did find that the FS100 LCD appeared less sharp and not quite as good as the F3’s even though they both use the same underlying panel. This is probably down to the additional layers required for touch screen operation on the FS100. I also did not like the 18-200mm f5.6 kit lens. There was too much lag in the focus and iris controls, but the beauty of this camera is that you can use a multitude of lenses. For the evening shoot I used a Nikon 50mm f1.8 which was so much nicer to use. On reviewing the footage I did find that we were tending to over expose the FS100 by half a stop to a stop, this does make making accurate comparisons difficult and I apologise for this. I believe this was down to the slightly different images we were seeing on the LCD’s. I did use the histograms on both cameras to try to ensure even exposure, but even so there is a difference. A small part of this is also likely down to the very slightly different contrast ranges of the two cameras.
Oe thing we discovered, not mentioned in the video is that when you use a full frame lens, like the Nikon 50mm. You must ensure that the E-Mount adapter you use has an internal baffle or choke. If it doesn’t you will suffer from excessive flare. The adapter I had did not have a baffle and some shots (not used) were spoilt by flare. The adapter I have from MTF for the F3 has a baffle as do MTF’s E-Mount adapters, so these should not suffer from this issue.
The FS100 performance is so very close to that of the F3’s (at 8 bit 4:2:0, 35Mb/s) that it is hard to tell the two apart. I believe the F3’s images are just a tiny bit richer, with about half a stop more dynamic range, in most cases it takes a direct side by side comparison to show up the differences.
The range of camera settings and adjustments on the FS100 is not quite as extensive as on the F3, nor do the adjustments have such a broad range. However there is plenty of flexibility for most productions.
If you don’t need 10 bit 4:2:2 then it is hard to justify the additional cost of the F3, both cameras really are very good. Despite some other reports else where I felt the build quality to be very good and the buttons, while small, are big enough and well placed. If you do want autofocus then you will be pleased to know that it actually works pretty well on the FS100 with only minimal hunting (of course you must use an AF compatible lens).
I did also record the HDMI output to one of my NanoFlashes at 100Mb/s. Comparing these side by side it is extremely hard to see any difference. It is only when you start to heavily grade the material that the advantage of the higher bit rate Nanoflash material becomes apparent. There is less mosquito noise in the NanoFlash material. I was really impressed by the AVCHD material. The lack of noise in the images really helps.
The FS100 really is the F3’s little brother. The pictures are remarkably close, which they should be as they share the same sensor. The FS100 packs down into a remarkably small size for transport. The loan camera from Sony was actually packed in a case designed for the MC1P mini-cam, about 15″x10″x5″ so very compact indeed. The F3 is considerably larger and bulkier, in part due to the extra space taken up by the built in ND filters.
The lack of ND filters does need to be considered. There are some clever solutions in the pipelines from various manufacturers as well as existing solutions such as vari ND’s, screw on ND’s and a Matte Box with ND’s, so it’s not a deal breaker
I think there is every chance that the FS100 will be the first NXCAM camera that I will purchase. It will be a good companion to my F3. It’s modular design will allow me to get shots that are not possible with the F3. I felt that the FS100 (with the 18-200mm lens that I don’t like) was better suited to “run and gun” than my F3 with either manual DSLR lenses or PL glass. You can, with the FS100 simply point the camera at your subject and hit the one push auto focus and auto iris and have an in-focus, correctly exposed shot. This is much more like a traditional small sensor camcorder in this respect. The long zoom range also makes this more like a conventional camcorder, although there is no servo for the zoom.

In conclusion, in my opinion, for “run and gun” or quick and dirty setups the FS100 with the 18-200mm lens has an edge over the F3 due to the fast auto focus and auto iris one-push controls. For more precise work and shallow DoF your going to want a different lens, something with manual control and calibrated focus and iris scales. For more demanding shoots then the F3 is probably the better choice with it’s slightly improved dynamic range and the ability to use S-Log and 4:4:4. In either case these cameras can produce highly cinematic pictures and I see no reason why you could not shoot a great looking feature with either.

Is this the future of 3D?

I am a big fan of 3D. I designed a a 3D rig, so I must be an enthusiast! However even I don’t believe that 3D is the future for all video production, but I do believe it is here to stay. I think it is for special event television, special features, movies and specialist presentations. I have long said that many of these non-movie productions will end up in the cinema. This has been born out by the release of a 3D film about the Isle of man TT races. TT3D, Closer to the edge, released just 4 days ago has shot straight into the top 10 of the UK box office charts making it one of the most successful documentary releases in UK cinema history.