I just run drtest.lua from r4158. I got a printf error, when I start it. Then I run isobase.lua and after drtest.lua again. Then it looks like, that it works. I think, I have seen it also on the old version.
Oops. This happens if the camera is not in record and P mode when you start the script. Fixed in svn 4159.
edit:
The CSV you attached is OK, but the results are a bit strange.
Was the subject a neutral, uniform scene? The neutral shot (row seven, exposure #6) seems to be as expected, but the others are unexpected. There should be ~96 difference between each shot in the m96 column, and the wl% and bl% should only be significant in the first and last shots.
The jump is not on sv96=603. The jump (peak) is on the first sv96 value, which is >= 603. So on the last run on sv96=605. When I run isoinc before, the jump was exactly on sv96=603. 605 were on isoinc OK.
What I was trying to say is that whatever crazy thing happens is
camera firmware behavior, and philmoz change has no impact on that.
In addition to unknown factors within the Canon code, timing of the overrides in CHDK may have some influence.
Does it help, to implement the continuous mode in isoinc? Then we could compare the runs under same conditions.
That's a good idea, I'll do that when I have some time. (edit: done
http://chdk.setepontos.com/index.php?topic=12165.msg122547#msg122547)
I don't think there is a need to run drtest under different conditions, at least not yet.
What is different, when lapser use continuous mode?
http://chdk.setepontos.com/index.php?topic=7934.msg105252#msg105252
I don't know, lapser used his own custom code.
