SD 4000 IS / IXUS 300 HS / IXY 30S porting thread - page 25 - DryOS Development - CHDK Forum supplierdeeply

SD 4000 IS / IXUS 300 HS / IXY 30S porting thread

  • 322 Replies
  • 162004 Views
*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #240 on: 01 / March / 2011, 18:41:12 »
Advertisements
@Yury
Nice work.

I've update aperture_sizes_table, but it looks like camera does not directly use this values for "Override aperture".
EDIT: "Override aperture" are roundet values derivered from prop_id in aperture_sizes_table struct :
Code: [Select]
const ApertureSize aperture_sizes_table[] = {
    // id, prop_id, name (typedef for struct is at platform.h)
    {  0, 200, "2.0" },
    {  1, 224, "2.2" },
    {  2, 256, "2.5" },
    {  3, 288, "2.8" },
    {  4, 320, "3.2" },
    {  5, 352, "3.5" },
    {  6, 384, "4.0" },
    {  7, 416, "4.5" },
    {  8, 448, "5.0" },
    {  9, 480, "5.6" },
    { 10, 512, "6.3" },
    { 11, 544, "7.1" },
    { 12, 576, "8.0" },
};

maybe the lens of Ixus 300 is from S95 G12 and so contain a Iris and Ixus 1000 have a lens without Iris and ND Filter.Is that possible ?
AFAIK camera have either ND-Filter or IRIS (and ND-Filter). But SD4000 and other firmware dumps contain ND-Filter strings and functions.
On SD900 i can hear a mechanical noise if Camera use (put in) ND-Filter. If you point Camera into very bright light source (sun / light bulp), camera use ND-Filter.

Maybe it set different aperture by zooming lenzes. When you zoom, camera show higher aperture values, because as I understand zoom reduce light power.
True.
« Last Edit: 02 / March / 2011, 13:48:56 by pixeldoc2000 »

Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #241 on: 03 / March / 2011, 07:10:24 »
Where to read about the structure of the raw-files for this model?

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #242 on: 03 / March / 2011, 12:47:19 »
Where to read about the structure of the raw-files for this model?
(CHDK) RAW files have no "defined" structure. It a "binary" files containing only "RAW" Data from Image Sensor.
CHDK "just" dumps the RAW Image Sensor Data (Buffer) from Camera Memory into a "RAW" file (CRW_0001.CRW for example).

SD4000 Image Sensor use CFA RGGB pattern:
Note: 2x2 CFA means that your sensor have RGGB CFA (RED, GREEN, GREEN, BLUE dispose in 2x2 matrix) then:
first line is       RGRGRGRGRGRG...
second line is: GBGBGBGBGBGB...
third line is:     RGRGRGRG...
and so on   ...
Code: [Select]
#define cam_CFAPattern 0x02010100 // Red  Green  Green  Blue
If you just want to view/edit/etc. RAW enable DNG in CHDK ("DNG format") or convert RAW files to DNG on your computer.
Most software should be able use DNG files from CHDK.
« Last Edit: 03 / March / 2011, 12:58:38 by pixeldoc2000 »

*

Offline Yury

  • *
  • 15
  • IXUS 300HS 1.00D, IXUS 980IS 1.01B
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #243 on: 03 / March / 2011, 15:46:23 »
I decided to check how DNG format works in 300HS, but when I was trying to switch it on - DNG format [ON] I've got message - Cannot load CHDK/badpixel.bin. Looks like it concern menu item that one position upper - Bad pixel removal, but it off in my case and I don't need it as long as camera new. I never tryed DNG before, maybe I am doing something wrong, but it looks for me as problem in menu. Hope anybody can help me understand it.


Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #244 on: 03 / March / 2011, 22:06:58 »
(CHDK) RAW files have no "defined" structure. It a "binary" files containing only "RAW" Data from Image Sensor.
CHDK "just" dumps the RAW Image Sensor Data (Buffer) from Camera Memory into a "RAW" file (CRW_0001.CRW for example).

I need structure of image Sensor :)

SD4000 Image Sensor use CFA RGGB pattern:
Note: 2x2 CFA means that your sensor have RGGB CFA (RED, GREEN, GREEN, BLUE dispose in 2x2 matrix) then:
first line is       RGRGRGRGRGRG...
second line is: GBGBGBGBGBGB...
third line is:     RGRGRGRG...
and so on   ...
Code: [Select]
#define cam_CFAPattern 0x02010100 // Red  Green  Green  Blue
Ok.

How to understand the meaning: cam_CFAPattern 0x02010100 ?
2 - red, 1 - green, 0 - blue?
It isn't order of color channels in raw file. For what use this value?

How many bits are used for each point in a saved file? 12-bit?

