View Full Version : New Film Looks available
Jason Rodriguez January 1st, 2008, 11:24 PM Hi,
We've uploaded a bunch of new film-emulation looks that we have created for the SI-2K. These .look files will allow the SI-2K to emulate some common negative and reversal film-stocks. Please note that this is not the same as emulating the native SI-2K color-space to a film-print stock like a 2383 or 2393 print (Vision Premiere print stock) that you would use on a film-out . . . this is actually an emulation of the colorimetry and gamma that one would get capturing on an original film-negative and/or reversal film-stock.
You can get them in the Silicon Imaging Look Library (http://www.si-2k.com/SiliconImaging_looks.html).
Thanks,
Jason
Lior Molcho January 2nd, 2008, 05:35 PM Hey Jason
could you please explain again the difference between these looks and film out looks?
in what instance should we use these new ones then?
Thanks
Lior
Jason Rodriguez January 2nd, 2008, 09:14 PM "Film-out" .look files are like the "Neutral_2383_Film.look". They basically say, "I have an SI-2K aligned to sRGB or ITU-R709 color-space, and I want to know what the camera will look like when it goes out on a piece of print film at the movie theater."
It's basically seeing what the camera's default color-space will look like when you print it and want to see it at the theater. Rather than a film-print, it could also be a DCI-based digital projector, etc. The main point is that the color-space of the SI-2K will be it's default aligned color-space such as a sRGB or ITU-R709 color-space.
These new looks take the SI-2K and basically say, "I want the SI-2K to mimic an image I would have captured if I shot on XYZ film-stock." There is a fundamental difference here. We're not talking about the camera's default color-space on a final release film-print at the theater, we're talking about wanting the scene to look like it was really shot with a certain shooting film-stock (In the case of Kodak these "shooting film stocks" would be the 52xx series versus a release-print stock that is in the 23xx series and in a normal film-chain would come after interpositive and internegative dupes).
So with these new .looks, we're maping the color-space of the camera to the colorimetry of a shooting film-stock rather than a default color-space like ITU-R709. You will notice there is no 3x3 matrix entry for these .look files . . . that is because this is no longer a pure linear transformation like going from the native XYZ space of the camera to sRGB or ITU-R709. It is a non-linear transformation designed to have the camera mimic the non-linear colorimetry of color negative and reversal film-stocks.
Thanks,
Jason
Bob Hart January 3rd, 2008, 08:03 AM Jason.
You won't forget the Agfa neg stocks and workprint stocks of the seventies-early eighties now will you?
John DeLuca January 3rd, 2008, 01:58 PM This is awesome Jason! Thank you for listening to customer feedback (I asked about the Provia 100F look awhile back). I’m curious how you where able to ‘map’ the film stock. Did you do it by eye with a calibrated monitor, or did you use some type of calibration.
Forgot to add- My favorite stocks of all time- Kodachrome 25 or Ektachrome EPP 100 Natural, yet gorgeous color.
Jason Rodriguez January 3rd, 2008, 01:58 PM If we can get our hands on them, then we can do them . . . :)
At this point in time, we chose some based off Fuji Provia and Kodak 250D. The Fuji Provia-based versions are not exactly Provia, but are like them a bit . . . that's why I didn't label them as Provia. The Kodak 250D versions are a statistical "best-fit" with some hand-tweaking to balance between accuracy and noise, but overall are pretty accurate compared to scanned Kodak 250D film-stock (so i.e., matching against Kodak 250D may not be perfect if you use a different scanner or telecine compared to what we used for our source data).
Did you do it by eye with a calibrated monitor, or did you use some type of calibration.
Well, I can't say exactly how it was done, but generally it's accomplished using statistical modeling of the different colorspaces. That allows one to get a good fit without incurring too much noise from the sometimes more extreme non-linear transformations that a pure 1:1 mapping would incur when trying to map from the source camera's color-space to the colorimetry of film stocks. So that means they should look pretty good by-eye, but sometimes that last 2% of mathematical accuracy can create some very funky effects in certain conditions. Since these looks have to be "general", meaning work in all lighting conditions, the accuracy under one isolated condition has to be balanced against delivering good results as well.
Thanks,
Jason
Bob Hart January 4th, 2008, 10:45 AM Jason.
Does that mean that if you were given the colour curves from the particular film stock you could recreate the look from those?
It is simply amazing you can do all this in a video camera.
Jason Rodriguez January 4th, 2008, 10:53 AM BTW, these types of transformations can't be done with curves (per-channel 1D LUTs), they can only effectively be done through 3D gamut mapping.
But yes, this is pretty cool technology, and one of the great powers that having a real-time 64-point cube 3D LUT system running in real-time on the camera can provide.
Mathieu Kassovitz January 8th, 2008, 11:01 PM Congratulations. The competition should follow your finest example.
Bob Grant January 9th, 2008, 05:24 AM I tried loading some of these Looks a few days ago, wasn't paying much attention to which ones sorry. The thing I did notice was they alter the exposure and readout on the meters, so presumably the false colour and histogram readings are taken after the Look is applied.
This raises the question of how should we actually be using the metering in the camera and what significance can we attach if the Look we'd like to use indicates we're clipping and the default Look shows we're not. I think I can understand the logic of this but I could use some clarification to be certain.
Jason Rodriguez January 9th, 2008, 10:19 PM Both Histogram and False color are taken pre-look. This was done so that no matter what the .look is, you'll know if you're screwing yourself during a shoot (i.e., if the .look is clipping but you're not clipping the RAW data, then no big deal . . . but you don't want to have a .look that doesn't show clipping, or somehow changes the contrast curve and doesn't give you an adequate indication of what the "true" RAW exposure is at, then you can do silly things like underexpose too far, massively over-expose, etc.).
The ONLY meters that should change relative with the .look file are those inside the IRIDAS control panel. This is so you can see the effects on the visual exposure of your changes when you're making a new .look file.
Now one thing to keep in mind is that a different .look file will change how you expose to get a "proper" looking image on the screen . . . i.e., Default.look uses a standard REC709 curve, and that crushes the shadows quite a bit and maximizes the effective SNR (i.e., middle-grey is "pushed higher" in the exposure scale). This forces one to expose a stop or two more open than another .look that would open up the shadows, and push the middle-grey point down in the exposure scale, so with a different .look you would be stopping down a little bit to get the same "visual" exposure. That is not a bug, that is the nature of different .look files having different digital gain and contrast mapping features.
So for instance, if you set the meters, and start flipping through .looks (i.e., set the main screen to false color meter mode, and just flip through the .looks), you should not see any switch in the false color meter. The same with the histogram. Now with the meters off, you will *visually* see a difference, but the underlying RAW data is all the same.
The reason I'm adding this note is because I can't reproduce a meter variation in the main GUI with the switching of .looks, so it seems to be operating normally in the latest builds (this build is not ready for release though).
If you want some more information on what I'm talking about with contrast mapping using a .look file, you can view my power-point presentation on exposing for RAW from NAB07 here (http://www.siliconimaging.com/DigitalCinema/Files/CameraRawWorkflows.ppt).
If your meters are really changing as you swap though .looks (they shouldn't have), that would be a bug. Please let me know which version of software you are using if you think you've encountered a bug.
Thanks,
Jason
Bob Grant January 10th, 2008, 08:19 AM Thanks for the detailed reply. I'll check this again just to be 100% certain.
Bob Grant January 11th, 2008, 03:56 AM Went back and checked again today. All is good, the meters aren't changing. What threw me was as you said was the shift in visual exposure, I think somehow because the colors of the subject were very close to the colors of the false color metering I got confussed.
However your detailed post has explained a lot for me, the pieces are coming together.
Jason Rodriguez January 11th, 2008, 11:11 AM Great, thanks for the feedback though, this was a very good question (and I should probably post it in the FAQ).
Bob Grant January 11th, 2008, 06:31 PM I had one thought later. Would there be any advantage to having the DVR meters switchable pre and post Look?
One other issue I struck yesterday. Please, please, can we have the DVR software accept keyboard as well as touch screen input. Trying to enter project names by clicking a spot on the screen using a dodgy laptop touchpad drove me nuts. Partially my own fault, I'd left my USB mouse behind. For some reason on the Dell 6300 the DVR software seems way more sensitive to the touchpad then Windows. I had to barely touch the pad or as I moved the pointer around every time it passed over a charcter on the onscreen keyboard DVR would input the character. Not a big thing but on a live shoot I can see this creating a lot of frustration.
Jason Rodriguez January 11th, 2008, 06:51 PM The on-screen keyboard already supports keyboard entry (i.e., when in the on-screen keyboard, just type if you want rather than clicking around on the keys). The only thing to keep in mind is that the DEL key is actually "delete" on a keyboard, not back-space. JFYI.
Thanks,
Jason
Jason Rodriguez January 11th, 2008, 06:56 PM As far as the meters being pre or post-look, the biggest issue is that what you're seeing is all pixel shaders as far as the 3D LUT rendering is concerned, and this is what allows us to-do quite a bit of fancy stuff in real-time . . . the downside is that GPU's are meant to render *to* the screen, not recall data back into the computer, and as a result, that reverse path is REALLY slow and hogs a lot of CPU.
There is a histogram that reflects the actual effects of the look (i.e., the image "post-look" rather than the RAW data) when you're inside the IRIDAS color-correction screen, but as you can see there, it updates very slowly, and it pulls a lot of CPU (more than you would think necessary for something so "simple").
I guess in a year or so when resources and pipelines between GPU and CPU are much smoother this won't be so much of an issue, but for right now it is, especially on mobile platforms.
|
|