CHDK 1.2 release planning - General Discussion and Assistance - CHDK Forum

CHDK 1.2 release planning

  • 23 Replies
  • 7033 Views
*

Offline reyalp

  • ******
  • 12159
CHDK 1.2 release planning
« on: 05 / July / 2013, 15:46:26 »
Advertisements
The remote capture merge was the last major thing I wanted to get in before the release.

The current trunk is pretty usable, I'm not aware of any area where it is significantly broken compared to the 1.1 branch. So I have declared the 1.2 trunk is now in the "stabilization phase".  I hope to keep this phase short, and have a very short "release candidate" phase after that.

There are still some minor things I'd like to get done before release.

* Clarify / resolve custom auto ISO issues http://chdk.setepontos.com/index.php?topic=8467.msg102489#msg102489
* Raw stuff in  http://chdk.setepontos.com/index.php?topic=10242.0 (some of this is already taken care of by remotecap merge)
* fix a470 sensor size mismatch changeset 2929
* Fix the PTP alt mode confusion http://chdk.wikia.com/wiki/Lua/PTP_Scripting#General_information_about_executing_Lua_code_over_PTP changesets 2944-2945
* Allow PTP to cleanly kill running script (maybe), I think it can be done in straightforward way, will punt if it can't. deferred, not urgent.
* Make PTP not use 50% of available RAM for buffer if there's lots available. deferred http://chdk.setepontos.com/index.php?topic=4338.msg103076#msg103076
* Make PTP_CHDK_CallFunction use call_func_ptr changeset 2931
* Make convert_dng_to_chdk_raw smarter about it's buffer size deferred, not urgent.
* unify set_record and switch_mode_usb http://chdk.setepontos.com/index.php?topic=9582.msg98447#msg98447 (from msl below)   changeset 2971

Please feel free to add suggestions or comments to this thread.
« Last Edit: 21 / July / 2013, 22:22:34 by reyalp »
Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 12159
Re: CHDK 1.2 release planning
« Reply #1 on: 05 / July / 2013, 15:55:23 »
One thing that would be nice to have for the 1.2 release is a summary of significant user-visible changes. I have added the ones I remember to http://chdk.wikia.com/wiki/Releases but a skim through the svn logs might bring up more worth mentioning. What I have in mind is stuff that would actually matter to end users.

This would also be a good time to update the language files.

It would also be good time to re-format code if we want to do that.

edit:
Also, waterwingz has being doing a great job with the 1.2 user manual: http://chdk.wikia.com/wiki/CHDK_1.2.0_User_Manual - I'm sure he'd appreciate anyone lending a hand!
« Last Edit: 05 / July / 2013, 16:00:07 by reyalp »
Don't forget what the H stands for.

*

Offline msl

  • *****
  • 1263
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: CHDK 1.2 release planning
« Reply #2 on: 05 / July / 2013, 16:58:51 »
A little thing: http://chdk.setepontos.com/index.php?topic=9582.msg98447#msg98447

Remote capture: More cameras with JPG support. Is there an instruction to complete these changes for other cameras?

msl 
CHDK-DE:  CHDK-DE links

*

Offline reyalp

  • ******
  • 12159
Re: CHDK 1.2 release planning
« Reply #3 on: 05 / July / 2013, 17:28:37 »
A little thing: http://chdk.setepontos.com/index.php?topic=9582.msg98447#msg98447
Good reminder, I'll try to get that in.

Quote
Remote capture: More cameras with JPG support. Is there an instruction to complete these changes for other
You basically just need to implement platform/sub/filewrite.c and define CAM_HAS_FILEWRITETASK_HOOK 1 and possibly CAM_FILEWRITETASK_SEEKS 1 (for dryos >= r50 most likely).  The existing cameras with filewrite support should give a good range of examples.

It's possible that some cameras will have different filewrite code, but the ones we have added cover early vxworks through recent dryos so hopefully we've covered most of the variations.

I guess phils new code_gen tool might help with this, I haven't had time to look at it yet.
Don't forget what the H stands for.


*

Offline philmoz

  • *****
  • 3129
    • Photos
Re: CHDK 1.2 release planning
« Reply #4 on: 05 / July / 2013, 19:15:57 »
Quote
Remote capture: More cameras with JPG support. Is there an instruction to complete these changes for other
You basically just need to implement platform/sub/filewrite.c and define CAM_HAS_FILEWRITETASK_HOOK 1 and possibly CAM_FILEWRITETASK_SEEKS 1 (for dryos >= r50 most likely).  The existing cameras with filewrite support should give a good range of examples.

It's possible that some cameras will have different filewrite code, but the ones we have added cover early vxworks through recent dryos so hopefully we've covered most of the variations.

I guess phils new code_gen tool might help with this, I haven't had time to look at it yet.

How do you find the correct values for:
   MAX_CHUNKS_FOR_JPEG
   fwt_data_struct

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)

*

Offline reyalp

  • ******
  • 12159
Re: CHDK 1.2 release planning
« Reply #5 on: 05 / July / 2013, 20:32:52 »
How do you find the correct values for:
   MAX_CHUNKS_FOR_JPEG
   fwt_data_struct
They need to be figured out from the filewritetask code, though if there's already a camera of a similar generation, it's probably sufficient to just check that the firmware code is similar and use the same values.

The calls to Write() can be used to work backward to where the address/size pairs are. On D10, this is in sub_FFA263B4

The filename should be easy to get form the Open call.
Don't forget what the H stands for.

*

Offline dvip

  • ****
  • 451
Re: CHDK 1.2 release planning
« Reply #6 on: 06 / July / 2013, 00:39:36 »
With the SX40HS and the A590IS.

One thing using 1.2, about User Menu Enable  [ Off, On, On Dire, Edit ]. I only get [ Off, On, On Dire], "Edit" is missing. Unless I need to activate something else.
 

*

Offline philmoz

  • *****
  • 3129
    • Photos
Re: CHDK 1.2 release planning
« Reply #7 on: 06 / July / 2013, 00:42:59 »
With the SX40HS and the A590IS.

One thing using 1.2, about User Menu Enable  [ Off, On, On Dire, Edit ]. I only get [ Off, On, On Dire], "Edit" is missing. Unless I need to activate something else.
 

CHDK Settings --> Menu Settings --> User Menu Edit.

Stand alone user menu editor module.

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)


*

Offline dvip

  • ****
  • 451
Re: CHDK 1.2 release planning
« Reply #8 on: 06 / July / 2013, 00:53:55 »
CHDK Settings --> Menu Settings --> User Menu Edit.

Stand alone user menu editor module.

Phil.


@Phil, I did try that one before and it didn't do anything.
Then pressed the ERASE button (and HALF SHOOT) and no item is added to the User Menu.
It seems like it is not going into "Edit" mode.

*

Offline philmoz

  • *****
  • 3129
    • Photos
Re: CHDK 1.2 release planning
« Reply #9 on: 06 / July / 2013, 01:01:17 »
CHDK Settings --> Menu Settings --> User Menu Edit.

Stand alone user menu editor module.

Phil.


@Phil, I did try that one before and it didn't do anything.
Then pressed the ERASE button (and HALF SHOOT) and no item is added to the User Menu.
It seems like it is not going into "Edit" mode.

http://chdk.setepontos.com/index.php?topic=9931.0

All of the old user menu editing is gone - it's a stand alone editor now.

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)

 

Related Topics