

preset file exported from any Perfectly Clear desktop application using PFC_ReadPresets Use one of the pre-defined presets available in the PFCPRESETID enum.There are three ways you can set the correction parameters to be applied in this SDK: Set bFastFAE to false when calling PFC_AutoCorrect.Set the CALC_FAEHISPEED feature when calling PFC_Calc.The one used by default in this SDK and in our Perfectly Clear desktop software is High Quality. The speed difference is between 10% and 20% of total processing time, and the detection rate is about 1% to 2% better on High Quality. High Speed is quicker, but is not as good at finding smaller faces. High Quality takes slightly longer to process, but find more faces - especially backlit, small faces. This affects the performance of the face detection process, which is used by Face Aware Exposure to gain insight into the exposure values of the people in your photos. There are two operating modes for Face Aware Exposure: High Quality and High Speed. In FAE exposure cases (enabled and faces are found), the maximum exposure will be (50, 100, 150) based on eAggressiveness. Specifically, the recommended exposure level will not exceed the iMaxStrength value you set when FAE is disabled, or when FAE is enabled, but a face is not detected. However, manually setting PFCCOREPARAM.iMaxStrength can still have an affect on the exposure correction level. Instead, it's automatically set to 50, 100, or 150 based on the value of PFCCOREPARAM.eAggressiveness (low, med, or high).

This last option is not able to be directly set within our Perfectly Clear desktop applications. Attempting to set iStrength to a specific value while bUseAutomaticStrengthSelection is true has no effect. The actual value of iStrength will also depend on image content, of course. When PFCCOREPARAM.bUseAutomaticStrengthSelection is 'true' then iStrength will be set automatically, and is influenced by all the other parameters. PFCCOREPARAM.iStrength is what will actually be applied to the image. There are several parameters which affect our automatic exposure correction: You can export these settings to be used in the SDK, as described below. These various corrections are best previewed and evaluated in our desktop applications like Perfectly Clear Complete, Workbench or QuickDesk.Finishing Tools and Graduated Filters are not supported on mobile platforms at this time.V3 LOOKs support is provided via an optional "v3.looks" file that should be deployed along with the SDK library files."V3 LOOKs" support - Finishing and Graduated Filters, along with several other corrections added in the "V3" versions of our Desktop products."Beautify" Corrections (licensed as an optional component).