Example, three first bytes from raw file:
0xFF 0xF1 0x11 = 0xFFF 0x111 (color channels R and G)

and little endian? Is it true?

If you just want to view/edit/etc. RAW enable DNG in CHDK ("DNG format") or convert RAW files to DNG on your computer.
Most software should be able use DNG files from CHDK.
There is no software that converts the file from 300HS.

For what we use these defines?
#define CAM_ACTIVE_AREA_X1 116
#define CAM_ACTIVE_AREA_Y1 14
#define CAM_ACTIVE_AREA_X2 3788
#define CAM_ACTIVE_AREA_Y2 2766

PS
My english is very bad english with google translate. Sorry.

*

Offline fe50

  • ******
  • 3139
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #245 on: 04 / March / 2011, 01:03:40 »
I decided to check how DNG format works in 300HS, but when I was trying to switch it on - DNG format [ON] I've got message - Cannot load CHDK/badpixel.bin. Looks like it concern menu item that one position upper - Bad pixel removal, but it off in my case and I don't need it as long as camera new.
A badpixel.bin file is always needed to enable DNG creation.

This is used to handle defective / "bad" pixels which were stored by the manufacturer in the original firmware. Those bad pixels are removed automatically while JPEG file creation; to create a valid DNG file, we also need those informations (means: the camera's original/internal bad pixel list)...

You'll find a menu item to create the badpixel.bin file in the CHDK RAW menu, with older or not fully ported CHDK builds (i guess also with this SD4000 port) run the "badpixel.lua" script instead.
(see also http://chdk.wikia.com/wiki/Badpixel_removal )

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #246 on: 05 / March / 2011, 16:45:07 »
How many bits are used for each point in a saved file? 12-bit?
Sensor is 12 Bit.

There is no software that converts the file from 300HS.
As i already said, please use DNG to avoid this issus.

For what we use these defines?
#define CAM_ACTIVE_AREA_X1 116
#define CAM_ACTIVE_AREA_Y1 14
#define CAM_ACTIVE_AREA_X2 3788
#define CAM_ACTIVE_AREA_Y2 2766
Read CAM_ACTIVE_AREA for SD4000.
This stuff is used for DNG, bad pixel, darkframe and more.

Get CHDK source and search for CAM_ACTIVE_AREA for example...

@FE50
AFAIK "Create badpixel.bin" CHDK Menu Item is already available in Beta v10.

*

Offline Yury

  • *
  • 15
  • IXUS 300HS 1.00D, IXUS 980IS 1.01B
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #247 on: 05 / March / 2011, 21:22:05 »
Thanks for help. I've checked DNG - it works fine - no problems found.
During this test I found that actually lenzes of 300HS have more distortion than we can see on JPG. This is because Canon firmware make post processing that remove distortion, but angle of view become less. I decided to show it to everybody, maybe it will be interesting to someone. Look at the door and you will see big difference.



Below images at original resolution.

JPG made by Canon firmware
www.propergraphics.com/temp/img/IMG_9152.JPG
JPG that was converted from DNG with ACDSee
www.propergraphics.com/temp/img/CRW_9152.jpg

Is it possible to make in CHDK option that allow save JPG image as we can see on DNG - without distortion correction and noise reduction? For some purposes it would be useful because actual angle of view wider and image sharper.
« Last Edit: 05 / March / 2011, 22:22:27 by Yury »


*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #248 on: 07 / March / 2011, 17:10:52 »
During this test I found that actually lenzes of 300HS have more distortion than we can see on JPG.
Yes, Barel distortion is rather strong compared to my SD900. Made a simular compare with JPG and DNG.

Is it possible to make in CHDK option that allow save JPG image as we can see on DNG - without distortion correction and noise reduction?
AFAIK nobody tried it.
But why don't you convert DNG to JPG, or do your own postprocessing on DNG and than convert to JPG?!?
« Last Edit: 07 / March / 2011, 17:46:49 by pixeldoc2000 »

*

Offline Yury

  • *
  • 15
  • IXUS 300HS 1.00D, IXUS 980IS 1.01B
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #249 on: 07 / March / 2011, 20:47:52 »
During this test I found that actually lenzes of 300HS have more distortion than we can see on JPG.
Yes, Barel distortion is rather strong compared to my SD900. Made a simular compare with JPG and DNG.
You made much better comparison!  :)

But why don't you convert DNG to JPG, or do your own postprocessing on DNG and than convert to JPG?!?
Yes, this work ok. But with DNG continuous mode will be very slow, so you will not be able to use it for example for sport. But probably such mode not very usefull, so nobody tryed it.
« Last Edit: 07 / March / 2011, 20:51:58 by Yury »

 

Related Topics