A590IS porting...

  • 968 Replies
  • 223195 Views
*

Offline dvip

  • ****
  • 451
Re: A590IS porting...
« Reply #860 on: 07 / February / 2012, 22:19:23 »
Advertisements
Thanks for the poke() and call_func_ptr() examples, rudi. Very cool!
I wonder what else we could do in lua, those functions, and the A590IS-101b.

Today Canon came up with some new cams with AA batteries
but nothing with PASM like the A590IS... and the A650IS.
It looks like those times are gone :(
They are great cams and with chdk they are fantastic.
To get a new A590IS now is like $379 or more.


*

Offline dvip

  • ****
  • 451
Re: A590IS porting...
« Reply #861 on: 29 / March / 2012, 22:41:19 »
Color bug?

1. Go into Visual Settings
2. Select Cursor Background Color (default is red)
3. Select blue
4. Turn the cam off
5. Turn the cam on

The cam will now have a different color, not blue nor red :)
I have always used the default red and white because of this.


Re: A590IS porting...
« Reply #862 on: 23 / April / 2012, 15:12:11 »
Hi,
My 590 has firmware ver 1.00D and the two published versions e and b do not work. I only wanted to use CHDK to get RAW on this great little camera.
I no nothing about programming, do I have any other options to get CHDK to work with this firmware or can I replace the firmware for another version?
Many thanks.

Re: A590IS porting...
« Reply #863 on: 23 / April / 2012, 16:20:12 »
My 590 has firmware ver 1.00D and the two published versions e and b do not work. I only wanted to use CHDK to get RAW on this great little camera.
Search this forum for RAW conversations - it might not be quite as big a deal as you are thinking.

Quote
I no nothing about programming, do I have any other options to get CHDK to work with this firmware
Unfortunately, no.  Somebody has to make a port for your version.
Quote
or can I replace the firmware for another version?
Firmware changes only happen if Canon issues an official update.  Which they very seldom do.

Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline dvip

  • ****
  • 451
Re: A590IS porting...
« Reply #864 on: 05 / May / 2012, 11:10:36 »
@peejayw,
Perhaps you can download the CHDK-Shell and make the changes that you need:

http://chdk.setepontos.com/index.php?PHPSESSID=01e04c0fdb73fcd298cb7d230dce4188&topic=845.0

http://chdk.wikia.com/wiki/CHDK-Shell

The Canon A590is (PASM) is a complete different camera with chdk. Having RAW/DNG and scripts makes it great.



*

Offline dvip

  • ****
  • 451
Re: A590IS porting...
« Reply #865 on: 20 / May / 2012, 18:59:42 »
If games and all ISO stuff, curves overlay, games, calendar, modules
get comment out will it make chdk run faster and save memory?
I don't  use those modules much.

Would love to have a lite and speedy chdk with just: RAW/DNG, Scripts, Video, Zebra and Histogram.
Any lite version?


*

Offline philmoz

  • *****
  • 3066
    • Photos
Re: A590IS porting...
« Reply #866 on: 20 / May / 2012, 19:05:40 »
If games and all ISO stuff, curves overlay, games, calendar, modules
get comment out will it make chdk run faster and save memory?
I don't  use those modules much.

Would love to have a lite and speedy chdk with just: RAW/DNG, Scripts, Video, Zebra and Histogram.
Any lite version?



In the release-1.0 version most of the things you mention can be removed with compile time options - you can build your own version without them (CHDK-Shell makes this quite easy).

While this saves memory I can't see how it would make CHDK run faster.

The trunk version moves much of this code to modules that are only loaded when needed so you get almost the same memory savings as manually removing them from the release-1.0 build; with the advantage that they are still there when you want them.

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: A590IS porting...
« Reply #867 on: 21 / May / 2012, 00:56:36 »
If games and all ISO stuff, curves overlay, games, calendar, modules get comment out will it make chdk run faster and save memory? I don't  use those modules much. Would love to have a lite and speedy chdk with just: RAW/DNG, Scripts, Video, Zebra and Histogram. Any lite version?
After I read this post (and philmoz's technically correct answer) I began to think that maybe you are not really worried so much about CHDK execution speed or code space but more about your experience with the CHDK user interface & menu structure.   

A few months ago,  I started using the user menu feature in CHDK such that the user menu appears first when the <ALT> key is pressed and the menu takes me to the places I use the most right away.  Makes CHDK a whole lot easier to use in real photographic usage situations !

Of coarse,  the user menus in the trunk version are basically broken and no longer support the features I use.  This has been discussed before and will be fixed - if necessary by backing out the changes made when the module system was introduced.

dvip's post has me wondering whether simply reverting the dev trunk to work like the stable version is enough ?  Maybe there is something more we can do to give him the "lite and speedy" CHDK he desires ?
« Last Edit: 21 / May / 2012, 00:58:37 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline dvip

  • ****
  • 451
Re: A590IS porting...
« Reply #868 on: 21 / May / 2012, 17:52:56 »
@Phil, thanks for the reply, makes sense.

@waterwingz, you're correct. A to the point menu would help. I have
never found any image improvement in the ISO stuff and it takes so
much space in the menu system. The same with curves which can be
done on the PC easier and better. Games and the calendar, I
understand they don't take much space and can be edited out from the
CHDK-Shell.

I would like to see as you said something that "Makes CHDK a whole
lot easier to use in real photographic usage situations".
Better DNGs, HDRs, fast scripts to talk to the ARM architecture... And a
simple menu for real photographic situations.
 A speedy and slick CHDK :D



Re: A590IS porting...
« Reply #869 on: 21 / May / 2012, 19:45:36 »
I would like to see as you said something that "Makes CHDK a whole ot easier to use in real photographic usage situations".
Better DNGs, HDRs, fast scripts to talk to the ARM architecture... And a simple menu for real photographic situations.
A speedy and slick CHDK :D
Okay - its easy to ask for "better".  Its something else to define what better means.   In this case,  the actual coding once you know what you want to do is probably the easy part. 

For example,  what does "better" DNG mean ?

On the other hand,  I understand your comment about HDR.   HDR is currently done with a script or a whole convoluted setup involving menus & timers.   On my G10,  the built-in HDR provided by Canon is just two button clicks and the camera just takes the 3 necessary exposure bracketing pix for HDR.  It all just works. I wish the CHDK version was as easy.

But then what does "fast scripts to talk to the ARM architecture" mean though ? 

For me, the user menu function is a big step towards a more "user friendly" CHDK.   Was reading through another photography forum today and was surprised to see people talking about trying CHDK and giving up because the menu were too complicated.

If you are serious about this,  then we probably need to move to a new thread.  Something like "Thoughts for a speedy and slick CHDK"  would be a good topic title if you want to start a new thread for this.

Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics