proposal - script shooting hooks - page 11 - General Discussion and Assistance - CHDK Forum

proposal - script shooting hooks

  • 290 Replies
  • 77117 Views
*

Offline c_joerg

  • *****
  • 1157
Re: proposal - script shooting hooks
« Reply #100 on: 26 / March / 2015, 04:27:49 »
Advertisements
Hallo reyalp,

i have sometimes problems with the default parameters in your script, when I run the script at the first time on a new installation. Some parameter where random and not default. Can it be that has something to do with the default values of a table?

Code: [Select]
#ui_draw_meter_t=0 " Meter area" {None Corners Box} table
I think tables be actual 1 based or?

https://github.com/c10ud/CHDK/commit/f848302f8ebe02b3c6ec9030671233a3d129d98e
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline reyalp

  • ******
  • 13439
Re: proposal - script shooting hooks
« Reply #101 on: 28 / March / 2015, 16:42:55 »
i have sometimes problems with the default parameters in your script, when I run the script at the first time on a new installation. Some parameter where random and not default.
I have noticed this too and haven't tracked it down.

Quote
Can it be that has something to do with the default values of a table?

Code: [Select]
#ui_draw_meter_t=0 " Meter area" {None Corners Box} table
I think tables be actual 1 based or?
Good idea, but looking back at the posts around the change, I don't think the #param value was changed, only the table values: http://chdk.setepontos.com/index.php?topic=12121.msg119816#msg119816

In the current trunk ,=0 selects "None" and 1 selects "Corners" when you use "Load default param values"

I think the weirdness may happen when the parameter definitions in the script change and you already have saved params, but I'm not completely sure.
Don't forget what the H stands for.

*

Offline c_joerg

  • *****
  • 1157
Re: proposal - script shooting hooks
« Reply #102 on: 28 / March / 2015, 17:50:44 »
Yes only table values are changed. tables begins with 1, arrays with 0.

So when i delete the files under data and start the script, i got random values for ui_draw_meter_t (None, box or corners). I don’t understand why it switch to None when I call "Load default param values".

But when I change ui_draw_meter_t=1, then I got always None at start. Whem I then call "Load default param values" it switches to Corners….

There must be an mismatch…
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline reyalp

  • ******
  • 13439
Re: proposal - script shooting hooks
« Reply #103 on: 28 / March / 2015, 19:29:08 »
So when i delete the files under data and start the script, i got random values for ui_draw_meter_t (None, box or corners). I don’t understand why it switch to None when I call "Load default param values".
Good idea. I did the following
1) Loaded a different script in the script menu
2) Deleted are rawopint* files in data
3) Loaded rawopint

In my current script, I have
Code: [Select]
#ui_display_mode_t=0 "Display" {On Off Blt_Off} table
#ui_draw_meter_t=1 " Meter area" {None Corners Box} table

After loading the script is
Display is Blt_Off
Meter area is None

After I run "Load default param values"
Display is On
Meter area is Corners

edit:
OK, I think I see the problem. It looks like the loaded value is assumed to be 1 based, but the default is stored before that adjustment is made. So both the script and CHDK have a bug.

edit 2:
I've checked in a change that should fix the CHDK part in trunk 4117
« Last Edit: 28 / March / 2015, 21:12:45 by reyalp »
Don't forget what the H stands for.


*

Offline c_joerg

  • *****
  • 1157
Re: proposal - script shooting hooks
« Reply #104 on: 29 / March / 2015, 08:06:21 »
Fantastic, good job, now it works correct…..  :)
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline c_joerg

  • *****
  • 1157
Re: proposal - script shooting hooks
« Reply #105 on: 04 / April / 2015, 10:18:40 »
Hello reyalp,

I made another test with G1X. The same problem as the run before. Its absolute reproducible. The result in the log file looks similar to the run before. The flicker starts around when bv96 gets negative.

The first 18s from the video are made from JPG, the second 18s are made from CHDK DNG files. Flicker around 11s. I never worked with DNG date before, but JPG and DNG data looks similar. The white balance looks a little bit crazy when flicker ends.
So it did not looks like a problem with the RAW buffer or?

http://youtu.be/1C-dMp1UTWs

May be I switch next time noise reduction in the CHDK menu off…
« Last Edit: 04 / April / 2015, 10:30:01 by c_joerg »
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

*

Offline reyalp

  • ******
  • 13439
