A590IS porting... - page 91 - DryOS Development - CHDK Forum

A590IS porting...

  • 968 Replies
  • 331140 Views
*

Offline reyalp

  • ******
  • 13434
Re: A590IS porting...
« Reply #900 on: 10 / July / 2013, 23:58:21 »
Advertisements
>CAM_EV_IN_VIDEO does not respond at dark scenes

It is not for dark scenes, it is for too bright scenes.

It is useful for overexpose video scenes
in general. And it is fast and easy to access by just pressing
the +/- key during video recording.
As developers, the question we are interested in is whether it works correctly on this camera? From the postings in this thread, that isn't clear to me.
Don't forget what the H stands for.

*

Offline dvip

  • ****
  • 451
Re: A590IS porting...
« Reply #901 on: 11 / July / 2013, 03:25:59 »
@reyalp, I had more time to look into this now.

It works in the sense that it can decrease exposure while recording video, but it can't
increase exposure (something I never use it for).

The horizontal exposure level that appears on the screen when
you press the +/- button to activate this, never goes passed the middle to increase
exposure, in other words, it never goes into the positive steps that the exposure level displays on the screen.

It is fine with me if it is removed since "Enable Fast EV swit [.]"
can accomplish the same thing while recording video. But it won't
display any horizontal exposure level to indicate the steps of
exposure. However, you do see the screen getting darker/lighter when
you press the up/down buttons.

If it can save some memory or simplify code, it is fine to remove it.


*

Offline blackhole

  • *****
  • 844
  • A590IS 101b
    • Planetary astrophotography
Re: A590IS porting...
« Reply #902 on: 11 / July / 2013, 08:26:37 »
Enabling CAM_EV_IN_VIDEO no adverse effects on the functionality of other features. Memory consumption of 800 bytes is not terrible.

*

Offline nafraf

  • *****
  • 1308
Re: A590IS porting...
« Reply #903 on: 11 / July / 2013, 19:09:51 »
You may also want to take a look at this bug.
If you set:
CHDK Settings->OSD Settings->Miscellaneous Values->Show Misc Values [Shoot]
it behaves as:
CHDK Settings->OSD Settings->Miscellaneous Values->Show Misc Values [Always]
@dvip
I only see problem with zoom value, behavior of other values are right.
Using [Shoot] parameters appear when you press half_shoot and dissappear after full_shoot.  Is that what you are seeing?

This patch should solve zoom value behavior.  Please test it.
Code: [Select]
Index: core/gui_osd.c
===================================================================
--- core/gui_osd.c (revision 2951)
+++ core/gui_osd.c (working copy)
@@ -363,7 +363,7 @@
 
     //gui_osd_calc_expo_param();
 
-    if (conf.values_show_zoom)
+    if (conf.values_show_zoom && (showtype==1) )
     {
         int fl, zp=shooting_get_zoom(), fl1=get_focal_length(zp);     
         switch (conf.zoom_value)


*

Offline dvip

  • ****
  • 451
Re: A590IS porting...
« Reply #904 on: 11 / July / 2013, 20:17:39 »
@nafraf,

If on the chdk menu you set:

CHDK Settings->OSD Settings->Miscellaneous Values->Show Misc Values [Shoot]
Show Zoom [.]
Zoom Value [EFL]

"Z: ## mm" should show on the screen only when  half press (camera_info.state.is_shutter_half_press).

The way it is now, both "Show Misc Values [Shoot]" and "Show Misc Values [Always]" behave the same way, they both always show "Z: ## mm" on the screen.

Perhaps the problem is in the logic of the gui_draw_osd() function.

« Last Edit: 11 / July / 2013, 20:25:04 by dvip »

*

Offline nafraf

  • *****
  • 1308
Re: A590IS porting...
« Reply #905 on: 11 / July / 2013, 20:31:01 »
Perhaps the problem is in the logic of the gui_draw_osd() function.
Please test this version.
« Last Edit: 27 / July / 2013, 06:33:26 by nafraf »

*

Offline dvip

  • ****
  • 451
Re: A590IS porting...
« Reply #906 on: 11 / July / 2013, 20:36:19 »
@nafraf, that did it! Thanks!  :D

*

Offline nafraf

  • *****
  • 1308
Re: A590IS porting...
« Reply #907 on: 11 / July / 2013, 21:20:53 »
@nafraf, that did it! Thanks!  :D
I applied the patch I posted previously. Reply #903


*

Offline dvip

  • ****
  • 451
Re: A590IS porting...
« Reply #908 on: 27 / July / 2013, 01:05:03 »
I wonder if the same work that was done in this A720 patch here:

http://chdk.setepontos.com/index.php?topic=650.msg103184#msg103184

can be done for the a590IS.

I have noticed that values like:

-----------------
   #undef  CAMERA_MIN_DIST
    #define CAMERA_MIN_DIST                 100     // Override min subject distance
    #undef  CAMERA_MAX_DIST
    #define CAMERA_MAX_DIST                 52855   // Override max subject distance

    #define CAM_HAS_FILEWRITETASK_HOOK       1

//   #define REMOTE_SYNC_STATUS_LED    0xC0xxyyyy      // specifies an LED that turns on while camera waits for USB remote to sync


-----------------

Don't look right.  I think CAMERA_MIN_DIST can be 52 and  #define REMOTE_SYNC_STATUS_LED is commented out... not an expert in this but would like to know if this is correct.
I posted this in the wrong forum and moved it here.


*

Offline nafraf

  • *****
  • 1308
Re: A590IS porting...
« Reply #909 on: 27 / July / 2013, 07:00:32 »
Don't look right.  I think CAMERA_MIN_DIST can be 52 and  #define REMOTE_SYNC_STATUS_LED is commented out... not an expert in this but would like to know if this is correct.
I posted this in the wrong forum and moved it here.
Hi, how did you get 52 value? Did you use the script posted here?

Blue LED is set as REMOTE_SYNC_STATUS_LED in attached file, please test it and report.

 

Related Topics