Don't get lens distortion correction to work...

[Michael Engelen]

Hi,

eagerly wanting to try out the new lens distortion correction (thanks for that, Chris!) I cannot get it to work. The conversion process ends with an "Error converting raw file". The conversion doesn't work with any file. Any idea what I do wrong? :confused:

OS: Win2K SP4, Win XP SPx
Canon 1D Mark II or Canon 20D, several lenses
I did the lens distortion setup for the equipment that I use.

Greetings,
Michael

[Chris Breeze]

Please can you run the BBUtil app in the BBPro installation folder after you get the error and press the "Check version information...". This will show whether it is a problem with different versions of the graphics library.

[Michael Engelen]

Please can you run the BBUtil app in the BBPro installation folder after you get the error and press the "Check version information...". This will show whether it is a problem with different versions of the graphics library.

BBUtil Version check results:
BBPro version 1.3.0.0

Graphics Library Version
-----------------------
Registered version: 2.11
File version: 2.1.1.0
Version in BBPro folder: 2.1.1.0
Registered version of PolyImagePro.dll is OK

Seems to be ok.

Michael

[Chris Breeze]

Thanks for running BButil. It shows that the problem isn't related to different versions of the graphics library and must be caused by something else. So far there have only been about half a dozen reports of problems with lens distortion and I haven't been able to reproduce the problems on my test systems. I have recently found a problem with the software protection system used in DSLR Remote Pro which caused it to crash occasionally and it's possible the same thing is happening with BBPro on some systems. I will build a test version with slightly different software protection settings to see if this fixes the problem.

[Michael Engelen]

Chris,

is there anything new about the problems with the lens distortion?

Michael

[Chris Breeze]

I still can't reproduce the problem on any of my test systems and so I have been sending debug versions to a number of users who can reproduce it. It's a fairly time consuming process to try to isolate the problem but I hope to have a fix some time next week.

[Ursula]

Hello,

I am using BBPro V1.3 with Windows XP SP2 (German version) and have the same problem. I only selected the lens I was using with my EOS20D. When I start the convertion it seam that the convertion works fine and it seams to me that when BBPro tries to write the file the error occurs. Because if I disable the postprocessing the conversion take the same time and after the conversion is finished the writing file message appears.
I run the BBUtil and get the same result as Michael.
Crossing my fingers that Chris finds a solution

[loenne]

...
The conversion process ends with an "Error converting raw file". The conversion doesn't work with any file
...


Same behaviour & error message on my PC (xp sp2) and on the notebook (xp prof) as well.
Greetings
Volker

[WiechersG]

:mad:

But first of all: BBpro 1.3 is running fine and gives me great results for my 5D!!!

Thanks,
Gerd

[Chris Breeze]

I have located the problem and will have a fix for it later this week. The problem only occurs in countries where a comma is used as the decimal point e.g. PI = 3,14. This was preventing BBPro from reading the lens profiles which use a period/fullstop for the decimal point.

[loenne]

Hello Chris,
this is great news, thanks alot!
gretings
Volker

BTW: after changing the decimal points into commas in the relevant PTLens ".txt" file, the lens correction works fine for me ;)

[WiechersG]

I have located the problem and will have a fix for it later this week. The problem only occurs in countries where a comma is used as the decimal point e.g. PI = 3,14. This was preventing BBPro from reading the lens profiles which use a period/fullstop for the decimal point.

Great news!
Looking forward to the fix.

Thx in advance,
Gerd

[Michael Engelen]

Chris,

that's great news. Some things are somewhat easy to fix (or at least to find a workaround) but really hard to locate. I'm looking forward to the final version. Thanks.

Greetings,
Michael

[WiechersG]

I have located the problem and will have a fix for it later this week. The problem only occurs in countries where a comma is used as the decimal point e.g. PI = 3,14. This was preventing BBPro from reading the lens profiles which use a period/fullstop for the decimal point.

Hi Chris,
when can we expect the fix for Germany?

Best regards,
Gerd

[Chris Breeze]

I hope to release an update later this week.

[WiechersG]

I hope to release an update later this week.

Thx again!

Best regards
Gerd

[Ursula]

Hello Chris,
this is great news, thanks alot!
gretings
Volker

BTW: after changing the decimal points into commas in the relevant PTLens ".txt" file, the lens correction works fine for me ;)

After I did the changes it works fine. Thank you very much for the idea

[Michael Engelen]

Chris,

thanks for the new version--the problem is that it doesn't work.
Win XP SPx: Error converting raw file
Win 2000 SP4: Strange looking picture

So what now?

Greetings,
Michael

[Chris Breeze]

I have withdrawn BBPro v1.3.1 while I investigate the problem. It appears to be caused by one of the libraries used by BBPro and so I may not be able to do anything about it until next week.

[Michael Engelen]

Thanks, Chris

[Chris Breeze]

The problem was caused by a new version of the graphics library. I have built a new release of BBPro using the previous version of the graphics library and this appears to have fixed the problem. You can download this from: http://www.breezesys.com/downloads/bbpro132RC1.exe
Please can you try this version and if I don't get any reports of problems I will release it properly at the end of the week.

[WiechersG]

