the collaborative CHDK build - page 12 - CHDK Releases - CHDK Forum

the collaborative CHDK build

  • 249 Replies
  • 116017 Views
*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: the collaborative CHDK build
« Reply #110 on: 09 / August / 2008, 07:38:09 »
Advertisements
Great work , reyalp !
This definitely increases the visibility of 'real' errors, thanks !

wim

*

Online reyalp

  • ******
  • 11748
Re: the collaborative CHDK build
« Reply #111 on: 09 / August / 2008, 16:54:13 »
For the second problem, we might be able to do something in the record task.
Don't forget what the H stands for.

*

Offline fbonomi

  • ****
  • 469
  • A570IS SD1100/Ixus80
    • Francesco Bonomi
Re: the collaborative CHDK build
« Reply #112 on: 10 / August / 2008, 04:45:46 »
Pardon the dummy question, but where in the source is the lua syntax table?
I mean, where are the CHDK functions defined in lua?

thanks!

*

Online reyalp

  • ******
  • 11748
Re: the collaborative CHDK build
« Reply #113 on: 10 / August / 2008, 04:53:14 »
@fbnomi: in core/luascript.c

edit:Here's another patch.

Changes:
Moved bitrate strings a global in conf, instead of redefining it as stactic in several functions

Added #defines for quality and bitrate settings

Added a macro MODE_IS_VIDEO to platform, which checks if mode is any of the *_VIDEO_* modes
updated most of the obvious places to use this. There's still a few in  gui.c gui_draw_osd that need going through.

moved video quality override display stuff to gui_osd_draw_state
The values of quality are and bitrate are shown if:
- they are different the default setting
or
- they are selected for fast override, and fast override is active
this also fixes a warning related to using undeclared functions

Only do osd_draw_movie_time_left if in movie mode

reworked kbd.c kbd_use_up_down_left_right_as_fast_switch()
- had to reformat the code to work out what was going on :)
- check MODE_IS_VIDEO
- use #defines for various things
- noted, but not fixed the big where it doesn't know if you are paused or not

fixed a possible uninitialized value in playsound. Now if you give it an unrecognized index, it just does nothing

fixed a possible uninitialized value in ubasic temperature check. If an invalid number is given, it returns 0

Also includes my earlier a540 patch and warnings patch

If you prefer individual, smaller patches, I can do that. Or if someone wants to give me svn, I can do that too ;)
« Last Edit: 10 / August / 2008, 04:59:34 by reyalp »
Don't forget what the H stands for.


*

Offline fbonomi

  • ****
  • 469
  • A570IS SD1100/Ixus80
    • Francesco Bonomi
Re: the collaborative CHDK build
« Reply #114 on: 10 / August / 2008, 05:56:15 »
thanks, I was looking for them in the lua folder !!!

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: the collaborative CHDK build
« Reply #115 on: 10 / August / 2008, 12:31:56 »
the mode_is_video check does seem to work on the a620, also the OSD stuff. however in the s3is it does not work, because on the s-series you can start videos in ALL modes via the dedicated button. so the only solution is to use both mode_is_video AND movie_status.
will see what i can do.

Re: the collaborative CHDK build
« Reply #116 on: 10 / August / 2008, 13:39:39 »
strangely i seems to find the temperature display only works / available when CHDK is loaded manually, ie when i autoboot it the option isn't there. I am using a TX1 1.00g

regards,

Alan

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: the collaborative CHDK build
« Reply #117 on: 10 / August / 2008, 13:56:33 »
well, i guess the solution is simple: replace DISKBOOT.BIN with the one from the autobuild. it seems to be an "old" one on your sdcard, and loading manually loads the PS.FIR - which seems to be a recent one from our autobuild :)


Re: the collaborative CHDK build
« Reply #118 on: 10 / August / 2008, 15:17:39 »
thanks for the quick responses.. i got the same answer from frank, and then i realised that i didn't overwrite the old diskboot.bin when i extracted from the archive, now i feel (deservingly) stupid :P

on another note, i am just wondering for the autoiso mode.. it doesn't really seems to be doing much (whether i turn it on or not). I specified the "minimum shutter speed", which i gather should be the slowest shutter speed that the camera should use (which to me is somewhat confusing), but the resultant shutter speed don't stay faster than it? Or have i got the whole thing confused?

I am just trying to use autoiso to force the shutter speed to be below a certain number, while using a faster shutter speed so not getting everything overexposed when it is too bright.. so the "minimum shutter speed" should be the slowest bound?

I am reading shooting.c at the moment.. i might come back tomorrow when i am actually awake to figure out what it is doing

sorry if i am not making much sense... 4am where i am located :P

regards,

Alan

*

Online reyalp

  • ******
  • 11748
Re: the collaborative CHDK build
« Reply #119 on: 11 / August / 2008, 05:50:43 »
the mode_is_video check does seem to work on the a620, also the OSD stuff. however in the s3is it does not work, because on the s-series you can start videos in ALL modes via the dedicated button.
Updated.

Basically does the video stuff if movie_status is > 1 or you are in a movie mode (so you can see your overrides when not recording, if you use movie mode)

Also made the video overrides stop instead of wrapping around (e.g. going to the lowest bitrate doesn't take you back to highest)

Added #CAM_HAS_VIDEO_BUTTON to camera.h for s2,s3 and s5. Untested, since I don't actually own any of those.

edit:
TX1 CAN HAZ VIDEO BUTTON too ;)
« Last Edit: 11 / August / 2008, 15:41:57 by reyalp »
Don't forget what the H stands for.

 

Related Topics