Adding new cameras, applying patches into trunk (with source code prepared) - page 94 - General Discussion and Assistance - CHDK Forum
supplierdeeply

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

  • 1666 Replies
  • 697183 Views
*

Offline nafraf

  • *****
  • 1308
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #930 on: 17 / December / 2012, 05:34:18 »
Advertisements
sx260 100b patch to fix long exposure time.

Bug detected by lapser, reported here

*

Offline philmoz

  • *****
  • 3442
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #931 on: 17 / December / 2012, 06:08:23 »
sx260 100b patch to fix long exposure time.

Bug detected by lapser, reported here


Added in revision 2393 (trunk) and 2394 (release-1.1).

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)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

*

Offline nafraf

  • *****
  • 1308
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #932 on: 19 / December / 2012, 16:56:13 »
sx260 new loader patch, written by whim, tested by lapser on sx260 100b.

*

Offline whim

  • ******
  • 2044
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #933 on: 19 / December / 2012, 19:41:36 »
Quote
written by whim
Sorry for being off topic, but there's only 1 person who has written this patch, and that's philmoz (See here)
Me - i just got carried away a bit after successfully testing it on my cams ... feels a bit embarassing
to be credited for what's basically copy/pasting.

thanks,

wim


*

Offline philmoz

  • *****
  • 3442
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #934 on: 22 / December / 2012, 17:10:36 »
sx260 new loader patch, written by whim, tested by lapser on sx260 100b.


Added in revision 2400 (trunk) and 2401 (release-1.1)

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)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #935 on: 28 / December / 2012, 13:22:45 »
Fix for USB remote V2 operation for the S3is per this post :

http://chdk.setepontos.com/index.php?topic=9169.msg94874#msg94874

Patch works for both 1.1 and dev trunks.


Ported :   A1200    SD940   G10    Powershot N    G16

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #936 on: 28 / December / 2012, 14:59:33 »
A couple of small patches for two of the four "default" scripts included with CHDK.   Those scripts are included in CHDK as the  simplest possible examples of things people might want to do with CHDK.  However,  I've noticed that they have become somewhat more than that to new users of CHDK.  They are often assumed to be the correct (if simple) way to do these things.

So I'd like to propose the smallest possible update to address issues I've seen posted.  My intent is not to produce better more complicated scripts.  There are hundred of each on the wiki & forum already and any "improvements"  can take us down a slippery slope likely to end up in flame-wars.   So these proposed updates are just to make two of the existing scripts a little more usable.

The first update is to make the threshold and delay values in the motion.bas & motion.lua scripts into parameters.  These are typically the two values people need to adjust to get reasonable motion detection performance.

The second update is add an adjustment (in 1/2 f-stop increments) to the hdr.bas & hdr.lua scripts.  This will let users adjust the amount of exposure range that the hdr scripts use.

Should be trivial enough to add to both the main trunk and dev branches ?

« Last Edit: 28 / December / 2012, 15:04:44 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3442
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #937 on: 28 / December / 2012, 17:49:09 »
Fix for USB remote V2 operation for the S3is per this post :

http://chdk.setepontos.com/index.php?topic=9169.msg94874#msg94874

Patch works for both 1.1 and dev trunks.



A couple of small patches for two of the four "default" scripts included with CHDK.   Those scripts are included in CHDK as the  simplest possible examples of things people might want to do with CHDK.  However,  I've noticed that they have become somewhat more than that to new users of CHDK.  They are often assumed to be the correct (if simple) way to do these things.

So I'd like to propose the smallest possible update to address issues I've seen posted.  My intent is not to produce better more complicated scripts.  There are hundred of each on the wiki & forum already and any "improvements"  can take us down a slippery slope likely to end up in flame-wars.   So these proposed updates are just to make two of the existing scripts a little more usable.

The first update is to make the threshold and delay values in the motion.bas & motion.lua scripts into parameters.  These are typically the two values people need to adjust to get reasonable motion detection performance.

The second update is add an adjustment (in 1/2 f-stop increments) to the hdr.bas & hdr.lua scripts.  This will let users adjust the amount of exposure range that the hdr scripts use.

Should be trivial enough to add to both the main trunk and dev branches ?



Both added in revision 2411 (trunk) and 2412 (release-1.1).

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)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)


Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #938 on: 28 / December / 2012, 18:05:20 »
Both added in revision 2411 (trunk) and 2412 (release-1.1).
Sure - today the patches get added quickly  :'(

Realized as I was driving home that the changes to the HDR script work in full f-stops rather than half stops.  This corrects the patched script for half stops.

TIA.
« Last Edit: 28 / December / 2012, 18:10:22 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3442
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #939 on: 28 / December / 2012, 18:25:42 »
Both added in revision 2411 (trunk) and 2412 (release-1.1).
Sure - today the patches get added quickly  :'(

Realized as I was driving home that the changes to the HDR script work in full f-stops rather than half stops.  This corrects the patched script for half stops.

TIA.


Updated in revision 2414 (trunk) and 2415 (release-1.1).

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)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

 

Related Topics