brucet wrote:Maybe Corel could simply give us an option to have 2 lists of lens. One as is. The other with our own lens listed. Then enable us to make 'our' list the default list. As we buy lens we add them to 'our' list. ASP could then simply look in 'our' list and pick the appropriate lens.
Or am I making it too simple?
Or more simply keep the one list but allow user to change the order so that owned lenses are at the top. Not that it is going to happen. Especially because you can already do this via support files.
I realize it is not as easy as a gui interface, but you can accomplish the same thing by editing the text file lens lists. For example in Windows 7 64 the Canon lens list is at
C:\Program Files (x86)\Corel\Corel AfterShot Pro\supportfiles\Profiles\LensProfiles\profile_canonlenstable.txt.
These lens ids seem to mostly follow exiftool
, the defacto "industry standard." You can find more info on exif and maker notes tags elsewhere on the exiftool site. Note that the X.Y lens id numbers is a convention invented by exiftool (which is say Phil Harvey) to sort lenses with same id. the value of .Y is arbitrary. All lenses starting with X report the same number in maker notes. (e.g. listed lenses 131, 131.1, 131.2, etc. all report 131.)
see also for links to other manufacturers and overview http://owl.phy.queensu.ca/~phil/exiftool/TagNames/index.htmlhttp://owl.phy.queensu.ca/~phil/exiftool/index.html
All photo editors start identification with lens id. Some (apparently DxO in some cases) try to resolve between the lenses using makernotes or exif data. Bibble had implemented this, though it was not perfect. See for example this post
from Jeff. I haven't tested whether ASP retained this or just looks at lens id. (I am still using Bibble waiting for the bugfix release of ASP.) In some cases the lens cannot be completely resolved due to identical max aperture and overlap in focal lengths. See Canon lens id 131 for example. DxO might only try when they have created a module for the lens. I have some Sigma lenses that should be resolvable, but have no module, and DxO fails to identify them.
While I'm at it, unlike DxO, ASP allows you to immediately add lens correction profiles that you have created using the manual correction tool. (I assume ASP also will, as Bibble did, create profiles from images you submit, though that requires waiting for the next release.) Lens profiles are stored (again using Canon as example) at
C:\Program Files (x86)\Corel\Corel AfterShot Pro\supportfiles\Profiles\LensProfiles\profile_canonSLR.txt, and
C:\Program Files (x86)\Corel\Corel AfterShot Pro\supportfiles\Profiles\LensProfiles\profile_genericSLR.txt.
The procedure and format is explained Here
To some degree DxO vs ASP is a philosophy difference. DxO does everything for you and bundles tools (lens modules include geometric, CA, vignette, etc) which means it takes longer for them to do, and you have to wait for their schedule. Support files in DxO are not accessible to users. ASP support files are stored as text files (the extension may be .txt, .ui, .batch, .js, .queue, .xmp, etc, but all can be edited with a text editor). So ASP allows you to add your own stuff immediately and to edit support files directly and with more flexibility, but you have to work a little harder.
edited to correct spelling.