Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Old post, but I have also found the DxO website, read all the information about their software and I must say it sounds impressive. I will wait until they come out with the 350D update before I download the trial version, but was wondering if anyone uses it and how well does it work? Any information would be appreciated.anyone use this? how is it?
--
Thanks for posting this info Bob, that was exactly the kind of input I was looking for.I use DxO with my 300D and really like the results. I shoot a lot
of art and architecture, including panoramas made up multiple
images stictched together, so correcting optical distortions is
essential. I'm less impressed with the sharpening, which sometimes
over-sharpens at the default setting, in my opinion, but you can
control this. I use it with the 17-40, 50 1.4, and 70-200 f4. If
you have lower end lenses, I expect you will probably be even more
impressed by the improvements.
However, DxO is expensive, and to correct optical distortions and
vignetting, you can also use PTLens (stand alone app or photoshop
plugin), which is free: http://epaperpress.com/ptlens/
One difference is that PTLens' distortion correction is done
assuming the lens is focused at infinity. Distortion changes at
close distances, so it will not be perfect in this case. DxO does
take the distance of the subject into account, and when this info
is included in the EXIF, it does all this automatically, which is
great. BUT, Canon appears to have decided to prevent such
automation by not including distance data in the EXIFs written by
their recent cameras. See this thread:
http://forums.dpreview.com/forums/read.asp?forum=1031&message=12982543
In this case, the approximate distance of the subject needs to be
entered in DXO for each image in order to get the best results,
which is tiresome. You can use a default setting of infinity for
all images, which is exactly what PTLens does.
I don't know whether the 350D includes distance data in EXIFs, but
my guess is that it doesn't.
Tried Irfanview and was unable to get it to show exif info in crw and cr2 files, even after downloading all the plug-ins.You can check it with the free Irfanview viewer.
http://www.irfanview.com/
Along with the app, make sure you install the plugin that allows it
to read EXIF data. Then open an image that is straight from the
camera (not post processed), select image> information, click on
EXIF info, then scroll down to the maker notes section and look for
subject distance. The value appears in mm in 300D images.
--Also be sure you are using a lens that supplies distance data. A
list of lenses that do and don't is here (although it doesn't seem
to include some of the lastest canon lenses):
http://photonotes.org/articles/eos-flash/#distancedata
Let us know what you find out.
However, DxO is expensive, and to correct optical distortions and
vignetting, you can also use PTLens (stand alone app or photoshop
plugin), which is free: http://epaperpress.com/ptlens/
One difference is that PTLens' distortion correction is done
assuming the lens is focused at infinity. Distortion changes at
close distances, so it will not be perfect in this case. DxO does
take the distance of the subject into account, and when this info
is included in the EXIF, it does all this automatically, which is
great. BUT, Canon appears to have decided to prevent such
automation by not including distance data in the EXIFs written by
their recent cameras. See this thread:
http://forums.dpreview.com/forums/read.asp?forum=1031&message=12982543
In this case, the approximate distance of the subject needs to be
entered in DXO for each image in order to get the best results,
which is tiresome. You can use a default setting of infinity for
all images, which is exactly what PTLens does.
I don't know whether the 350D includes distance data in EXIFs, but
my guess is that it doesn't.
--Hmmm, interesting. I used Ifranview to look at the EXIF on 300D
jpegs, didn't try it with raw files. So the 350D raw files really
include subject distance data? That's really going to annoy 20D
owners who use DxO.
However, I downloaded some of Phil's sample 350D jpegs (at the end
of his review) and for those the subject distance value is always
0, regardless of the subject location. I guess that could because
the lenses he was using don't communicate subject distance,
although I'd be surpised since they are both recent designs, the
EF-S 17-85 IS and 70-300 DO.
Can you shoot some jpegs and see if you get values in the subject
distance field for them?