kautsu / 400plus

Automatically exported from code.google.com/p/400plus
0 stars 0 forks source link

Cannot have both EAEB and AEB active #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi. 
I just wanted to use the EAEB Functionality.
What I did in the 400+
Set AEB to +3
Set EAEB FRames to 7
Set EAEB Stephan to +1
What I would have expected:
to get a Series of Pictures with 0 -3 +3 -2 +2 -1 +1 (maybe in a different 
sequence, but these EV values)
What I got: 0 -2 +2 -5 +6 -3  (Yes only 6 pics)
I might have to say, that I tried to do a night scene HDR - because I guess the 
limitation of 30s max has something to do with it. Nevertheless I cannot 
explain the calculation of the EV Value series. 

Original issue reported on code.google.com by Frank.Jo...@googlemail.com on 22 Mar 2011 at 1:38

GoogleCodeExporter commented 9 years ago
The settings for AEB do not affect EAEB: the former is only used for the 
standard camera-controlled AEB, while the later is a new script by 400plus, 
completely independent.

With EAEB set to 7 frames at 1EV separation, I would expect a series of 0 +1 -1 
+2 -2 +3 -3 (in that order, BTW). The 30s limitation could have affected the 
effective exposition of -1, -2, and -3, but I cannot explain your results. I 
would like to reproduce the issue, could you please add more info about the 
camera mode (Av / Tv / ...) and settings (shutter speed, diaphragm, exposure 
compensation, ...) you used?

The short number of shots could be explained if the script was interrupted: 
remember that all scripts are interrupted as soon as the face detector at the 
back of the camera detects something; could this be the case?

Original comment by eduardo....@gmail.com on 22 Mar 2011 at 2:52

GoogleCodeExporter commented 9 years ago
I always Usedom AV Mode and P
Other Sequences I produced: EV/Exposure Time
P-Mode 0/5s -1/2.5 +1/10 +2/20 but then -4/0"3  (EAEB Set to 5 shots) all at 
F4.5
AV-Mode 0/1s -1/0"5 +1/2 +2/4 -4/1/15 (again EAEB Set to 5 shots) all at F8.0
AV-Mode 0/6 -1/3"2 +1/13 +2/25 -4/0"4 +5/30" 4/30 (EAEB Set to 7 shots) all at 
F14

The Short Number of shots could indeed be causae by me as I wasn't aware of the 
fact that the script stops, when the face Detektor detects something.

Original comment by Frank.Jo...@googlemail.com on 23 Mar 2011 at 12:02

GoogleCodeExporter commented 9 years ago
Just to add additional experience:
it just worked perfectly, when trying it in P-Mode, 7 shots, stepping 2/3, 
starting from 0 F14 1/60 with the sequence you described +, -, +, -, +, -. So 
my personal guess would be: it has something to do with using the script in 
combination with long exposures. I will give it another try tomorrow evening. 

Original comment by Frank.Jo...@googlemail.com on 23 Mar 2011 at 6:49

GoogleCodeExporter commented 9 years ago
Could this be related to issue #15? When you review the pictures, is the 
exposure compensation correct, but the exposure time wrong, perhaps? Thanks.

Original comment by eduardo....@gmail.com on 23 Mar 2011 at 6:55

GoogleCodeExporter commented 9 years ago

Original comment by eduardo....@gmail.com on 23 Mar 2011 at 8:38

GoogleCodeExporter commented 9 years ago
I didn't get what exactly you mean? Do you say, that only the displayed values 
are incorrect, but the exposure itself is correct? If so - two displayed values 
gave to be incorrect: exposure time & +-EV value ( which of course is easily 
explainable if one is the mathematical result of the other)

Original comment by Frank.Jo...@googlemail.com on 23 Mar 2011 at 11:09

GoogleCodeExporter commented 9 years ago
No, both the displayed value and the exposure used are wrong, only the exposure 
compensation is right; let me try to explain it with an example:

* The EAEB script starts, sets AV=0 and takes a picture. The camera measures 
the light and decides base exposure time is 5s.

* The EAEB script now sets AV=+1 and takes another picture. The camera measures 
the light again, decides base exposure time is still 5s; so 5s + 1EV = 10s... 
nice!

* The EAEB script now sets AV=-1 and takes another picture; but the light has 
changed, and this time the camera decides that 1s is the correct base exposure; 
so 1s - 1EV = 1/2s... wrong!

When this happens, you will have a series with the correct exposure 
compensation (0, +1, -1), but as the base exposure has changed (5s, 5s, 1s), 
the real exposure (5s, 10s, 1/2s) is wrong. You need to review the pictures, 
and look not only at the exposure time, but the exposure compensation also.

Thanks.

Original comment by eduardo....@gmail.com on 23 Mar 2011 at 11:30

GoogleCodeExporter commented 9 years ago
Hi. 
1. The light situation has not changed while taking the pictures. 
2. Did you notice, that I have already given you the exposure compensation 
_and_ the exposure values? P-Mode 0/5s -1/2.5 +1/10 +2/20 but then -4/0"3  
(EAEB Set to 5 shots) all at F4.5 
Exposure compensation: 0 -1 +1 +2 -4
AV-Mode 0/1s -1/0"5 +1/2 +2/4 -4/1/15 (again EAEB Set to 5 shots) all at F8.0
Exposure compensation: 0 -1 +1 +2 -4
AV-Mode 0/6 -1/3"2 +1/13 +2/25 -4/0"4 +5/30" 4/30 (EAEB Set to 7 shots) all at 
F14
Exposure compensation: 0 -1 +1 +2 -4 +5 +4

Or did I still get you wrong? I will give it another try this evening.
Thanks for the help until now.
Best regards

Original comment by Frank.Jo...@googlemail.com on 24 Mar 2011 at 12:40

GoogleCodeExporter commented 9 years ago
I see from your first post that you had both AEB and EAEB active, is that true?

Sorry I did not notice it before, but I have just realized that they interfere 
with each other; you do not need to use AEB if you are using EAEB, in fact, you 
must deactivate AEB prior to use EAEB. I can confirm this is a bug in 400plus.

Please, try to set AEB to "Off" and try again; thanks for your patience.

Original comment by eduardo....@gmail.com on 24 Mar 2011 at 4:47

GoogleCodeExporter commented 9 years ago
Yes, I had both AEB and EAEB active - I somehow had misunderstood something. I 
had no issues after you explicitly stated that AEB is not needed. So if you 
additionally found an interference/bug I guess that is the reason. Again - I 
will give it a try this evening once it is dark, but unless you hear different 
the problem is solved for me. 

Btw, I have to thank for the patience, because you provide me and others with 
this incredible piece of software and even support it in a more than 
professional way. You have my full respect.

Thanks again.

Original comment by Frank.Jo...@googlemail.com on 24 Mar 2011 at 5:53

GoogleCodeExporter commented 9 years ago
Just to confirm: works perfect with long exposuretimes - if AEB is not active.

Regards
Frank

Original comment by Frank.Jo...@googlemail.com on 24 Mar 2011 at 8:13

GoogleCodeExporter commented 9 years ago
Thanks! Fix in 3, 2, 1, ...

Original comment by eduardo....@gmail.com on 24 Mar 2011 at 11:02

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r206.

Original comment by eduardo....@gmail.com on 24 Mar 2011 at 11:02