supplierdeeply
« previous next »
Pages: 1 ... 3 4 5 6 7 [8] 9 10 11 12 13 ... 30   Go Down

proposal - script shooting hooks

  • 290 Replies
  • 33219 Views
*

Offline c_joerg

  • *****
  • 588
Re: proposal - script shooting hooks
« Reply #70 on: 05 / March / 2015, 13:07:22 »
Advertisements
I made just a short test. Only 28 Pictures. Overexposur 2%, Underexposure 0%. Ok it was a stupid scene. Until picture 16 it goes down to 2% but then it increases again.... Frame rate of the video is only 2 frames/s. The weather is not so good for longer test…..


http://youtu.be/OIwHyH7SVfc
« Last Edit: 05 / March / 2015, 13:11:20 by c_joerg »
Logged
*

Offline reyalp

  • ******
  • 11441
Re: proposal - script shooting hooks
« Reply #71 on: 05 / March / 2015, 16:35:17 »
Quote from: c_joerg on 05 / March / 2015, 06:13:46
Quote
Do you know what aspect ratio the camera was set to for the DNG you sent?


I just checked the JPG from this shoot. It is 4000*3000 so the ratio must be 4:3.
Ok, just to be 100% sure, can you can take a DNG with the jpeg aspect ratio set to 16:9, and check that the DNG has image in the whole 4:3 frame? I'm 99% sure it will but might as well make that 100%

Quote
May be some lines on the Display for 16:9 should be helpful. Is there any option in CHDK to do this?
Do you mean just for framing? CHDK lets you create custom grids. The canon firmware might have a 16:9 grid as well. The script also lets you set the resolution (which usually includes aspect ratio) in the "Image size" setting, so you could compose in 16:9 and have the script to something else. Maybe I misunderstood?

I think your last test shows is expected behavior. Overexp protection only reaches max weight a bit above the "limit" value due to the /120 "slope" factor in calc_ev_change, so the meter being below target partially cancels it out. You could set the limit down to 1%, or increase the Overexp Ev range. I'd suggest the second option, 1/4 stop below over exposure really isn't much.

You could also change the /120 to /100 to make overexposure protection stick closer to the actual limit. I originally put in these factors when histogram precision was limited to 1% increments.
Logged
Don't forget what the H stands for.
*

Offline c_joerg

  • *****
  • 588
Re: proposal - script shooting hooks
« Reply #72 on: 06 / March / 2015, 05:18:35 »
Quote
Do you mean just for framing?

Yes, just for framing.

Ok now I understood a little bit more.  The bar extending from right to left, representing overexposed pixels, represents only the meter area and not the whole frame.

The meter area in the scene is in the shadow. Not there where I want to have. Does it make sense, for scene like this, to have a much larger meter area, may be mostly 90% ? Or, as I suggest before, having a parameter for moving meter area up and down?

A meter area from 10% is something what the cam is doing in spot or partial metering mode. 90-100% is an average metering mode.

Quote
You could also change the /120 to /100 to make overexposure protection stick closer

You mean in the code...

In your test you made Ev shift +1/4. That means you made the whole scene a little bit more brightness?


Logged
*

Offline c_joerg

  • *****
  • 588
Re: proposal - script shooting hooks
« Reply #73 on: 06 / March / 2015, 08:33:20 »
Quote
Ok, just to be 100% sure, can you can take a DNG with the jpeg aspect ratio set to 16:9, and check that the DNG has image in the whole 4:3 frame?

I confirm, the jpeg ratio has no influence to DNG. DNG has always the same size.

 A grid is Ok for 16:9. But I am wondering, there is no 16to9grid. But I think it is easy to make one.

What about native lua calls. They where not enabled.....
« Last Edit: 06 / March / 2015, 09:11:06 by c_joerg »
Logged
*

Offline reyalp

  • ******
  • 11441
Re: proposal - script shooting hooks
« Reply #74 on: 06 / March / 2015, 15:59:09 »
Quote from: c_joerg on 06 / March / 2015, 05:18:35
The bar extending from right to left, representing overexposed pixels, represents only the meter area and not the whole frame.
Correct, the top bar with the tick marks is the meter value.

Quote
The meter area in the scene is in the shadow. Not there where I want to have. Does it make sense, for scene like this, to have a much larger meter area, may be mostly 90% ?
Yes, there is no reason not to. You may need to increase "Meter step", there will be an error when you try to run the script if its too small. The value should be odd so it samples all the colors of the bayer pattern.

Quote
Or, as I suggest before, having a parameter for moving meter area up and down?
Yes, I'd like to make the meter area configurable. A simple position wouldn't be hard to add, I will try to put that in the next version.

Quote
Quote
You could also change the /120 to /100 to make overexposure protection stick closer

You mean in the code...
Yes.

