in).
Thanks, I added your contribution!
Tschö,
Torsten.
--
Torsten Bronger
smime.p7s
Description: S/MIME cryptographic signature
___
Lensfun-users mailing list
Lensfun-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lensfun-users
Hallöchen!
Guido Scholz writes:
> as I found the current lensfun database does not list my Fujifilm
> X-H1 and some other models as well. Does someone care to add
> these:
>
> [...]
Thank you, I added the cameras!
Tschö,
Torsten.
--
Torsten Bronger
smime.p7s
Desc
, possibly resolve, non-upload tickets and issues on GH and
SF.
- Patch DT for the new Lensfun API (once we know how it looks like).
- Move to GitHub.
Regards,
Torsten.
--
Torsten Bronger
___
Lensfun-users mailing list
Lensfun-use
ence negligible. In particular, it is not wrong.
Note that Lensfun’s correction bases on its own distortion
measurements, and the Sony engineers have made their own
measurements. It is only natural that the results are not exactly
the same.
Regards,
Torsten Bronger.
--
lf of the image
height (in landscape mode). Thus, the value is bigger than 1 on the
corners.
Regards,
Torsten Bronger.
--
Torsten Bronger
___
Lensfun-users mailing list
Lensfun-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lensfun-users
am only -- lensfun-update-data --
and therefore, I don't plan to advertise it specially. Sometimes I
have to point people to
http://wilson.bronger.org/lensfun-db/version_0.tar.bz2 because that
is for Lensfun users with versions too old to be shipped with
lensfun-update-data.
Regards,
Torsten
rds,
Torsten Bronger.
--
Torsten Bronger
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Lensfun-u
Hallöchen!
Diogo Sousa writes:
> I have created a profile for the DJI Mavic Pro FC220. I'm
> submitting it for inclusion in the lens profile database.
Thank you, I included your data!
Tschö,
Torsten.
--
Torsten B
Hallöchen!
Kelvie Wong writes:
> Could this be added to mil-sony.xml?
>
>
> Sony
> ILCE-7RM2
> Alpha 7R II
> Sony E
> 1
>
Thank you, I included this entry!
Tschö,
To
sensor and lens.
Tschö,
Torsten.
--
Torsten Bronger
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
T
ce), the
*distance* doesn't matter. But in practice, I believe that it is
very tricky to do this right, and even more so to validate it.
Especially stray light is difficult to manage.
Tschö,
Torsten.
--
Torsten Bronger
-
impLensfun, but my entry
> ./local/share/lensfun/test.xml doesn't get included in the lens
> list. The file itself gets loaded - I get an error message, when
> it contains garbage (but only if before ).
What does t
escribed in the vimeo tutorial. This way, I created my custom
> lensfun.xml file [2].
Please try to add an aspect ratio tag to the lens. I suspect the
camera produces 4:3 images, however, Lensfun assumes 3:2 by
default. If this doesn't help, I dig deeper.
Tschö,
Torsten.
--
Torsten Bronger
es too,
> pending updated hugin instructions.
So I should send you access credentials?
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
--
What NetFlow Analyzer can do for yo
be paper (if absolutely level of course). The
actual ilumination should not cast a visible gradiant of the
diffuser but unless somebody points a laser pointer to it, I think
this will work in all practical cases.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten
are willing to help – much or little – send me an email.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
--
What NetFlow Analyzer can do for you? Monitors network bandwidth
camera and 5.9 for the lens (based perhaps on full area vs. JPEG
> area?)
Actually, bot must be the same Otherwise, your calibration data
would not be applied accurately.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
Hallöchen!
Roman Lebedev writes:
> This will allow to do *some* verification of the database XML's
> at the build time. Well, each time make is run.
I just re-found check_database.py. Maybe the checks shoudl be
incorporated into that and connected with a Git hook?
Tschö,
Torsten.
--
T
.php?title=Lens_correction_model=14463=14358
By the way, for Lensfun, d != 1 is really unfortunate, because we
need to preserve the effective focal length for certain algorithms.
Thus, Lensfun jumps through some hoops for un-doing the scaling.
Hope this clears up some things ...
Tschö,
Tors
Hallöchen!
Torsten Bronger writes:
> [...]
>
>> What you are suggesting is to rescale Rd -> d*Rd which is not
>> allowed.
>
> If you scale Rd, which is used for the look-up, this is a uniform
> scaling of the original image.
Here, I was wrong. If you scale Ru
Hallöchen!
Torsten Bronger writes:
> [...]
>
> This may happen with a bad calibration. But whether you use
> a',b',c',d' or a,b,c has no effect on accuracy. In fact, both can
> be transformed into another:
>
> a = a' / d'^4
> b = b' / d'^3
> c = c
Hallöchen!
Helmut Jarausch writes:
> On 06/16/2016 05:31:05 PM, Torsten Bronger wrote:
>
>> Helmut Jarausch writes:
>>
>>> On 06/16/2016 01:52:38 PM, Torsten Bronger wrote:
>>>
>>> [...]
>>>
>>>> [...] But can't you
Hallöchen!
Helmut Jarausch writes:
> On 06/16/2016 01:52:38 PM, Torsten Bronger wrote:
>
> [...]
>
>> [...] But can't you just use the Lensfun formula in Octave?
>
> Of course, I could, but it won't make sense. As one can see in
> the table below, the sum of the coe
e name?
* Should the DTD get a valid URL as its name?
* Should this check be enabled by default when building/installing?
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
--
What N
em is that Lensfun cannot process distortion parameters
depending on distance. Currently, at least I don't have plans to
change this because it would mean complicated modifications with
small benefit.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: tors
longitudinal CA and blown-out
highlights.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
sing? Could you
make one of your calibration images available for me?
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
--
What NetFlow Analyzer can do for you? Monitors network bandw
Hallöchen!
junkyardspar...@yepmail.net writes:
> [...] The attached version seems to behave better throughout the
> focus range.
Thank you for your contribution! Which camera did you use? (Just
for the record.)
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabbe
a Nikon MakerTag issue based on its
> output, but I hope to get it working even if I don't have
> auto-detection.
But a failing autodetection should also fail before your changes.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
---
case the image processed by Silkypix differs significantly
> from that produced by darktable which uses lensfun. If I crop the
> image produced by darktable to pixels 173 .. 5299 x 115 .. 3533
> and rescale the image to 5472 x 3648 pixels I get
Collect all elements of one lens model in one entry.
7. Add optional "camera" attribute to .
Any comments are welcome!
Tschö,
Torsten.
--
Torsten BrongerJabbe
a usage outside the PanoTools? Has anybody reported
benefit from it?
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
--
___
Lensfun-us
Hallöchen!
Torsten Bronger writes:
> [...] (Plan is to add affine transformations later, to be really
> complete.)
I now also added affine transformation (scaling, rotation, shift) in
the branch "affine-transformation". See also
<http://wilson.bronger.org/lensfun-affine/st
ould be grateful for any
feedback, especially whether the code compiles properly with
non-GCC, and whether the test suite runs through on your hardware.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabbe
in lensfun cmake files...
We fixed an issue with the Python package yesterday in the branch
"debian-packaging". Please test this branch for your use case.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
--
as 135mm nominal and focus at
infinity?
[...]
Are you interested if we propose a pull request with a new calibration
binary (with OpenCV optional at compile time)?
I personally no. I do not believe in checkerboard calibrations for
reasons I have stated earlier.
Tschö,
Torsten.
--
Torsten
of the images tell differently).
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
--
___
Lensfun-users mailing list
Lensfun-users
because it had been taken at close focus,
and did not work *at* *all* for images taken at a large distance.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
of http://www.digicamdb.com
?
Nice site, but their figures are not more accurate than ours.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs
/calibration
Regards,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support
with distances larger than 10m. At the same
time, the highest accuracy provide uninterrupted horizontal features
that span the whole image width. This is why I urge people to take
pictures of modern buildings.
Regards,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
at http://wilson.bronger.org/calibration
Regards,
Torsten Bronger.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide
Hallöchen!
muellst writes:
I did calibrate the vignetting of my new
Sigma 12-24mm
f/4.5-5.6 EX DG ASPHERICAL HSM
lens and like to share my results.
Thank you for the data! Which camera model was used?
Regards,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth
, or adding a Prepare...() method, is better in my opinion.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
--
Dive
and GPtrArray
- void in the declarations moved to lensfun.h.in and some other
places, and static-typecast them back to the GLib types when we call
GLib functions?
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger
Hallöchen!
junkyardspar...@yepmail.net writes:
My question now is if the TCA correction really need to be at the
same focal lengths as the distortion corrections.
No, it needn't.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
and generate TCA entries like
tca model=poly3 focal=focallength vr=red vb=blue /
Older darktable versions swapped red and blue, so check the result!
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger
for his
lens (which he had before). This must not happen.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
--
Dive
for his
lens (which he had before). This must not happen.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
--
Dive
. Still, Lensfun should return something that can be safely
cast to integer. Alternatively, one can force the calling programs
to change their checks. In any case, Lensfun should adopt
well-defined and documented behaviour for such cases.
Tschö,
Torsten.
--
Torsten BrongerJabber ID
Hallöchen!
We need alias names for cameras and lenses. How could be dealt with
the fact that a certain camera models have different names on
different continents?
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http
to
converters
- two or more compact cameras may be optically equivalent, thus,
they share the set of lenses
Both cases are rare, so, they may be solved in a not-so-nice way.
I assume that the current situation may turn out as the lesser evil.
But there is always hope.
Tschö,
Torsten.
--
Torsten
not be a problem.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
--
Dive into the World of Parallel Programming
the EXIF data is ambiguous.
Besides, it is already possible to locally add lens entries with a
lens model name like (123).
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
contains only calibration data for this lens with cropfactor
2.0, but you need 1.0.
Please upload a sample image at
http://wilson.bronger.org/calibration according to the instructions
there.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
the model name), there were
different aspect ratios but the same crop factor. Then, the same
camera and lens model can be used for all aspect ratios.
(This is certainly something to re-visit for the next database
overhaul ...)
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron
code
and check the features you mentioned.
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
or http://bronger-jmp.appspot.com
--
Dive
contribute
some. I think you have the best knowledge about the really
critical cases.
I fixed test_modifier. It (rightfully) fails now, because the
centre pixel (x=y=0) sometimes is passed to atan2, and atan2(0,0) is
NaN.
I will look for a fix and further tests later.
Tschö,
Torsten.
--
Torsten
M.14-42mm F3.5-5.6 II R/model
I think this camera and lens are already in Lensfun, see
http://wilson.bronger.org/lensfun_coverage.html. Or is there a
difference between the ED and non-ED version?
Tschö,
Torsten.
--
Torsten BrongerJabber ID: torsten.bron...@jabber.rwth-aachen.de
Hallöchen!
Jan Wolter writes:
[...]
Does anyone has the same problem? Or can reproduce it with my raw
file, which you can download here:
https://www.dropbox.com/s/oa717wk8w7vkgmy/P7057624.ORF
I cannot reproduce it with Darktable. Maybe a Digikam problem?
Tschö,
Torsten.
--
Torsten
All your assumptions are correct. Note that Ru is measured in the
original image (taken by the camera), whereas Rd is measured in the
destination picture (which is supposed to be undistorted).
--
Put Bad Developers to
My camera gives also a wrong focal distance ... I think it is also 0.
Maybe it is darktable bahaviour or that of the EXIF library.
Unfortunately, only a few cameras return the focal distance. And even
for them, only a few lenses do.
If vignetting has been already corrected in the camera, the remaining
vignette cannot be reliably corrected. Vignetting correction *must*
work on *linear* sensor data.
That said, unless vignetting is not over-corrected, everything is
fine. The human eye cannot see slightly under-corrected
GoPro hero in connection with LensFun means that somebody takes test
pictures and makes the calibration. The result of the calibration is
then incorporated into LensFun's database. See
http://wilson.bronger.org/calibration for futher information.
The 1.8 is approx. sqrt(1.5**2 + 1**2), i.e. half-diagonal in
normalised coordinates. And half-height is 12mm, and this is the
factor between normalised coordinates and real-world coordinates since
half-height is 1 in normalised coordinates by definition. Thus, the
half-diagonal of the sensor is
66 matches
Mail list logo
