proposal - script shooting hooks - page 15 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 ... 10 11 12 13 14 [15] 16 17 18 19 20 ... 30   Go Down

proposal - script shooting hooks

  • 290 Replies
  • 106715 Views
*

Offline c_joerg

  • *****
  • 1248
Re: proposal - script shooting hooks
« Reply #140 on: 17 / April / 2015, 16:58:18 »
Advertisements
Quote
I should have more time again after next week.

It’s OK. Don’t hurry…

As you say, the release didn’t fix everything in rawopint, there is a jump at around 26s….

http://youtu.be/1P9fXrJMnQE
Logged
M100 100a, M3 121a, 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

  • *****
  • 1248
Re: proposal - script shooting hooks
« Reply #141 on: 18 / April / 2015, 08:45:19 »
Just for completeness.

The curves didn’t look so bad expect the peek around sv96=603.
The run was with dark frame subtraktion
There are two thinks which I was wondering:

1) After the peek the speed of the video increases (it looks like factor 2). But tv has not changed. Can it be that cam switched of dark frame subtraction?
2) After the peek the brightness looks to high. But meter96 shows a different direction.

Logged
M100 100a, M3 121a, 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 jmac698

  • ***
  • 138
Re: proposal - script shooting hooks
« Reply #142 on: 28 / April / 2015, 03:28:39 »
Hi,

I had another use for this.  I have trouble taking pictures of flowers with very saturated colours, they can be overexposed while the rest isn't, and have less shading detail.

My idea is to take 3 pictures but exposure for R,G, B separately.  Then combine the 3 pics into a normal, but fake  higher-bit DNG file.  For example boost Blue by 2 stops, then shift it down 2 bits, and make a fake 16bit DNG from a 14bit sensor.  This is like a fake floating point. It would give better accuracy in colour balance and more detail with saturated subjects. You might wonder about mismatched highlights - this can be fixed with usual highlight recovery, but there's a slight problem.  You'd have to do normal highlight recovery on equalized channels first then put them back to proper colour balance, if you follow.

For now, make sure there's no overexposure in each colour.  Can this be done?  I don't know to construct a fake DNG in this way.

In fact for flowers, I'd like to just expose for (say) red, I don't even care if background has highlights since it's not the subject.

For another idea, I'd like to analyze raw buffer without saving between pictures. At first for noise analysis, but also for photogrammatry or looking for scene change etc.  Hopefully it's much faster when I don't need to save the buffer.
« Last Edit: 28 / April / 2015, 03:35:54 by jmac698 »
Logged
*

Offline reyalp

  • ******
  • 14079
Re: proposal - script shooting hooks
« Reply #143 on: 28 / April / 2015, 16:34:11 »
Quote from: jmac698 on 28 / April / 2015, 03:28:39
For now, make sure there's no overexposure in each colour.  Can this be done?  I don't know to construct a fake DNG in this way.
The meter and histogram code can be used to measure individual channels, by using the CFA offsets and appropriate step size. There are examples of this in the drtest script.

As far as constructing a combined DNG, you might have to write some software to do that. Aside from combining the actual data, the color matrix would be need to be different.

I don't have much opinion about how viable the overall concept is. If you have to heavily over expose one channel to get "correct" exposure on another, you may run into problems with blooming.
Quote
For another idea, I'd like to analyze raw buffer without saving between pictures. At first for noise analysis, but also for photogrammatry or looking for scene change etc.  Hopefully it's much faster when I don't need to save the buffer.
You can analyze the raw buffer without saving raw. You can't currently prevent jpeg saving, but it is a relatively small part of the total shooting time. We do have the ability to prevent jpeg save on some cameras for USB remote shoot but it currently isn't accessible from script, and because it only affects the final write to SD card, it doesn't save a lot of time.