The problem was caused by a new version of the graphics library. I have built a new release of BBPro using the previous version of the graphics library and this appears to have fixed the problem. You can download this from: http://www.breezesys.com/downloads/bbpro132RC1.exe
Please can you try this version and if I don't get any reports of problems I will release it properly at the end of the week.

Hi Chris,
with my local settings in Germany it is running fine!

Thx,
Gerd

[loenne]

Hi Chris,
with my local settings in Germany it is running fine!

Thx,
Gerd
Same with my system (checked jpg, png,tiff with files from PTlens)!
(A minor issue: BBP still crashes during browsing if there are these strange empty "0-byte" files in the directory. After deletion of these zombies, everything is fine.)

BTW I like the persistant magnifier function. :)

greetings
Volker

[TomPro]

Chris,

Worked fine converting an EOS350D CR2 file using Norwegian settings.

regards,
Tom

[Michael Engelen]

Chris,

first of all the good news: the lens distortion works also with my setup :)
But there is the problem that my 20D files are not treated correctly (the problem occured for the first time with V1.3.1) :( . The image serial number is wrong (e.g. 7507 would end up as 5459). I found that out when batch renaming files with a custom style that involves the image serial number (%n_%v_%f%r). Things are ok for my 1D files.
Any ideas?

Michael

[Chris Breeze]

Same with my system (checked jpg, png,tiff with files from PTlens)!
(A minor issue: BBP still crashes during browsing if there are these strange empty "0-byte" files in the directory. After deletion of these zombies, everything is fine.)

BTW I like the persistant magnifier function. :)

greetings
Volker

Could you let me know what empty file types cause BBPro to crash? I've identified a problem with 0 length PNG files and will fix this in the next update.

[Chris Breeze]

Chris,

first of all the good news: the lens distortion works also with my setup :)
But there is the problem that my 20D files are not treated correctly (the problem occured for the first time with V1.3.1) :( . The image serial number is wrong (e.g. 7507 would end up as 5459). I found that out when batch renaming files with a custom style that involves the image serial number (%n_%v_%f%r). Things are ok for my 1D files.
Any ideas?

Michael

I've located where the folder and image numbers are stored in the shooting data for 20D and 350D images but wasn't quite reading it properly in BBPro v1.3.1. I've worked out what was wrong and will fix it in the next update.

[loenne]

Could you let me know what empty file types cause BBPro to crash? I've identified a problem with 0 length PNG files and will fix this in the next update.
I switched back to V1.3.1 in order to produce these zombies. Only empty "png" files caused the crash - "jpg" and "tif" simply triggered an error msg (which is correct) when selecting such file and bbp did not crash.
greetings
Volker

[Michael Engelen]

I've located where the folder and image numbers are stored in the shooting data for 20D and 350D images but wasn't quite reading it properly in BBPro v1.3.1. I've worked out what was wrong and will fix it in the next update.

:) Thanks, Chris. I'll be happy if V1.3.x works the way you wanted it.

For me the best new feature still is the lens distortion correction with the PTlens data. I made a little helping tool in Excel to calculate the data from 1.6 to 1.3 for lenses where data is only available for 1.6 crop factor cameras (like for the 24-85mm lens). That completes my collection of conversion tools for now.

[Chris Breeze]

:) Thanks, Chris. I'll be happy if V1.3.x works the way you wanted it.

For me the best new feature still is the lens distortion correction with the PTlens data. I made a little helping tool in Excel to calculate the data from 1.6 to 1.3 for lenses where data is only available for 1.6 crop factor cameras (like for the 24-85mm lens). That completes my collection of conversion tools for now.

What formula are you using to calculate the 1.3 data from 1.6 crop factor data? BBPro currently calculates 1.3 data from 1.0 data and 1.6 data from 1.3 data if lens information is only defined for a larger crop factor.

[Michael Engelen]

What formula are you using to calculate the 1.3 data from 1.6 crop factor data? BBPro currently calculates 1.3 data from 1.0 data and 1.6 data from 1.3 data if lens information is only defined for a larger crop factor.

Chris,
I used the formula that is explained in the documentation (3rd grade polynomial). Of course it is an extrapolation to get from 1.6 to 1.3 --but it is good enough and works for me.

Here is what my little Excel-sheet uses (example: 100-400L @400mm):
Factor old: 1,6
Factor new: 1,3
a: -0,000338
b: 0,003752
c: 0,000000
d: 0,996586

F=old/new: 1,230769231
Z = a*F^3 + b * F^2 + c*F + d: 1,001639349

a' = a*F^3 / Z: -0,000629122
b' = b*F^2 / Z: 0,005674201
c' = c*F / Z: 0
d' = d / Z: 0,994954922

Example: 100-400L
focal length a' b' c'
100 0,002878 -0,005376 0,000000
135 0,000878 -0,000618 0,000000
150 0,000410 0,001031 0,000000
200 -0,000205 0,002906 0,000000
250 0,002471 -0,001691 0,000000
300 -0,003301 0,008891 0,000000
350 0,001343 0,001017 0,000000
400 -0,000629 0,005674 0,000000

Michael

[Michael Engelen]

Chris,

I worked all evening with the latest version and found it to be ok. Thanks :)

Michael