Lens correction settings

[B4b5]

The trick to all such problems is to NEVER change the DefaultRaw.xmp...

Let the Original unmolested DefaultRaw.xmp pick whatever it likes best
then treat all of the image files with a preset that changes only those thing
that need fixing...

Make separate presets for any different lenses that aren't picked correctly
but unless you have some real expertise don't mess around with the DefaultRaw.xmp.

ASP & Bibble documentation make it sound trivial but I've never found it to be a
good idea to play with the DefaultRaw.xmp.

I recommend reverting to your original DefaultRaw.xmp and doing what you need with presets only.

[Tadjio]

The appropriate entries for me seem to be the following:
bopt:profilemake="Canon SLR"
bopt:profilemodel="EOS 7D"
bopt:profilelens="Canon EF-S 15-85mm f/3.5-5.6 IS USM"
bopt:lens="Canon EF-S 15-85mm f/3.5-5.6 IS USM"

preceded by:
bopt:warpon="true"
bopt:warpresize="true"
(?)

Perhaps if I set the default lens to the proper Sigma it will only correct for the Canon lens. I'll see ...

I would guess not but it will be interesting to see...

As I said the software seems to check the lens after it applies the initial settings because it has then reset the lens to the (almost) correct lens and still left the lens correct set to ON.

I have a Canon too, so you can post me whichever wide-angle lens you don't need...

Good idea. I'll get right on that

Thanks. I can then swap out my EF 24-105 occasionally (that I keep on the camera all the time)

[greerd]

Did you see I had another line:- bopt:lens="Micro 4/3 Zuiko Digital 14-42mm F3.5-5.6 ED"
This seems to override the Metadata definition of the lens, so it might solve your problem???

The appropriate entries for me seem to be the following:

bopt:profilemake="Canon SLR"
bopt:profilemodel="EOS 7D"
bopt:profilelens="Canon EF-S 15-85mm f/3.5-5.6 IS USM"
bopt:lens="Canon EF-S 15-85mm f/3.5-5.6 IS USM"

What I did was load an unadjusted RAW image, set the lens correction to ON and then did a right-click -> Settings -> Write AfterShot Xmp. I then changed the name to the default raw file and copied it to the default folder. I did not see the direct way to do it, but this seems to have worked well enough. I will continue to play around with this. Perhaps if I set the default lens to the proper Sigma it will only correct for the Canon lens. I'll see ...

As I said the software seems to check the lens after it applies the initial settings because it has then reset the lens to the (almost) correct lens and still left the lens correct set to ON.

I have a Canon too, so you can post me whichever wide-angle lens you don't need...

Good idea. I'll get right on that

From what i understand of the lens profiles, your sigma 10-20 isn't suported for your 7D, but it is for cameras with a 1.0 and 1.5 crop factors. If you look in the LensProfile directory /opt/AfterShotPro/supportfiles/Profile/LensProfiles (in linux) the profile_canonSLR.txt states the 7D has a multipier of 1.6 and belongs to the group genericSLR (among others) The profile_genericSLR.txt has the sigma 10-20 but only for multipiers of 1.0 and 1.5. You could maybe cheat and use the 1.5, I'm not sure how much difference there would be.

[thufor]

From what i understand of the lens profiles, your sigma 10-20 isn't suported for your 7D, but it is for cameras with a 1.0 and 1.5 crop factors. If you look in the LensProfile directory /opt/AfterShotPro/supportfiles/Profile/LensProfiles (in linux) the profile_canonSLR.txt states the 7D has a multipier of 1.6 and belongs to the group genericSLR (among others) The profile_genericSLR.txt has the sigma 10-20 but only for multipiers of 1.0 and 1.5. You could maybe cheat and use the 1.5, I'm not sure how much difference there would be.

Lens calibration made with multiplier 1.5 works for 1.6x sensors. This is because ASP will "scale" calibration from 1.5 field to 1.6. The same works when calibration exists for 1.0 multiplier only - ASP will use that and "scale" accordingly. The reverse however is impossible, e.g. ASP will not be able to use 1.6 calibration for 1.5 or 1.0 sensor. There is simply no mathematical transformation to apply it the rest of the image since the calibration doesn't describe how distorted the rest of the image outside of the smaller calibration is. Hope this explanation is clear enough to understand ;-)

