Adding new cameras, applying patches into trunk (with source code prepared) - page 90 - General Discussion and Assistance - CHDK Forum
supplierdeeply
« previous next »
Pages: 1 ... 85 86 87 88 89 [90] 91 92 93 94 95 ... 168   Go Down

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

  • 1672 Replies
  • 708954 Views
*

Offline aditidatta

  • *
  • 10
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #890 on: 19 / November / 2012, 22:09:45 »
Advertisements
Bur where is the 101c folder in ixus115hs???
Logged
*

Offline waterwingz

  • ******
  • 12134
    • Waterwingz
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #891 on: 19 / November / 2012, 22:14:50 »
Quote from: aditidatta on 19 / November / 2012, 22:09:45
Bur where is the 101c folder in ixus115hs???
cross posted here : http://chdk.setepontos.com/index.php?topic=845.msg93479#msg93479

please don't do that
« Last Edit: 19 / November / 2012, 22:36:59 by waterwingz »
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline philmoz

  • *****
  • 3447
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #892 on: 20 / November / 2012, 03:54:57 »
Quote from: nafraf on 19 / November / 2012, 04:06:00
Patch to sx240/sx260:
- #define MKDIR_RETURN_ONE_ON_SUCCESS   added to platform_camera.h.
- sx240/sx260 100c - Fix pointer to DeleteFile_Fut in stubs_entry_2.S
- sx240 101a port. Tested by JamesBMI6 and Uran, reports here

Quote from: ERR99 on 19 / November / 2012, 16:34:58
Hello,

here ist the first version of the SX50HS port (1.00b, ALPHA version with SKIP_AUTOBUILD configuration).
Patch is created based on trunk revision 2289. The diff includes also a small change for tools/packfi2/fi2enc.c (DryOS R51 also needs the "extra value" as R50 to get PS.FI2 working).


Both added in revisions 2292-2293 (trunk) and 2294 (release-1.1)

Phil.
Logged
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 #893 on: 21 / November / 2012, 18:46:05 »
small patch to fix PLATFORMID in sx240 101a
Logged
*

Offline reyalp

  • ******
  • 13965
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #894 on: 21 / November / 2012, 23:11:32 »
Quote from: nafraf on 21 / November / 2012, 18:46:05
small patch to fix PLATFORMID in sx240 101a
Added, changesets 2298 and 2299.
Logged
Don't forget what the H stands for.
*

Offline nafraf

  • *****
  • 1308
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #895 on: 23 / November / 2012, 06:51:10 »
patch ixus105 to solve this bug, found and fixed by casrap
Quote
Overrides only work when the self timer is off, when you select a self timer of 2 or 10sec (or custom) overrides are ignored. Sometimes it takes one shot with timer+overrides, but all the next shots are again without overrides.

I prepared the patch and ported the code to 100b. 
Patch was tested in 100d, but it was not tested in 100b.

Logged
*

Offline philmoz

  • *****
  • 3447
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #896 on: 23 / November / 2012, 07:24:12 »
Quote from: nafraf on 23 / November / 2012, 06:51:10
patch ixus105 to solve this bug, found and fixed by casrap
Quote
Overrides only work when the self timer is off, when you select a self timer of 2 or 10sec (or custom) overrides are ignored. Sometimes it takes one shot with timer+overrides, but all the next shots are again without overrides.

I prepared the patch and ported the code to 100b. 
Patch was tested in 100d, but it was not tested in 100b.



Added in revisions 2309 (trunk) and 2310 (release-1.1)

Phil.
Logged
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 srsa_4c

  • ******
  • 4451
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #897 on: 23 / November / 2012, 14:45:58 »
Small patch for the SX150IS to fix the file counter issue (thread starts here, success report here).

@philmoz
About changeset 2308: If the following
Quote from: pshotuser on 21 / November / 2012, 15:26:11
p.s. Could the problem be due to dark frame subtraction? With brief shutter time i have never had a problem.
is true, the file counter is sometimes already correct when the raw hook is reached. In that case r2308 will enforce the maximum delay. Partial proposal below. Partial = some affected ports (like the Ixus220) do not currently call the NR hook, those will need an additional #define in capt_seq.c. I might be still missing something, that's the reason why I'm posting here.
Logged
*

Offline philmoz

  • *****
  • 3447
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #898 on: 23 / November / 2012, 18:01:31 »
Quote from: srsa_4c on 23 / November / 2012, 14:45:58
@philmoz
About changeset 2308: If the following
Quote from: pshotuser on 21 / November / 2012, 15:26:11
p.s. Could the problem be due to dark frame subtraction? With brief shutter time i have never had a problem.
is true, the file counter is sometimes already correct when the raw hook is reached. In that case r2308 will enforce the maximum delay. Partial proposal below. Partial = some affected ports (like the Ixus220) do not currently call the NR hook, those will need an additional #define in capt_seq.c. I might be still missing something, that's the reason why I'm posting here.

I considered that possibility; but decided against it.

When I looked at this I started out recording the before and after file counter values to see how often the loop went to the full delay period. On the cameras I have that are affected by this it happened very rarely so I decided to stick with a simple solution. It's no worse than the previous code and in most cases exits the loop after 10 - 20ms.

There's no guarantee that capturing the file counter in capt_seq_hook_set_nr will behave any differently - the call to this is not that much earlier than the call to capt_seq_hook_raw_here and there is no sleep between them so in all likelihood it would get the same file counter value.

Phil.
Logged
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 philmoz

  • *****
  • 3447
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #899 on: 23 / November / 2012, 18:06:14 »
Quote from: srsa_4c on 23 / November / 2012, 14:45:58
Small patch for the SX150IS to fix the file counter issue (thread starts here, success report here).

Added in revision 2312 (trunk) and 2313 (release-1.1).

Phil.
Logged
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)
Pages: 1 ... 85 86 87 88 89 [90] 91 92 93 94 95 ... 168   Go Up
« previous next »
 

Related Topics