SD940 (IXUS120) porting thread - page 22 - DryOS Development - CHDK Forum supplierdeeply

SD940 (IXUS120) porting thread

  • 542 Replies
  • 155834 Views
*

Offline waldo

  • ***
  • 238
Re: SD940 (IXUS120) porting thread
« Reply #210 on: 07 / January / 2011, 20:07:58 »
Advertisements
Then again, in a camera with such a small image sensor, most people would probably want the default Canon behavior for lower noise (i.e. the "Auto" setting).
I hear you.  Looking at the barrel distortion in my DNG images,  I also wonder why RAW seems attractive on a small camera to people ?  Sure, on a $1500 DSLR with  a good 50mm lens there is something to be said for not having jpeg compression.  But I must be missing something - what does it get me with something like the SD940?

Raw has a little more detail, but every passing year, it gets harder to use because cameras do more processing internally before they save the jpeg.  It creates a bigger burden to replicate all that processing on your PC.  One thing I do like about Raw is its extended dynamic range, 10 or 12 bits vs. 8 with jpeg.  But the intelligent contrast feature works pretty well to do tone mapping of the raw image prior to saving as a jpeg and this reduces the need for Raw somewhat IMO.

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD940 (IXUS120) porting thread
« Reply #211 on: 07 / January / 2011, 20:15:25 »
Yes, that seems to be the problem with the battery display.  For some reason, the values in get_vbatt_min() and get_vbatt_max() are wrong.
AFAIK SD940 has a 3,6V or 3,7V battery. If battery is fully charged it will be around 4,1V.

Current Source:
Code: [Select]
long get_vbatt_min()
{
return 4550;     // 4550 = 4.5V
}

long get_vbatt_max()
{
return 5150;     // 5150= 5.1V
}
obviously does not fit if battery max voltage is 4,1V ;)

Try:
Code: [Select]
// Battery min. Voltage
long get_vbatt_min() {
    return 3200;    // ToDo: use real value, this is just a guess
}

// Battery max. Voltage
long get_vbatt_max() {
    return 4100;    // ToDo: use real value, this is just a guess
}
« Last Edit: 07 / January / 2011, 20:18:14 by pixeldoc2000 »

*

Offline reyalp

  • ******
  • 13440
Re: SD940 (IXUS120) porting thread
« Reply #212 on: 07 / January / 2011, 22:35:25 »
Also keep in mind you can override this in your settings, and if you do this, you won't see any subsequent changes from the code.
Don't forget what the H stands for.

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD940 (IXUS120) porting thread
« Reply #213 on: 07 / January / 2011, 22:46:47 »
Also keep in mind you can override this in your settings, and if you do this, you won't see any subsequent changes from the code.
Yes, if code is changed one need to reset chdk settings or delete chdk config to see changes in chdk.


Re: SD940 (IXUS120) porting thread
« Reply #214 on: 08 / January / 2011, 05:16:43 »
But I must be missing something - what does it get me with something like the SD940?

In my opinion, you are not missing anything.
The early developers of CHDK became angry if you suggested such a thing and even tried banning discussion of the topic.

The one small advantage is that you can change white balance.

Re: SD940 (IXUS120) porting thread - releasing to the trunk ?
« Reply #215 on: 08 / January / 2011, 10:11:22 »
I know we are not quite there yet but I scrolled through "Adding new cameras, applying patches into trunk (with source code prepared)" http://chdk.setepontos.com/index.php?topic=650.  Unless I missed it, there was not much there to explain the ground rules of the process - is there a wiki link or better thread to follow ?

I have a list of files that I change when I move my port to a newer trunk release (currently  ./include/camera.h, ./core/conf.c, ./core/kbd.c, ./makefile, ./makefile.inc )   I guess I need to generate a patch file that inserts #ifdef CAMERA_ixus120_SD940 into the appropriate place in each file ?

I'd also like to change the default setup so that CCHDK.CFG is tuned to the camera (OSD colors,  screen position etc).  What's the best way to do that ?
Ported :   A1200    SD940   G10    Powershot N    G16

Re: SD940 (IXUS120) porting thread - releasing to the trunk ?
« Reply #216 on: 08 / January / 2011, 10:41:36 »
I'd also like to change the default setup so that CCHDK.CFG is tuned to the camera (OSD colors,  screen position etc).  What's the best way to do that ?

In conf.c, function conf_init_defaults() can load specific values for each camera.

e.g.

#if defined (CAMERA_g11) || defined (CAMERA_sx200is)|| defined(CAMERA_s90)|| defined(CAMERA_s95)
    def_mode_state_pos.x=294;
    def_batt_icon_pos.x = 10;
#endif

David

Re: SD940 (IXUS120) porting thread
« Reply #217 on: 08 / January / 2011, 11:25:48 »
In conf.c, function conf_init_defaults() can load specific values for each camera.

Just to be sure,  you are talking about the conf.c in the trunk1031/core directory ?  The stock trunk1031 file I have does not currently have any customizations in conf_init_defaults() although I obviously see how your example will work.
Ported :   A1200    SD940   G10    Powershot N    G16


Re: SD940 (IXUS120) porting thread
« Reply #218 on: 09 / January / 2011, 03:56:24 »
« Last Edit: 09 / January / 2011, 04:01:42 by dave1978 »

Re: SD940 (IXUS120) porting thread
« Reply #219 on: 09 / January / 2011, 05:08:26 »
Just to be sure,  you are talking about the conf.c in the trunk1031/core directory ? 

Yes, but it seems the CHDK version does not have any customisation.

The example I quoted is from the SDM version.

 

Related Topics