supplierdeeply

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

  • 302 Replies
  • 64006 Views
*

Offline reyalp

  • ******
  • 9865
  • Publish
    Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
    « Reply #190 on: 02 / February / 2011, 00:27:16 »
    Advertisements
    Check the size of the badpixel.bin, and amount of free memory at boot. Probably, the badpixel.bin is so large it is using up too much memory: http://chdk.setepontos.com/index.php?topic=6050.0
    Don't forget what the H stands for.

  • Publish
    Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
    « Reply #191 on: 02 / February / 2011, 04:47:13 »

    I tried some more times and it seems that the image quality is better both in raw and in jpg using iso 16 (that I obtained requiring ISO 20).


    thats the true, because this camera seem use a Sony BSI Sensor.And on this WB2000(use a sony 10 MP BSI Sensor) testimage can too see, that on ISO 80 there is less noise.to see image larger click on + button

    http://www.cnet.de/galerie/41536404/beispielfotos_die_bildqualitaet_der_samsung_wb2000.htm#SID41536401

    >-It seems confirmed that the badpixels list with slower shutter speed is bigger

    try create a badpixel file with darkframe subtraction off, or on(is in RAW menu), maybe this work better.
    Ixus 1000 HS

    *

    Offline na01

    • *
    • 17
  • Publish
    Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
    « Reply #192 on: 02 / February / 2011, 04:58:48 »
    free memory at boor is 257920 bytes, about the half of the size of badpixels.bin

    try create a badpixel file with darkframe subtraction off, or on(is in RAW menu), maybe this work better.

    I tried it, but the number of bad pixels seems to be the same using slow shutter speed.

    I was trying to compile the beta9 code to do some test on the active area (to correct the black border).
    I have a question: i have to fill  FI2KEY and FI2IV, I read the informations about rom an offset, but is not clear for me what I have to put there (I have to get it from the original firmware?)...
    Maybe I lost the information somewhere in the thread, someone can help me?

    « Last Edit: 02 / February / 2011, 12:15:38 by na01 »

  • Publish
    Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
    « Reply #193 on: 02 / February / 2011, 06:26:28 »
    >I was trying to compile the beta9 code to do some test on the active area (to correct the black border).

    the Ixus 1000 have same sensor, and this are the settings.I think this values are ok.asm1989 have add it for his Camera and on my Camera this values are too good

       #define CAM_ACTIVE_AREA_X1         42
       #define CAM_ACTIVE_AREA_Y1         24
       #define CAM_ACTIVE_AREA_X2         3816-126
       #define CAM_ACTIVE_AREA_Y2         2784-24

    this values get of active area the jpg width and hight.

    how many badpixels you get ?

    I get on Ixus 1000 8326.and with that file i have 214 kb of free RAM
    its very constant and change only when i change darkframe subtract settings

    what values you get ?
    « Last Edit: 02 / February / 2011, 06:30:27 by Bernd R »
    Ixus 1000 HS


    *

    Offline na01

    • *
    • 17
  • Publish
    Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
    « Reply #194 on: 02 / February / 2011, 06:57:04 »
    Thank you, I tried the value from ixus 1000 with no succes, but with the following values it seems to work well

        #define CAM_ACTIVE_AREA_X1          94      
        #define CAM_ACTIVE_AREA_Y1          8      
        #define CAM_ACTIVE_AREA_X2          3811    
        #define CAM_ACTIVE_AREA_Y2          2784  

    now I'm going to test a little better the problem with hot pixels
    « Last Edit: 02 / February / 2011, 09:01:13 by na01 »

  • Publish
    Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
    « Reply #195 on: 02 / February / 2011, 11:43:34 »
    I dont know, but i think the values need match 10 megapixel size of CAM

    this is 3648*2736

    but your width is 3717 and 2776
    on other side, when there are 2776 pixels, its better for lens correct, because thru distortion there need cut some pixels.
    Ixus 1000 HS

    *

    Offline na01

    • *
    • 17
  • Publish
    Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
    « Reply #196 on: 02 / February / 2011, 11:56:44 »
    I suppose that the extra pixels are exactly used to crop in the jpeg.
    If you use  3717*2776 you are able to correct the distortion and use roughly the same field of view of jpeg (these are the results of a first camera calibration).

    I choose that values because represents the wider area that I can use without obtaining black borders. There is a reason to crop the raw image?

    *

    Offline pixeldoc2000

    • ****
    • 355
    • IXUS900Ti 1.00C, IXUS300HS 1.00D
      • pixel::doc homebase
  • Publish
    Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
    « Reply #197 on: 02 / February / 2011, 12:03:04 »
    UPDATE
    solved, correct values read from original rom are
    FI2KEY=<DELETE_ME>
    FI2IV =<DELETE_ME>
    Please remove FI2KEY and FI2IV Keys from your post!

    Please avoid to public them in forum, blog, website for our/your own sake. Read: http://chdk.setepontos.com/index.php/topic,2995.0.html

    -I can confirm that the freeze shown in the last post is due to the bigger badpixels list (or due its content?)
    Looks like this affect Cameras with CMOS Sensor much more. Also the amount of badpixel is related to Sensor temperatur amd Longer exposer is likely to cause higher Sensor temp.
    « Last Edit: 02 / February / 2011, 12:11:06 by pixeldoc2000 »


    *

    Offline pixeldoc2000

    • ****
    • 355
    • IXUS900Ti 1.00C, IXUS300HS 1.00D
      • pixel::doc homebase
  • Publish
    Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
    « Reply #198 on: 02 / February / 2011, 12:32:59 »
    I have to admit i didn't spend much time about CAM_ACTIVE_AREA stuff yet.

    Code: [Select]
        #define CAM_ACTIVE_AREA_X1          120      // x offset right ?
        #define CAM_ACTIVE_AREA_Y1          20       // y offset down ?
        #define CAM_ACTIVE_AREA_X2          3600     // ToDo, just guesswork
        #define CAM_ACTIVE_AREA_Y2          2750     // ToDo, just guesswork

    This is what i came up with after short testing yesterday.

    Just for the record:
    Stuff like ROM:FFB28EF4 in my source refers to related firmware dump disassembled in IDA with correct defined segment address. Read more: http://chdk.wikia.com/wiki/Loading_dump_to_IDA or http://chdk.wikia.com/wiki/GPL_Disassembling .

    platform\ixus300_sd4000\sub\100d\makefile.inc
    Code: [Select]
    ROMBASEADDR=0xFF810000    # 0xFF810000 for S-, SD-, and G- seriesmakefile also gives you correct ROM "base" address for the related firmware dump.

  • Publish
    Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
    « Reply #199 on: 03 / February / 2011, 12:16:21 »
    @pixeldoc2000
    >Looks like this affect Cameras with CMOS Sensor much more. Also the amount of badpixel is related to >Sensor temperatur amd Longer exposer is likely to cause higher Sensor temp.

    how many badpixels you get ?
    I see the Ixus 300 RAW with blackpixel from both of you, and i can say my Ixus 1000 with same sensor show more wrong pixel, but when i run badpixel i get 8326 Bad pixels, and my DNG save is then bad pixel clean.

    so your cam should have less than 8326 badpixels and 33 kb filesize i think.

    it seem also important that you not capture too black scene, because this camera have for black also valid values below 127.


    i measure the correct values with a testcode , see here

    http://chdk.setepontos.com/index.php?topic=5722.msg60215#msg60215

    this is also usefull to find max black and white levels.values i use in camera.h

     #define CAM_WHITE_LEVEL             ((1<<CAM_SENSOR_BITS_PER_PIXEL)-16)
        #define CAM_BLACK_LEVEL             110
    « Last Edit: 03 / February / 2011, 12:23:28 by Bernd R »
    Ixus 1000 HS

     

    Related Topics