This information has been provided by development team on Bibble forums quite a while ago.

[greerd]

From what i understand of the lens profiles, your sigma 10-20 isn't suported for your 7D, but it is for cameras with a 1.0 and 1.5 crop factors. If you look in the LensProfile directory /opt/AfterShotPro/supportfiles/Profile/LensProfiles (in linux) the profile_canonSLR.txt states the 7D has a multipier of 1.6 and belongs to the group genericSLR (among others) The profile_genericSLR.txt has the sigma 10-20 but only for multipiers of 1.0 and 1.5. You could maybe cheat and use the 1.5, I'm not sure how much difference there would be.

Lens calibration made with multiplier 1.5 works for 1.6x sensors. This is because ASP will "scale" calibration from 1.5 field to 1.6. The same works when calibration exists for 1.0 multiplier only - ASP will use that and "scale" accordingly. The reverse however is impossible, e.g. ASP will not be able to use 1.6 calibration for 1.5 or 1.0 sensor. There is simply no mathematical transformation to apply it the rest of the image since the calibration doesn't describe how distorted the rest of the image outside of the smaller calibration is. Hope this explanation is clear enough to understand

This information has been provided by development team on Bibble forums quite a while ago.

Good to know, I was only ever interested in micro 4/3rds which doesn't have this issue (yet). So with that out of the way, MikeFromMesa should be able to just delete any entries of "Sigma 10-20mm f/3.5" from the profile_genericSLR.txt file and give his lens a better chance of being picked? Knowing full well that the next ASP update will overwrite his edited file.

[MikeFromMesa]

Let the Original unmolested DefaultRaw.xmp pick whatever it likes best
then treat all of the image files with a preset that changes only those thing
that need fixing...

Believe me, I tried that before I started posting.

The problem is that I often have many different images taken with different lenses all jumbled up in a single folder. If I select one image, copy the preset and then paste that preset onto other images I end up with many images with the wrong selected lens. And, since I don't have any indication from an image what lens was used to take the photo (and I often don't remember exactly where I changed lenses) I end up having to manually reload the EXIF information for all the images. That resets the lens, but I am trying to avoid doing all that manual work repeatedly for perhaps hundreds of photos.

[MikeFromMesa]

preceded by:
bopt:warpon="true"
bopt:warpresize="true"
(?)

Yes. Along with a lot of other stuff mixed in.

[MikeFromMesa]

From what i understand of the lens profiles, your sigma 10-20 isn't suported for your 7D, but it is for cameras with a 1.0 and 1.5 crop factors. If you look in the LensProfile directory /opt/AfterShotPro/supportfiles/Profile/LensProfiles (in linux) the profile_canonSLR.txt states the 7D has a multipier of 1.6 and belongs to the group genericSLR (among others) The profile_genericSLR.txt has the sigma 10-20 but only for multipiers of 1.0 and 1.5. You could maybe cheat and use the 1.5, I'm not sure how much difference there would be.

I did not know that. That is interesting. Perhaps I can figure out some way to add the f/3.5 lens to the Canon database by changing the crop factor to 1.6 and using the f/4-5.6 distortion information. If I can do that then it will not matter if ASP selects the f/3.5 since the distortion information will be the same as for the f/4-5.6.

It will give me something to do this morning. Thanks.

[Tadjio]

preceded by:
bopt:warpon="true"
bopt:warpresize="true"
(?)

Yes. Along with a lot of other stuff mixed in.

Yes, I think this is the core of Enabling Lens Correction (warp).
I also think that setting bopt:lens="XXXX" (for the MetaData) alongside bopt:profilelens="YYYY" is where the profile matching occurs.

Does anyone know, is it possible to have Conditional (IF...ELSE...) tests in Presets?

[MikeFromMesa]