Quote
In your test you made Ev shift +1/4. That means you made the whole scene a little bit more brightness?
This means that the target exposure is slightly brighter than the default "neutral" value.  This will still be modified by the over / under exposure limits. The meter was mostly on sky, and I find the sky looks better if it's a bit brighter than the default "neutral".

Quote
What about native lua calls. They where not enabled.....
Not needed for this script.
Logged
Don't forget what the H stands for.
*

Offline c_joerg

  • *****
  • 588
Re: proposal - script shooting hooks
« Reply #75 on: 07 / March / 2015, 15:00:32 »
Nice sunset. Meter area was on the right place. Interval time was 4s and max Tv also 4s. So the Interval increases when it gets dark. But this doesn’t matter…  unfortunate I have not switch meter area of…. But I will find a way in postprocessing….

http://youtu.be/9suSmmt_d2A
Logged
*

Offline reyalp

  • ******
  • 11441
Re: proposal - script shooting hooks
« Reply #76 on: 08 / March / 2015, 00:34:31 »
Nice sunset.
Quote from: c_joerg on 07 / March / 2015, 15:00:32
Interval time was 4s and max Tv also 4s. So the Interval increases when it gets dark.
Yeah, not too much can be done about that. I've thought about making a setting to keep integer multiples of the interval (if it can't do 4, it does 8, 12 etc) so you could keep the same time scale by duplicating or interpolating frames, but I don't know if it would be worth it.

After trying to do some moon rises, I agree with you that better than 1% precision is needed for over exposure control.
Logged
Don't forget what the H stands for.
*

Offline c_joerg

  • *****
  • 588
Re: proposal - script shooting hooks
« Reply #77 on: 10 / March / 2015, 13:25:52 »
Hello,

Quote
I've thought about making a setting to keep integer multiples of the interval (if it can't do 4, it does 8, 12 etc) so you could keep the same time scale by duplicating or interpolating frames, but I don't know if it would be worth it.

I think it is OK as it is.



There are two thinks which conspicuous me.

1)I run both cameras (S110 and G1X) with ‘Review Off’
In the script ui_display_mode_t=0 so I expect the Display on all the time or?
On S110 the Display is off all the time after I start the script.
On G1X I see the Review picture for the full interval time (in the Test 8s).

2) I set ui_sv_target_mkt=80 in the script. I found this value also in the EXIF data on the G1X. In technical data of the G1X I read that the minimum ISO is 100. Does the G1X works correct with ISO 100?
Logged
*

Offline reyalp

  • ******
  • 11441
Re: proposal - script shooting hooks
« Reply #78 on: 10 / March / 2015, 17:07:25 »
Quote from: c_joerg on 10 / March / 2015, 13:25:52
1)I run both cameras (S110 and G1X) with ‘Review Off’
In the script ui_display_mode_t=0 so I expect the Display on all the time or?
On S110 the Display is off all the time after I start the script.
On G1X I see the Review picture for the full interval time (in the Test 8s).
If display is set to ON, the script should not try to change the display state at all.

Can you tell if the display is actually off (no backlight) or black, with the backlight on?

The difference you see may be a difference in camera behavior. The script acts as if you are holding the shutter half way and clicking full shoot, without letting up on the half.

On my cameras, with review OFF it seems to show the last image between clicks, but I don't know if this is true for every camera or if it depends on some canon settings.

Quote
2) I set ui_sv_target_mkt=80 in the script. I found this value also in the EXIF data on the G1X. In technical data of the G1X I read that the minimum ISO is 100. Does the G1X works correct with ISO 100?
G1X should definitely work with 100, to find out if it works with lower values, you would need to test. You can use the script in http://chdk.setepontos.com/index.php?topic=12165.msg120951#msg120951 to test this.
Logged
Don't forget what the H stands for.
*

Offline c_joerg

  • *****
  • 588
Re: proposal - script shooting hooks
« Reply #79 on: 11 / March / 2015, 03:14:23 »

Quote
Can you tell if the display is actually off (no backlight) or black, with the backlight on?

For a while I made a test with set_backlight(0), set_lcd_display(0) and both together on the S110 and measured the current.  I don’t see any difference on the display form S110 if I do set_backlight(0) or set_lcd_display(0). I booth cases it looks black for me.

Quote
The script acts as if you are holding the shutter half way and clicking full shoot, without letting up on the half.

Yes, that’s the different to my tests…

Quote
On my cameras, with review OFF it seems to show the last image between clicks,

On the G1X as well. I see the last image the full interval. But when I change review to 2s, I see last picture for 2s. On S110 with review OFF I see last picture just flashing….

I will run isoinc.lua…
Logged
Pages: 1 ... 3 4 5 6 7 [8] 9 10 11 12 13 ... 30   Go Up
« previous next »
 

Related Topics