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

proposal - script shooting hooks

  • 290 Replies
  • 74905 Views
*

Offline reyalp

  • ******
  • 13387
Re: proposal - script shooting hooks
« Reply #120 on: 11 / April / 2015, 14:36:03 »
Advertisements
I think also as start at 2. But I would expect a jump in the log file with the sleep values when it starts or not?
There should be a drop in the sleep time, and the raw_ready time should go up.

Quote
I have not looked about this yet, but should not have an effect on RAW data or?
I wouldn't expect it to affect the raw data, but it might affect how the ISO overrides are interpreted, or somehow affect our hooks in the shooting code.

Quote
Everythink is OK. I’m really interested to get it run and what’s going on and why it not happened on S110….
Yes I want to understand too. I think there is probably something different about the G1x, but it would be good to understand it, and fix it if we can.

Quote
Run isoinc with high Tv=8s on G1X. That’s it. Meter makes a jump…
Thanks.

edit:
Very clear. It seems like maybe the "base" ISO changes under some condition.

One thing to try would be a simple script that doesn't use shoot hooks, just like

Code: [Select]
set shutter to 4 seconds
for sv96=550,600
  set sv96
  shoot
The images should show the jump if it's present.

It would also be interesting to know the specific shutter speed it happens at.
« Last Edit: 11 / April / 2015, 14:48:29 by reyalp »
Don't forget what the H stands for.

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: proposal - script shooting hooks
« Reply #121 on: 11 / April / 2015, 18:35:57 »
I can reproduce this on my G1X.

Attached images are from DNG's saved from CHDK, on either side of the meter jump.

First image is at sv96 = 571 (ISO 317), second image os sv96 = 572 (ISO 320).
As you can see the second image is wrong, so this could explain why the rawop meter is wrong - the JPEG and Canon RAW images are fine.

Looks like it could be a bug in the RAW capture on the G1X port - I suspect we may be getting to the RAW buffer too late, and the JPEG conversion process has already started.

I don't have much free time at present; but if I get a chance I'll dig into it more.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

*

Offline lapser

  • *****
  • 1093
Re: proposal - script shooting hooks
« Reply #122 on: 11 / April / 2015, 19:02:35 »
I think this is the same problem with the G1X I referred to here:

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

We never figured out the cause, but it didn't happen in continuous mode on the G1X, as described here:

http://chdk.setepontos.com/index.php?topic=7934.msg105252#msg105252


EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: proposal - script shooting hooks
« Reply #123 on: 11 / April / 2015, 23:37:56 »
I tried moving 'capt_seq_hook_raw_here' to task_DvlpTask as suggested by srsa_4c in another thread; but it made no difference - the DNG image is still wrong once the ISO hits 320.

So I took a closer look at the actual RAW data and compared the good DNG to the bad DNG.

It appears that we are actually getting the RAW data from the sensor in both cases; but the camera seems to be switching to a 12 bit mode when the ISO hits 320.

In the good DNG the image data starts at ~ level 512 as we would expect from the black point.
In the bad DNG the image data doesn't start until ~ level 2048 - 2 stops higher.

If I convert the bad DNG file using dcraw with a black point of 2048 it looks much closer to the good DNG image.

My guess is the camera is switching to a 12 bit ADC.  The Canon raw files still report as 14 bits with a black point of 512. So Canon is doing some sleight of hand later in the image pipeline to convert back to 14 bits.

At this stage we don't have a way to fix this - we assume a fixed black point, not a variable one.
I don't yet know under what circumstances Canon is using this 12 bit mode - so there is no easy way to even know which black point to use.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)


*

Offline reyalp

  • ******
  • 13387
Re: proposal - script shooting hooks
« Reply #124 on: 12 / April / 2015, 01:58:19 »
Thanks for looking into this phil. My impression from c_joerg's post was that exposure of canon jpegs also jumps at the 320 switch, which suggests something triggered by CHDK overrides, rather than just canon doing something funky under the hood with the raw data.

Also noted in http://chdk.setepontos.com/index.php?topic=11081.msg121572#msg121572 at somewhat higher ISO, the value reported by get_prop(props.SV) stops matching the value set with overrides, somewhat similar to what happens if ISO_BASE was wrong.
Don't forget what the H stands for.

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: proposal - script shooting hooks
« Reply #125 on: 12 / April / 2015, 02:46:00 »
Thanks for looking into this phil. My impression from c_joerg's post was that exposure of canon jpegs also jumps at the 320 switch, which suggests something triggered by CHDK overrides, rather than just canon doing something funky under the hood with the raw data.

