The interface is clear and understandable with oodles of visual feedback and options. Instead of a cheesy little palette full of sliders and buttons, Color Finesse opens up its own full-screen graphical user interface (GUI). When used in Adobe After Effects for example, it loads the Color Finesse application up in memory and keeps it memory (user definable of course). Nothing too accurate about that!Īlthough packaged as a plugin, Color Finesse is really an application unto itself. When using a standard brightness tool in Adobe After Effects for example, the result adds RGB gain to make it appear it's really bright, when in fact it's adding contrast and clipping for the illusion of brightness. Just like the inaccurate audio speakers you can buy at the store that boost specific audio frequencies to make them appear as if they sound good, so is the same with standard color correction tools. Totally inaccurate! View the results on a waveform monitor and you'll see a mix of clipping, noise gain, rounding errors, RGB gain, contrast gain, saturation gain, banding and some times errors so profound they actually create errors in the places they were supposed to fix! With Color Finesse, you're using a tool that is scientifically accurate, resulting in a natural, lifelike results. Standard color correction tools are the same way. You know those great sounding speakers you can buy at the local audio/video/computer store? Lots of bass and bright highs with a lot of color? So why don't recording studios use these speakers? Because they're totally inaccurate! If you measure the frequency response of the speaker's output, you'll get a graph that's something akin to the Swiss Alps. The best example I can use for relating Color Finesse to standard color correction/effect tools is by the following example. Instead of writing an article review explaining the merits of such a fine product Color Finesse is, I will otherwise try to convince you that the current crop of color correcting/effect tools available today are junk and without this tool, you're missing out on superior color correction quality available in software form. the Color Finesse plugin by Synthetic Aperture is by far the best color correction tool available for post production, save a DaVinci color suite costing a few hundred grand. WARNING! THIS ARTICLE REQUIRES HIGH RESOLUTION IMAGESįOR COMPARISON PURPOSES RESULTING IN LONG DOWNLOAD TIMES! The differences are shocking! Note: this is NOT an article on how to color correct (although some of the principles are explored in the article and there is much to be learned here). Parenthesis are valid in directory and filenames.Article, photos and images © 2002, Marco Solorioĭon't have the hundreds of thousands of dollars for a DaVinci color-correction system? But you do have After Effects? In a jaw-dropping review of Synthetic Aperture's 'Color Finesse,' Marco Solorio shows how Color Finesse far surpasses the capabilities of standard color correction tools - as well as the error-prone realities of using standard color correction plug-ins. I renamed that directory, using File Explorer, removing the parenthesis, and now this file behaves normally!!! I was suspicious of the 2nd set of parenthesis, "(Color Finesse 2 Support)". 'Z:\backups\desktop\Cdrive\Program Files (x86)\Adobe\Adobe After Effects CS4\Support Files\Plug-ins\Effects\Synthetic Aperture(Color Finesse 2 Support)\Color Finesse 2\Color Finesse Presets\Gels\GamColor CineFilters\GamColor CineFilters_1-4 Plus Green.cfpreset'. However, the first File.Copy throws an exception, "Could not find a part of the path". I figured there was some corruption in the NTFS tables, so I added recovery code to my program that was going to copy each file to \tmp, delete the original, then copy back (figuring this would create a fresh, valid entry). However, it does exist, I can see them with File Explorer, select Properties and get valid results, and I have verified their contents(a few are. Once I had this list of files, I called System.IO.FileInfo on each one and found 166 files where FileInfo.Exists=false, which implies exactly what it says, that file does not exist. I wrote a C# program that walked the entire directory tree for a NTFS volume that had over 1.5M files. NET Framework 4.8 System.IO.FileInfo() and File.Copy() (at least).
0 Comments
Leave a Reply. |