Analyzing the full raw buffer is quite slow (several seconds) even in C code, if you do it pixel by pixel in Lua, it's even slower. If your analysis only needs to look at a small area or sample a small fraction of the pixels, it can be fairly quick (tens of milliseconds or less.)
Logged
Don't forget what the H stands for.
*

Offline c_joerg

  • *****
  • 1248
Re: proposal - script shooting hooks
« Reply #144 on: 04 / May / 2015, 02:33:23 »
I think, revision 4153 makes it even worse.
I got now flicker also with ISO200 (on the end of the video), not much, but this did not happens before…

http://youtu.be/BuMPmHyrO4s




« Last Edit: 04 / May / 2015, 02:35:19 by c_joerg »
Logged
M100 100a, M3 121a, 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

  • *****
  • 1248
Re: proposal - script shooting hooks
« Reply #145 on: 04 / May / 2015, 02:34:36 »
And the log file...
Logged
M100 100a, M3 121a, 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

  • *****
  • 1248
Re: proposal - script shooting hooks
« Reply #146 on: 13 / May / 2015, 14:21:34 »
I am still really happy with the script rawopint. It controls everything very good. Here is an nice example made with S110:

http://youtu.be/AP2_ZMTQREA

I’m still thinking, revision r4153 makes it worse with G1X. I get now still flicker also with lower ISO values. For me, the best solution right now, is to go back to revision r4138.
Logged
M100 100a, M3 121a, 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

  • ******
  • 14079
Re: proposal - script shooting hooks
« Reply #147 on: 13 / May / 2015, 23:28:07 »
Quote from: c_joerg on 13 / May / 2015, 14:21:34
Here is an nice example made with S110:
That looks like it worked quite well.
Quote
I’m still thinking, revision r4153 makes it worse with G1X. I get now still flicker also with lower ISO values. For me, the best solution right now, is to go back to revision r4138.
It definitely won't work right until the script and rawop code is updated to deal with it. I should hopefully have some time to work on this again soon. (yeah, I know I've said that before  :-[)

From a quick look, I think the flicker you see in post #144 is a different issue, although I'm not sure exactly what it is. Philmoz change shouldn't have any effect outside of when the black level jumps, which I don't think is happening there.
Logged
Don't forget what the H stands for.
*

Offline c_joerg

  • *****
  • 1248
Re: proposal - script shooting hooks
« Reply #148 on: 14 / May / 2015, 04:30:09 »
Quote
I should hopefully have some time to work on this again soon

Don’t get on pressure from my side …

Quote
From a quick look, I think the flicker you see in post #144 is a different issue, although I'm not sure exactly what it is.

It looks definitely different as the thing before. So r4153 should not have an effect on G1X with Tv=4s and ISO200. It is not much flicker which can be reduced with a deflicker filter in VirtulDub.
Logged
M100 100a, M3 121a, 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

  • *****
  • 1248
Re: proposal - script shooting hooks
« Reply #149 on: 15 / May / 2015, 05:37:44 »
Quote
but in my testing on the cameras that I have, the "hold half press / click full press" approach gives very similar performance to continuous mode

This is one issue where I still thinking about. I can’t agree this for S110 and G1X.
May be it is a misunderstanding from my side.
Running rawopint with minimum interval time gives me an interval from around 1.3s.
I got the same result, with a simple script like this:

Code: [Select]
loop_stop = false
press("shoot_half")
repeat
 sleep(10)
until get_shooting() == true

repeat

count = get_exp_count()
press("shoot_full_only")
sleep(200)
release("shoot_full_only")
repeat
  sleep(10)
until get_exp_count() ~= count
 
if is_pressed "menu" then
    print("Stop because MENU Click")
    loop_stop = true
end

until loop_stop

A script in continues mode like iv_turbo.lua gives me on both cameras a interval from around 0.5s
Logged
M100 100a, M3 121a, 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
Pages: 1 ... 10 11 12 13 14 [15] 16 17 18 19 20 ... 30   Go Up
« previous next »
 

Related Topics