Like b5 before it, ASP does a great job of selecting the appropriate Camera Make Model & Lens, etc.
Since not every Camera is known there are limitations but if the software functions with your RAW file
both the documentation and general discussions on the topic encourage users to find useable setting
and save a new DefaultRaw.xmp... A very good idea, but remember it's easy to go overboard by saving
too many settings in your "New DefaultRaw.xmp". If you need more than just a few simple changes
A new Preset might be a better choice. In either case keep it simple.
Presets are .xmp files just like the sidecar files are.
As a general proposition the sidecar.xmp contains explicit instructions only.
It explicitly gives values to be applied to the RAW file. On the other hand Preset.xmp's can contain
both explicit [as above] and implicit instructions which specify values not directly mentioned in the Preset,
all values not expressly given in the Preset remain unchanged from the previously existing sidecar.xmp file.
If no sidecar.xmp exists [yet] then ASP programatically uses DefaultRaw.xmp to establishes the required values.
A quick review of the originally supplied DefaultRaw.xmp reveals that it contains almost no explicit values
so the program does all of the work on the initial pass, mostly selection of Lens Correction;
Camera Make Model Lens Focal Length & Resize image ON, BUT DOES NOT Enable correction.
Understanding these behaviors is slightly obscured because ASP [or b5] doesn't write the initial
sidecar.xmp unless and until the user changes any setting - even the slightest thing, like Lens Correction ON.
When the program writes that very first sidecar.xmp it includes the Lens Correction stuff noted above and
what amounts to an inventory of all possible settings including those in any plugins that you have installed.
It also includes the one slight change you made to some setting in order to get that first sidecar.xmp...
The original DefaultRaw.xmp causes ASP to identify any [known] Camera Image that you give it.
Once you save a "New DefaultRaw.xmp" ASP follows the "new instructions" you've set. If the "New" Default
contains Camera or Lens specific settings ASP's ability to identify new equipment will be influenced.
In my case I only needed DefaultRaw to be Enable correction ON. If you are doing something simple like that
be careful not to include any other settings such as Focal Length which in my case gets properly set by ASP.
If you do each new image will be given the same Focal Length.
Finding the right settings for my camera was a bit confusing because I was using the factory supplied preset "ResetEverything"
to help speed things along. ResetEverything has a flaw, it resets ALMOST everything but at the same time tells ASP
that the image is from a camera that you might wish you owned - but you don't!
Here are the WRONG SETTINGS that ship with ResetEverything...
bopt:warpfocal="105"
bopt:profilemake="Canon SLR"
bopt:profilemodel="EOS 5D Mark II"
- EDIT - There is more than this, I have given more attention to the settings in a post below...
Not even close - I own a Panasonic Camera... and I'd recommend fixing ResetEverything before using it - it makes a nice exercise.
I hope this post provides encouragement to experiment with Preset - one of b5/ASP most best features.
I also hope it encourages users to share their Preset Tricks and to be careful when changing DefaultRaw.xmp.
One final thought. If your original DefaultRaw.xmp has been replaced by a "New" one that isn't giving you what
you want, and you can't fix it, a copy of the original exists at the address here:
Help>System Info...>System Home: C:\Program Files (x86)\Corel\Corel AfterShot Pro\supportfiles\defaults\defaults
HAVE FUN!
