supplierdeeply

Adding new cameras, applying patches into trunk (with source code prepared)

  • 1598 Replies
  • 295436 Views
*

Offline reyalp

  • ******
  • 11496
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1250 on: 20 / October / 2013, 00:12:18 »
Advertisements
Patch file to enable the G10 to use set_focus() in both MF and non-MF modes.
Added, trunk changeset 3166 release changeset 3167
Don't forget what the H stands for.

*

Offline dvip

  • ****
  • 451
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1251 on: 20 / October / 2013, 00:24:48 »
>Patch file to enable the G10 to use set_focus() in both MF and
>non-MF modes.

Nice patch.
I know the A590IS always has to be in MF for this to work.
I wonder if this patch to enable the G10 to
use set_focus() in both MF and non-MF modes will do the same using the A590IS.


Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1252 on: 20 / October / 2013, 09:58:03 »
I know the A590IS always has to be in MF for this to work.  I wonder if this patch to enable the G10 to
use set_focus() in both MF and non-MF modes will do the same using the A590IS.
For what its worth,  the SD override code is pretty much the same for every camera.   There are five #defines that control when CHDK will try to use this code :

Code: [Select]
#define CAM_CAN_SD_OVERRIDE          1   // Camera allows to do subject distance override
 #define CAM_CAN_SD_OVER_NOT_IN_MF    1   // Camera allows subject distance (focus) override when not in manual focus mode
 #undef  CAM_CAN_SD_OVER_IN_AF_LOCK       // Camera allows subject distance (focus) override when in AF Lock mode
 #undef  CAM_CAN_SD_OVER_IN_AF_LOCK_ONLY  // Camera allows subject distance (focus) override only when in AF Lock mode OR in movie mode
 #define CAM_HAS_MANUAL_FOCUS         1   // Camera has manual focus mode
A particular camera's CHDK port will have some combination of these mode - testing is mostly trial & error to figure out which ones work and which don't.  After that,  its really only a question of the MoveFocusLensToDistance address in platform_camera.h
Ported :   A1200    SD940   G10    Powershot N    G16

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1253 on: 06 / November / 2013, 17:42:26 »
Small patch for config file ID typo in 1.3.0.

Was causing the "Shutter halfpress show" menu item to not save / restore properly.
« Last Edit: 06 / November / 2013, 17:52:32 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline philmoz

  • *****
  • 3070
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1254 on: 07 / November / 2013, 03:13:08 »
Small patch for config file ID typo in 1.3.0.

Was causing the "Shutter halfpress show" menu item to not save / restore properly.

Added in revision 3202.

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

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1255 on: 08 / November / 2013, 19:41:42 »
Small fix for the "circles of confusion" parameter for the G10 found here : http://www.dofmaster.com/digital_coc.html

I spot checked a few other cameras but did not find problems although I may very well have missed them if they are there.

Should probably go in trunk and dev branches.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3070
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1256 on: 08 / November / 2013, 23:35:49 »
Small fix for the "circles of confusion" parameter for the G10 found here : http://www.dofmaster.com/digital_coc.html

I spot checked a few other cameras but did not find problems although I may very well have missed them if they are there.

Should probably go in trunk and dev branches.

Added in revision 3206 (trunk) and 3207 (release-1.2).

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

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1257 on: 09 / November / 2013, 11:46:46 »
Fix for variable OSD font sizes not drawing misc values and state display properly as reported by msl here :
http://chdk.setepontos.com/index.php?topic=10869.msg107011#msg107011
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline philmoz

  • *****
  • 3070
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1258 on: 09 / November / 2013, 17:17:45 »
Fix for variable OSD font sizes not drawing misc values and state display properly as reported by msl here :
http://chdk.setepontos.com/index.php?topic=10869.msg107011#msg107011

Added in revision 3209.

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

*

Offline srsa_4c

  • ******
  • 3689
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #1259 on: 13 / November / 2013, 11:10:27 »
Patch to fix a regression in raw_init_badpixel_bin() - CHDK 1.2 and 1.3.
Code: [Select]
Index: modules/dng.c
===================================================================
--- modules/dng.c (revision 3220)
+++ modules/dng.c (working copy)
@@ -845,6 +845,7 @@
                     fwrite(c, 1, 4, f);
                 }
                 count = count + len;
+                y += len - 1;
             }
         }
     }
Can somebody upload a real life badpixel.bin made on a CMOS camera (preferably after the fix)? I'd like to test something...

 

Related Topics