Global Config
You can save default settings in ~/.pprc/configs/default.json so they apply to every
run without needing CLI flags. CLI flags always take priority over config values.
On Windows, ~/.pprc/ resolves to %USERPROFILE%\.pprc\
(e.g. C:\Users\<you>\.pprc\).
Saving config
The easiest way to create a config is with --save-config:
pprc --clip 2.5 --dir-out ../INPUT_DIR_inverted --save-config This saves the specified options and exits without processing.
Named configs
You can save named configs for different workflows and switch between them with
--use-config:
pprc --mode bw --clip 1.0 --save-config bw pprc --use-config bw
Named configs are saved to ~/.pprc/configs/<name>.json and are complete
replacements for the default config. They are not merged with it.
Manual editing
You can also create or edit ~/.pprc/configs/default.json directly:
{
"dirOut": "../INPUT_DIR_inverted",
"clip": 2.5
} Configurable options
The following options can be set in the config file:
dirOut— output directory templatemode— processing mode (negative,raw,e6,bw,bw-rgb)perImageBalancing— per-image balancing (boolean)noFrameRejection— disable frame rejection (boolean)clip— clip both ends by N%clipBlack— clip darkest N%clipWhite— clip brightest N%outputGamma— output gamma applied during inversion (default: 2.15)noStretch— disable contrast stretch (boolean)borderExclude— exclude outer N% from profilingpixelRejectionPercentage— ignore brightest/darkest N% of pixelsprofile— name of a saved inversion profile to use. Saved profiles live in~/.pprc/profiles/<name>.json(%USERPROFILE%\.pprc\profiles\<name>.jsonon Windows).
Last run config
After each run, PPRC saves the effective settings to ~/.pprc/last_run_config.json.
If you liked the results, you can copy it to use as your config:
macOS / Linux:
cp ~/.pprc/last_run_config.json ~/.pprc/configs/default.json Windows:
copy %USERPROFILE%\.pprc\last_run_config.json %USERPROFILE%\.pprc\configs\default.json Config display
When settings are loaded from config, PPRC displays them at startup so you always know what's being applied. If a CLI flag overrides a config value, both are shown.