G1X + others ISO override issues (was Re: rawopint.lua) - page 6 - General Discussion and Assistance - CHDK Forum supplierdeeply
« previous next »
Pages: 1 2 3 4 5 [6] 7   Go Down

G1X + others ISO override issues (was Re: rawopint.lua)

  • 65 Replies
  • 21187 Views
*

Offline c_joerg

  • *****
  • 908
Re: G1X + others ISO override issues (was Re: rawopint.lua)
« Reply #50 on: 19 / July / 2017, 15:24:44 »
Advertisements
Quote from: srsa_4c on 19 / July / 2017, 13:10:26
In one of the links reyalp linked above, a similar problem was triggered by people (faces) in front of the camera. Is there a chance you were shooting a scene with people when the camera crashed?

I have read reyalp's links. With the crash were definitely no faces in the game. The camera was focused on my monitor.

I just tested it again with the faces of my family. There was no crash.
Logged
M100 100a, M3 101a, 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

  • *****
  • 908
Re: G1X + others ISO override issues (was Re: rawopint.lua)
« Reply #51 on: 08 / August / 2017, 14:21:30 »
Quote from: c_joerg on 16 / July / 2017, 06:24:53
I don’t have access to my SX50 right now so I can’t check SX50 right now.
I got my SX50 back….
Quote from: philmoz on 08 / July / 2017, 04:01:25
Test version for SX50HS 1.00c.
I checked it and works fine. 😊
Quote from: philmoz on 07 / July / 2017, 20:30:49
Fix for all G1X versions is now in SVN revision 4853.
What about S110 and SX50?

My G1x works still without problems….
Logged
M100 100a, M3 101a, 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

  • *****
  • 908
Re: G1X + others ISO override issues (was Re: rawopint.lua)
« Reply #52 on: 18 / October / 2017, 01:55:37 »
Quote from: c_joerg on 08 / August / 2017, 14:21:30
Quote from: philmoz on 07 / July / 2017, 20:30:49
Fix for all G1X versions is now in SVN revision 4853.
What about S110 and SX50?

How is status for S110 and SX50? Is there any reason why it couldn’t checked in?
From my side it works fine…
Logged
M100 100a, M3 101a, 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 lapser

  • *****
  • 1093
Re: G1X + others ISO override issues (was Re: rawopint.lua)
« Reply #53 on: 18 / October / 2017, 13:15:05 »
The way I understand it, Phil was able to bypass ISO "cooking" but not the black level change, is that right? Has anyone checked to see if a sudden black level change when crossing the ISO threshold (without "cooking") produces a brightness jump?

I'd like to try out the high ISO noise reduction in continuous mode. If I set my first photo at > ISO 400, does that trigger it when the script sets ISO above 400?

I want to try out the high ISO noise reduction, especially in night shots. I've noticed that there is more noise in the corners of my G1X Milky Way time lapses compared to the M3. The brightness of the corners is boosted digitally in Lightroom to compensate for lens vignetting. So a black level of 2047 would show less digital noise than 511, especially in the corners.

Is there any way to turn the "cooking" back on from a script? Is an "uncooked" ISO 1600 shot the same as a "cooked" ISO 3200 shot? I assume the black level is 2047 in both?
Logged
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos
*

Offline c_joerg

  • *****
  • 908
Re: G1X + others ISO override issues (was Re: rawopint.lua)
« Reply #54 on: 19 / October / 2017, 06:21:32 »
Quote from: lapser on 18 / October / 2017, 13:15:05
Has anyone checked to see if a sudden black level change when crossing the ISO threshold (without "cooking") produces a brightness jump?

I can’t see on the rawopint log file, if the black level changes. But I’m not sure if  rawopint will log the changes while running or only in the init part. I can't see brightness jumps.
May be I still have the RAW data and can check it with EXIFTOOL.
Values from G1x RAW Data

Code: [Select]
Per Channel Black Level         : 512 512 512 512

Quote from: lapser on 18 / October / 2017, 13:15:05
So a black level of 2047 would show less digital noise than 511, especially in the corners.

Not sure what the cam is doing in the case? Just changing the AD Converter from 14 to 12 Bits?
May be you can replace the black level in the RAW Data with EXIFTOOL…

In the manual of EOS M5 is written, that the cam changes resolution from 14 to 12 Bits in continuous mode…

Logged
M100 100a, M3 101a, 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 philmoz

  • *****
  • 3155
    • Photos
Re: G1X + others ISO override issues (was Re: rawopint.lua)
« Reply #55 on: 20 / October / 2017, 04:40:44 »
Quote from: c_joerg on 18 / October / 2017, 01:55:37
Quote from: c_joerg on 08 / August / 2017, 14:21:30
Quote from: philmoz on 07 / July / 2017, 20:30:49
Fix for all G1X versions is now in SVN revision 4853.
What about S110 and SX50?

How is status for S110 and SX50? Is there any reason why it couldn’t checked in?
From my side it works fine…


Added in SVN revision 4922.


Phil.
Logged
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)
*

Offline c_joerg

  • *****
  • 908
Re: G1X + others ISO override issues (was Re: rawopint.lua)
« Reply #56 on: 20 / October / 2017, 14:23:10 »
Quote from: philmoz on 20 / October / 2017, 04:40:44
Added in SVN revision 4922.

Thanks  :)
Logged
M100 100a, M3 101a, 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

  • *****
  • 908
Re: G1X + others ISO override issues (was Re: rawopint.lua)
« Reply #57 on: 08 / January / 2018, 04:31:26 »
It's been some time and I cannot remember if I've ever tested it.
I get the following error in RAWOPINT in QUICK mode:

Code: [Select]
411 != cam 412
I discovered it now by accident because I usually only use the cont mode.
Logged
M100 100a, M3 101a, 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

  • *****
  • 908
Re: G1X + others ISO override issues (was Re: rawopint.lua)
« Reply #58 on: 27 / April / 2018, 08:19:29 »
Quote from: c_joerg on 08 / January / 2018, 04:31:26
It's been some time and I cannot remember if I've ever tested it.
I get the following error in RAWOPINT in QUICK mode:

Code: [Select]
411 != cam 412
I discovered it now by accident because I usually only use the cont mode.


I would like to bring this article forward once. My SX50 also has the problem in Quick Mode (staying in Half Press) when using RAWOPINT since these updates here.
Code: [Select]
sv 411! = cam 412Unfortunately, I only checked the continuous mode here.
Logged
M100 100a, M3 101a, 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

  • ******
  • 12537
Re: G1X + others ISO override issues (was Re: rawopint.lua)
« Reply #59 on: 28 / April / 2018, 00:09:28 »
Quote from: c_joerg on 27 / April / 2018, 08:19:29
Code: [Select]
sv 411! = cam 412Unfortunately, I only checked the continuous mode here.
This is strange. It seems like a rounding error, but I don't see why it would be different in quick vs cont. CHDK override shouldn't behave differently, but maybe the camera recalculates the propcase SV values in quick.

It would be interesting to know if it keeps happening when the script increases ISO, or if you set target sv to say, 101 instead of 100.

I wouldn't expect a 1 unit mismatch to cause problems, but it's odd.
Logged
Don't forget what the H stands for.
Pages: 1 2 3 4 5 [6] 7   Go Up
« previous next »