Recognising Sigma 50mm F1.4 DG HSM
Added by Anonymous Poster over 7 years ago
New lens: Sigma 50mm F1.4 DG HSM
Hi,
I'm am the happy owner of this new lens (the successor to the "Sigma 50mm F1.4 EX DG HSM" which is still being marketed...) -in Canon mount. This also being refered to as "Sigma 50mm F1.4 Art", but I believe the correct designation is "Sigma 50mm F1.4 DG HSM".
I would like to contribute to enable you to include recognition of this lens by Exiv2. My technical abilities probably don't go much further than supplying test images.
Here is a test shot (RAW file) shot with this lens (on a Canon 6D):
https://dl.dropboxusercontent.com/u/1148011/Sigma_50mm_F1.4_DG_HSM.CR2
Many thanks in advance,
Henrik Kristensen
PS: I don't actually use Exiv2 directly, but rather the library via Darktable.
PPS: It is currently being recognised as "Canon EF 35mm f/1.4L"
Replies (4)
RE: Recognising Sigma 50mm F1.4 DG HSM - Added by Robin Mills over 7 years ago
Henrik
I've opened issue# 969 to deal with this: http://dev.exiv2.org/issues/969
I've assigned this to Niels as he usually deals with this kind of issue. Thanks for the test file. The test file is rather large (20mb). Neils may ask you to provide a small jpg and/or raw image that we can include in our test suite.
Robin
RE: Recognising Sigma 50mm F1.4 DG HSM - Added by Niels Kristian Bech Jensen over 7 years ago
This is a duplicate of issue #959 which was fixed in the svn trunk a month ago.
Best regards,
Niels Kristian Bech Jensen
RE: Recognising Sigma 50mm F1.4 DG HSM - Added by Anonymous Poster over 7 years ago
Excellent! Looking forward to seeing it further down the stream :-)
thanks, Henrik
RE: Recognising Sigma 50mm F1.4 DG HSM - Added by Robin Mills over 7 years ago
We discussed a couple of things at the Team Meeting which relate to this: http://dev.exiv2.org/boards/3/topics/1765
1) API Management Andreas owns this
DigiKam want us to never change the API of our library. They want the DLL to always appear identical, then users of application such as DigiKam and DarkTable. and “drop in” a new version of our library and the application can use it.
2) Accessory overflow file Tuan owns this
Several folks have suggested that we add new models and accessories into an external file. Then it’s possible to change the overflow file in an application such as DigiKam or DarkTable. Tuan is going mentor in GSoC2015 and I’ve asked him to evaluate candidates by asking them to implement this. So in Exiv2 0.26 should have this feature.
When we ship a new version 0.26, 0.27, the overflow file should be empty and everything compiled into the library. Additions and corrections can be added if we check the overflow file, before falling back on the current “built-in” model.
Neils has ideas about the overflow file/file(s). It's desirable to be able to update those file(s) using the internet. Tuan, as the Cloud Ready Engineer, is in a strong position to implement an API to perform this update. We should consider how providing this API can be achieved with minimum disruption. Perhaps an "argc/argv" interface to the library should be provided as this enables to add/change semantics APIs without compromising binary API compatibility.
Robin