Also noted in http://chdk.setepontos.com/index.php?topic=11081.msg121572#msg121572 at somewhat higher ISO, the value reported by get_prop(props.SV) stops matching the value set with overrides, somewhat similar to what happens if ISO_BASE was wrong.

I'd lay odds that Canon are doing something funky with the ADC.
Attached are two more images:
- the first is 2 secs @ ISO 400 (Canon manual settings), DNG converted with black point at 2048
- the second is 2 secs @ ISO 800 (CHDK settings), DNG converted with black point at 512

As you can see they look pretty much the same.

When using CHDK ISO overrides, the DNG and JPEG ISO values do not match once the ISO goes over 320. The DNG files always shows 1/2 the selected ISO and has 1/2 the exposure of the JPEG. For some reason the image is being exposed at 1/2 the selected ISO; but the JPEG is then overexposed to compensate. This is why I used ISO 800 in the sample attached image with CHDK settings - the ISO reported in the file is 400.

If I use Canon M mode to manually set Tv >= 1.3 seconds and ISO >= 320 then I get bad DNG files as described earlier.
If I used CHDK overrides to do the same thing, the DNG files are fine regardless of the ISO selected (but I get the exposure issue above).
I have no idea why setting the Tv and Sv values in the script does not behave like setting them in the CHDK overrides menu.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

*

Offline c_joerg

  • *****
  • 1146
Re: proposal - script shooting hooks
« Reply #126 on: 12 / April / 2015, 05:27:05 »
Quote
There should be a drop in the sleep time, and the raw_ready time should go up.

But I don’t see it on the last run….

I make a second run with isoinc and ‘Dark frame subtraction ’ = Off.  Interesting on this run is the peak on sv96=603. Only one peak. On the first run the script crashes here…

Off topic:
I bought I second used G1X. This one has the firmware 100e. My first one has Firmware 101a. I have not found a firmware at canon. Did someone know where the difference is and where I find the newest firmware?
« Last Edit: 12 / April / 2015, 05:44:22 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

  • ******
  • 13387
Re: proposal - script shooting hooks
« Reply #127 on: 12 / April / 2015, 13:27:16 »
Quote
There should be a drop in the sleep time, and the raw_ready time should go up.
But I don’t see it on the last run….
Yes, maybe this camera is different.  Usually the Canon manual says something like "With shutter speeds of 1.3 seconds or slower, there will be a delay before you can shoot again..."
I don't see anything like this in the G1x manual. Anyway, it doesn't look like the problem is related to dark frame.

Quote
I make a second run with isoinc and ‘Dark frame subtraction ’ = Off.  Interesting on this run is the peak on sv96=603. Only one peak. On the first run the script crashes here…
Do you mean the script ends with an error, or the camera shuts down? If the script ends with an error, please check 'last console' and the chdk menu. If you the camera shuts down, get a romlog: http://chdk.wikia.com/wiki/Debugging#Camera_crash_logs_.28romlog.29

Quote
Off topic:
I bought I second used G1X. This one has the firmware 100e. My first one has Firmware 101a. I have not found a firmware at canon. Did someone know where the difference is and where I find the newest firmware?
Usually the differences are very minor. We can't easily tell exactly what changed, but it's usually very little code, or some non-code area like translations strings. Canon doesn't issue a public firmware update unless there are serious bugs, and unless canon issues an an update, there is no way to update the firmware.
Don't forget what the H stands for.


*

Offline c_joerg

  • *****
  • 1146
Re: proposal - script shooting hooks
« Reply #128 on: 12 / April / 2015, 16:31:59 »
Quote
Do you mean the script ends with an error, or the camera shuts down? If the script ends with an error, please check 'last console'

When I came on the first run to the camera, it looks like that the script normally finished (sv from 520 to 640). I notice only that there was a problem, when I copied the data. But then it was too late to watch at last consol.

On the second run I tried to run it under same condition. I put an additional print_screen on the script. But on the second run it did not stopped. May be it has something to do with dark frame subtraction.
Should I run I again with dark frame subtraction again?

I was only wondering on the peak at sv96=603 on the second run that the script finished at 603 on the first run…

Quote
there is no way to update the firmware

so than I can’t run both cams with the same sd card without changes… :(
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

  • *****
  • 1146
Re: proposal - script shooting hooks
« Reply #129 on: 13 / April / 2015, 13:33:05 »
I made a couple of trys with isonic between sv96=590 – 610. The peak at 603 is always reproducible. After 10 runs it stopped ones (Tv=8s, Sv=590). The run was with dark frame subtraktion.
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