Re: proposal - script shooting hooks
« Reply #106 on: 04 / April / 2015, 21:10:11 »
The first 18s from the video are made from JPG, the second 18s are made from CHDK DNG files. Flicker around 11s. I never worked with DNG date before, but JPG and DNG data looks similar. The white balance looks a little bit crazy when flicker ends.
So it did not looks like a problem with the RAW buffer or?
Yes, it looks like there's valid image data in all the DNGs, so it's not a case of having a completely wrong raw buffer or something like that.

The pattern is definitely the same as the last one.

I don't have any good ideas at the moment, maybe it's a case of the script hooks interfering with normal canon code like I think is happening on D10.

The next version of the script will have some parameters to adjust the sleep and yield settings that affect this on D10. I have a couple more things to sort out before I upload it.

If you want to try this manually, you can put sleep(10) just before the line hook_raw.continue()

Quote
May be I switch next time noise reduction in the CHDK menu off…
The only noise reduce option CHDK has is dark frame subtraction. That's usually triggered by shutter speed, where your problem happens after the shutter has already been bottomed out for a while. I don't  have any better ideas though...

One other thing to try might be to set the shutter speed limit different. If you allow it to go to say 2 sec, does the flicker start at the same ISO?
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 13439
Re: proposal - script shooting hooks
« Reply #107 on: 04 / April / 2015, 21:30:39 »
Something I missed before: In the logs from both the G1x runs with flicker there are messages like

sv 619 != cam 715

This means the script tried to set ISO ~456 but the value it read back in the next exposure was ~898

This happens after the flickering has stopped  :-[

The problem appears to occur when the script requests sv96 > 571 (ISO ~317). It seems like somewhere between 571 and 574, the effective change in ISO is much larger than expected, although the set value is still read back... the fact that this doesn't happen with the isoinc script suggests this isn't just a generic issue with ISO overrides on this cam.

edit:
This explains the bouncing behavior: Because the going over 571 causes a big jump in exposure, the next iterations try to compensate, dropping below the threshold. Then it's under exposed, so it pushes over the threshold again. Eventually, even the compensated value is above the threshold and it stops flapping.
« Last Edit: 04 / April / 2015, 21:34:19 by reyalp »
Don't forget what the H stands for.


*

Offline lapser

  • *****
  • 1093
Re: proposal - script shooting hooks
« Reply #108 on: 04 / April / 2015, 23:53:31 »
Since you seem to be having ISO problems, why don't you try a test where you set the ISO using the propcase method I described here:

http://chdk.setepontos.com/index.php?topic=11081.msg121063#msg121063

Also, I suspect there are some timing related issues with having the script control the interval for every shot. Using my set_shot_interval(i) method, the pre-shot delay always ends after a msleep(10). This may be important. The script could still control the actual interval for each shot by setting it very long, and re-setting it to trigger the end of the delay. I've done that with my code for external sync applications.

I also found that it sometimes take a very long time to write a single line of the log file when you're writing a lot of picture data (raw files especially). Set_shot_interval() can still trigger the next shot on time, even when the script is still hung up writing the log file.

The other advantage of set_shot_interval() is that it makes time lapse scripts simpler.
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

*

Offline c_joerg

  • *****
  • 1157
Re: proposal - script shooting hooks
« Reply #109 on: 05 / April / 2015, 02:56:37 »
Quote
If you allow it to go to say 2 sec, does the flicker start at the same ISO?

Yes, thought about the same, would be interesting to see if every think moves…
And also running S110 with the same parameter…..

Quote
The only noise reduce option CHDK has is dark frame subtraction.

When I make pictures with 4s the interval goes to around 10s. This is a noise reduction which the cams (S110 and G1X) makes. There is nothing on the cam, to switch it off. I thought, I can switch it off with CHDK…

Quote
I also found that it sometimes take a very long time to write a single line of the log file when you're writing a lot of picture data

I have always problems with my own simple interval script and log files, when I using the fast camera bracketing function + RAW. On every second run the log function brakes…

Quote
why don't you try a test where you set the ISO using the propcase method

Would this help? With my knowledge right now I have not really understood what’s going on…  :)

I have seen, you change the scale in histo:range. For the moon  ;)

Could you this also do in shot_histogram.c for get_histo_range?
This is what I using in my simple script. It was already suggest here

http://chdk.setepontos.com/index.php?topic=8997.20

but I have not understood, why it was not realized. I would be a really improvement... 



M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

 

Related Topics