Change Input Gamma to Panasonic V-Log and Input Gamut to Panasonic V-Gamut. cube, click Analysis, and let the Web App do the work. In the LUTAnalyst section, select “Choose File” to load the Panasonic 709 conversion LUT, note that the file format is. And the value is roughly 4.9 stops Above 18% gray. The goal is to match the image’s false color overexposure part (red color) to the clipping area that appeared in the waveform. We will repeatedly adjust and output LUT in LutCalc, and then load it into the camera for testing. By observing the waveform, we know that in V-Log plus DR Boost mode, the highlight clipping point of the GH6 is around 88% IRE value, which is a crucial reference indicator. The general idea is to modify the official LUT based on GH6 characteristics. There are two materials for making the false color LUT, the first is the official Panasonic V-Log to V709 LUT, and the second is the LutCalc conversion tool developed by Ben Turley. So the LUT has only targeted the V-Log plus DR Boost mode. Otherwise, its dynamic range is even slightly worse than the old GH5. Since the GH6 uses a dual gain output sensor (DGO) that provides additional 1.5 stops of dynamic range, I believe most professional creators will use the V-Log plus Dynamic Range Boost mode. Fortunately, we can load a false color LUT in the V-Log View Assists menu to achieve this feature that only some higher-end cinema cameras have. However, in more complex scenes, you may need false color to work faster because you can see the IRE value of each part of the image. In most scenarios, exposure using waveform is sufficient. We all know that the GH series provides videographers with many convenient exposure control tools other mirrorless cameras do not have, such as waveform. If you are not interested in the technical details, you can download the LUT file I have already generated and copy it to the memory card, then use the V-Log View Assists menu on the GH6 to read and use it. It should be a bit smoother now.GH6 does not have the False Color function built-in, but we can achieve this advanced feature by loading a Monitor LUT (.vlt). If your screen is big enough, you can enlarge the window to avoid scrollbars when displaying the preview and the charts together.Īs for bugfixes, there are small ones to the PSST-CDL, basically around interpolation. Lastly, I've got around to sorting out window resizing. I have also added the C300mkII and Panasonic Varicam 35 to the camera options, basically so that you can compare camera black / white clip levels on the chart. Spoiler alert - it looks extremely similar to Arri LogC. Not ideal, but assuming the chart is correct the error should be less than 1%, and good enough to get an idea pending proper Canon White Papers. I used a chart in the C300mkII introduction video to estimate it. On the camera / gamma front, I have added in a fairly decent stab at the upcoming Canon Log2 curve. It is shaped like a filled-up vectorscope and is hand to get an idea what adjustments will do overall. I've added another preview option - this one is a colour wheel displaying the Rec709 colour space. LUTCalc will then set the LUT parameters as recommended or required and generate a LUT in the appropriate format. You are then shown a selection of applications or cameras (OK, the cameras is only Sony 3D User MLUT at the moment, but I have the Varicam code in place, just making sure of levels). Instead of a Sony-specific 'MLUT' option, you now choose between 'Grading LUT' and 'Camera LUT (MLUT)'. I've also tried to make it easier to get the settings right when generating a LUT. The capability is also there to save in these formats and to add more as I learn about them. In addition to cube files, LUTAnalyst can now read Resolve 1D iluts and oluts plus Panasonic 3D vlt files. I'm planning to submit the LUTCalc For Mac version to the Mac App Store, so have added a bit more than I intended to make it more flexible / generally useful. I've just uploaded a new version of LUTCalc and LUTCalc For Mac, and this one really, really should be the last before calling it v2.0.
0 Comments
Leave a Reply. |