badpixel.bin failed - page 2 - RAW Shooting and Processing - CHDK Forum  

badpixel.bin failed

  • 14 Replies
  • 15836 Views
*

Offline c_joerg

  • *****
  • 1248
Re: badpixel.bin failed
« Reply #10 on: 03 / May / 2018, 15:31:14 »
Advertisements
Here's what I did. In case it's easy, may be you can correct me?
dcraw -j -t 0 -4 330___05/CRW_1591.DNG

a1=imread('/mnt/win1/330___05/CRW_1591.ppm');
[iq,jq]=find(a1(:,:,1)==0 & a1(:,:,2)==0 & a1(:,:,3)==0);
size(iq)

If you only want to read RAW data (1 to 1) I do it in the following way:
Code: [Select]
dcraw -4 -D -T img_0001.dng
pic = imread(‘img_0001.tiff‘);
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

Re: badpixel.bin failed
« Reply #11 on: 03 / May / 2018, 15:46:05 »
Code: [Select]
dcraw -4 -D -T img_0001.dng
Thanks, the -D was the magic key!

*

Offline reyalp

  • ******
  • 14082
Re: badpixel.bin failed
« Reply #12 on: 03 / May / 2018, 17:18:20 »
Code: [Select]
dcraw -4 -D -T img_0001.dng
Thanks, the -D was the magic key!
FWIW, you can get this kind of information in chdkptp too, using the dnghist command:
Code: [Select]
___> dngload CRW_1591.DNG
loaded CRW_1591.DNG
___> dnghist -max=127 -bin=8
  0-  7 16193
  8- 15 0
 16- 23 0
 24- 31 0
 32- 39 0
 40- 47 0
 48- 55 0
 56- 63 0
 64- 71 0
 72- 79 0
 80- 87 0
 88- 95 0
 96-103 0
104-111 0
112-119 1
120-127 41
___> dngload CRW_1593.DNG
loaded CRW_1593.DNG
___> dnghist -max=127 -bin=8
  0-  7 54631
  8- 15 248
 16- 23 334
 24- 31 245
 32- 39 282
 40- 47 295
 48- 55 393
 56- 63 372
 64- 71 640
 72- 79 673
 80- 87 769
 88- 95 1104
 96-103 1332
104-111 1377
112-119 1797
120-127 2462
dngdump can be used to dump the data unmodified, e.g.

Code: [Select]
dngdump -raw -rfmt=16pgm
writes the data as a 16 bpp PGM file

edit: Oops, forgot is shifted to fill the full 16 bit range, so not strictly unmodified. Actually it doesn't, but it sets the maxval in in the pgm, which an image editing program may use to scale.
« Last Edit: 05 / May / 2018, 00:22:53 by reyalp »
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 14082
Re: badpixel.bin failed
« Reply #13 on: 03 / May / 2018, 17:42:22 »
Ok, let's see, 3 new DNGs. The CRW_1594.DNG is a bit underexposed, but hopefully still can be compared with the CRW_1593.DNG.
It looks to me like the ISO 3200 images always have 53543 zero valued pixels, but the numbers higher than 0 are variable.

This posses a dilemma for badpixel code, since the > 0 values will still look bad if unpatched, but can't be used to generate a list.
Don't forget what the H stands for.


Re: badpixel.bin failed
« Reply #14 on: 03 / May / 2018, 18:31:17 »
the ISO 3200 images always have 53543 zero valued pixels, but the numbers higher than 0 are variable.
Yes, I'm confirming this (thanks for the dnghist!) for 6 other DNGs I have. I checked 0<=values<=15.


 

Related Topics