the collaborative CHDK build

[obsidian]

A710IS:  when pressed half shutter while starting the camera crashes. Why? Latest collaborative autobuild.
Does the edge overlay work in A710IS?

[Jucifer]

A710IS:  when pressed half shutter while starting the camera crashes. Why?

Mine doesn't... ?/ Could have something to do with CHDK... (=I have no idea, try renaming cchdk.cfg.)

Does the edge overlay work in A710IS?

From what I've tested, doesn't seem to.

[obsidian]

I got it!
The problem is zebra! If the "show zebra is on" the camera crashes, if the zebra is off, the camera doesnt crash.

My zebra config:
mode blink 1
under exp 1
over exp 1
refresh default view yes
refresh osd yes
draw over histo
rgb zebra off
..........

I will have a loo kto source.




--------

I looked:
is suspect this:
gui.c - look up a string "    if (conf.zebra_draw && gui_mode==GUI_M" and anylyze it

can it be debugged?

[Jucifer]

(edit: I don't have any problems with those zebra options...)


motion detection in Lua now returns the number of detected cells.

usage:
cells=md_detect_motion( a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p )
(h can be pretty much anything, it's there for compatibility with ubasic documentation)
(edit: every parameter is now optional, some of the default values are the same as in fudgey's MD scripts)

or:
cells=md_detect_motion( columns, rows, pixel_measure_mode, detection_timeout, measure_interval, threshold, draw_grid, ignored, clipping_region_mode, clipping_region_column1, clipping_region_row1, clipping_region_column2, clipping_region_row2, parameters, pixels_step, msecs_before_trigger )

[reyalp]

Here's a patch that fixes the warning spew from lua, and another one in luascript.

You might also want this patch I posted for the trunk.

I've also noticed some issues with the fast video control stuff (mentioned on IRC, but posting here so it doesn't get lost):
It doesn't correctly detect when you aren't in movie mode. movie_status can be 1 even after you've switched the mode selector to a still mode (on my a540 anyway). This means that pressing left or right will still try to do the pause/unpause functions. To know if you are in movie mode, you need to check all of the MODE_MOVIE_ values.

Even when you are in movie mode, the unpause function doesn't know if you are actually stopped or just paused. This means that if you try to use the left/right after having actually stopped the video you still try to pause or unpause.

I'll post a patch for the first issue and some other cosmetic stuff, but I'm not sure how you can deal with the second one.

On my camera, the fast ev keys (up/down) also conflict with the flash and macro/mf functions.

[whim]

Great work , reyalp !
This definitely increases the visibility of 'real' errors, thanks !

wim

[reyalp]

For the second problem, we might be able to do something in the record task.

[fbonomi]

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!

[reyalp]

@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

[fbonomi]

thanks, I was looking for them in the lua folder !!!

[PhyrePhoX]

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.

[actinium]

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

[PhyrePhoX]

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

[actinium]

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

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

regards,

Alan

[reyalp]

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