> Just guessing but worth a try. I think you need to add the lense
> information from the /usr/share/lensfun/slr-canon.
> xml (just the one lense)
> to /usr/share/lensfun/slr-sony.xml and it should work as expected.
>
> I believe darktable *only* parses the camera data file for *your* camera.
Good idea
!
It was not working in *sony.xml files so I added my lens in generic.xml; I
slightly modified it to a generic lens:
<lens>
<maker>Generic</maker>
<model>Canon FDn 50mm 1:1.4</model>
<mount>Generic</mount>
<cropfactor>1.0</cropfactor>
<calibration>
<distortion a="-0.000919817" b="0.00112022" c="-0.00289404"
focal="50" model="ptlens" />
<tca bb="0.0000216" br="-0.0000338" focal="50" model="poly3"
vb="0.9998764" vr="1.0002152" />
<vignetting aperture="1.4" distance="0.45" focal="50"
k1="-0.2747" k2="-0.1546" k3="0.1527" model="pa" />
<vignetting aperture="1.4" distance="1" focal="50" k1="-0.5692"
k2="0.3348" k3="-0.1042" model="pa" />
<vignetting aperture="1.4" distance="3" focal="50" k1="-0.6686"
k2="0.5132" k3="-0.2054" model="pa" />
<vignetting aperture="1.4" distance="1000" focal="50"
k1="-0.6918" k2="0.5512" k3="-0.2278" model="pa" />
<vignetting aperture="2" distance="0.45" focal="50"
k1="-0.0668" k2="0.0029" k3="-0.0171" model="pa" />
<vignetting aperture="2" distance="1" focal="50" k1="-0.0725"
k2="-0.0250" k3="0.0104" model="pa" />
<vignetting aperture="2" distance="3" focal="50" k1="-0.0748"
k2="-0.0428" k3="0.0297" model="pa" />
<vignetting aperture="2" distance="1000" focal="50"
k1="-0.0782" k2="-0.0459" k3="0.0329" model="pa" />
<vignetting aperture="2.8" distance="0.45" focal="50"
k1="-0.0604" k2="-0.0194" k3="0.0045" model="pa" />
<vignetting aperture="2.8" distance="1" focal="50" k1="-0.0732"
k2="-0.0241" k3="0.0120" model="pa" />
<vignetting aperture="2.8" distance="3" focal="50" k1="-0.0832"
k2="-0.0198" k3="0.0121" model="pa" />
<vignetting aperture="2.8" distance="1000" focal="50"
k1="-0.0824" k2="-0.0342" k3="0.0223" model="pa" />
<vignetting aperture="4" distance="0.45" focal="50"
k1="-0.0694" k2="-0.0016" k3="-0.0078" model="pa" />
<vignetting aperture="4" distance="1" focal="50" k1="-0.0828"
k2="0.0019" k3="-0.0081" model="pa" />
<vignetting aperture="4" distance="3" focal="50" k1="-0.0919"
k2="-0.0002" k3="-0.0022" model="pa" />
<vignetting aperture="4" distance="1000" focal="50"
k1="-0.0919" k2="-0.0064" k3="0.0028" model="pa" />
<vignetting aperture="22" distance="0.45" focal="50"
k1="-0.1151" k2="0.1018" k3="-0.0809" model="pa" />
<vignetting aperture="22" distance="1" focal="50" k1="-0.1117"
k2="0.0668" k3="-0.0536" model="pa" />
<vignetting aperture="22" distance="3" focal="50" k1="-0.1539"
k2="0.1340" k3="-0.0892" model="pa" />
<vignetting aperture="22" distance="1000" focal="50"
k1="-0.1587" k2="0.1348" k3="-0.0874" model="pa" />
</calibration>
</lens>
2015-01-09 20:13 GMT+01:00 Pedro Côrte-Real <[email protected]>:
>
>
> This is a really bad idea. Editing raw files can lead to corruption
> very easily. Seems much easier to just set this in the darktable
> interface or if you need to do it in bulk setting that in the db/xmp
> file. Raw files should be considered as read-only at all times.
I don't agree, meta-data are meant to be edited. But you are right it seems
to corrupt the white balance :(
Selecting manually
was impossible, the lens
wasnot listed.
I will try to add the tags and test with the generic lens added.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