Good to know, I was only ever interested in micro 4/3rds which doesn't have this issue (yet). So with that out of the way, MikeFromMesa should be able to just delete any entries of "Sigma 10-20mm f/3.5" from the profile_genericSLR.txt file and give his lens a better chance of being picked? Knowing full well that the next ASP update will overwrite his edited file.

Yes. That actually seems like a better idea than mine of adding the f/3.5 to the Canon database. If I can remove the f/3.5 from the generic perhaps it will start defaulting to the proper lens.

More good information. Thanks again. I will try that later this morning and post my results.

[MikeFromMesa]

So far I have done the following:

1) Selected a single image that had no changes made to it yet, set the lens correction functionality to ON, wrote out the resulting xmp file (right-click -> XMP -> Write AfterShot XMP files), renamed the file to DefaultRaw.xmp and copied it to the defaults folder. Of course I backed up the original DefaultRaw.xmp file before I over-wrote it,

2) Removed the Sigma 10-20mm f/3.5 lens from the profile_genericSLR.txt file (and, of course, I backed up the original file first),

3) Removed the sidecars from one of the folders I had that contained images that had automatically defaulted (improperly) to the Sigma 10-20mm f/3.5 lens and renamed the folder containing those images,

4) Started ASP and selected the new folder.

All of the images in that folder automatically defaulted to the proper lens (Sigma 10-20mm f/4-5.6). The previously selected lens (Sigma 10-20mm f/3.5) is no longer on the list of available lenses. So far, so good. When it gets lighter I will take some new photos with the Sigma lens, copy them to the computer and see if that also works properly, but I am much more positive that before that things are now working properly.

Thanks to all of you who have posted to help me solve this problem.

[RickHeath]

In 1 - a better option, that is less likely to add unwanted info/settings to your defaults, would be be to right click on a suitable image with lens correction enabled & go to Settings>Save as RAW/Camera default. Click on the Advanced tab and find the Lens correction section and open it up to check that only "enabled" is ticked (it was like that on the test image I tried it on just now). Any other sections that you don't want enabled in your default you can untick while you are at it before saving.

If you copy XMP from an image there is a risk that you may set other things in subsequent files that you did not intend to.

Regards

Rick.

[MikeFromMesa]

In 1 - a better option, that is less likely to add unwanted info/settings to your defaults, would be be to right click on a suitable image with lens correction enabled & go to Settings>Save as RAW/Camera default. Click on the Advanced tab and find the Lens correction section and open it up to check that only "enabled" is ticked (it was like that on the test image I tried it on just now). Any other sections that you don't want enabled in your default you can untick while you are at it before saving.

If you copy XMP from an image there is a risk that you may set other things in subsequent files that you did not intend to.

Regards
Rick.

I actually tried that yesterday but after writing the new DefaultRaw.xmp file, exiting ASP and restarting it I found that the lens correction setting was still OFF. It appeared that for some reason the new file did not get written and I did no further investigation as to why. That is how I ended up doing this the long and detailed way.

However I agree that your idea is better and should work and I will try later today to find out why it did not work earlier. The folder containing all of these setup files is protected, of course, and it may be that the system would not allow me to write the new DefaultRaw.xmp file (I am administrator on the system so it should have worked). Or it may be that I thought I wrote it but failed to actually properly click on the context menu. Or it may be that I need to explicitly start ASP as administrator. I will check and post my results. And thank you for the comment.

[rawshoter]

Does anyone know if there is some way to set the defaults so that ASP will automatically set the lens correction to ON by default?

May could this be helpful?
I did not test it by my self so far but from what´s written there, it sounds like quite useful.

http://support.bibblelabs.com/forums/vi ... 98&t=19806

[MikeFromMesa]

Does anyone know if there is some way to set the defaults so that ASP will automatically set the lens correction to ON by default?

May could this be helpful?
I did not test it by my self so far but from what´s written there, it sounds like quite useful.

http://support.bibblelabs.com/forums/vi ... 98&t=19806

Thank you for the link to the post but this appears to be a Bibble plugin and, as far as I know, there is not a version for ASP. At least yet. Still I will keep an eye open for one.