the collaborative CHDK build - page 11 - CHDK Releases - CHDK Forum supplierdeeply

the collaborative CHDK build

  • 249 Replies
  • 172924 Views
Re: the collaborative CHDK build
« Reply #100 on: 06 / August / 2008, 09:56:41 »
Advertisements
I am sure because the same pixel constantly appears on pictures.
but when I use CHDK, I can clean him from a picture.
and at the record of video he remains on the same place

It is not possible to get access to each video frame and then, in realtime, remove the hot pixel.

Maybe there is a plugin for VirtualDub that will remove hot pixels from the recorded movie ?

Re: the collaborative CHDK build
« Reply #101 on: 06 / August / 2008, 10:03:00 »
Microfunguy

ok, I understood. thank you that answered.

Re: the collaborative CHDK build
« Reply #102 on: 06 / August / 2008, 10:16:01 »
it is possible to do what to ON/OFF "focus LED lamp" during a record video for a nightly survey?

Re: the collaborative CHDK build
« Reply #103 on: 06 / August / 2008, 10:17:13 »
for example by the button of "erase"


*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: the collaborative CHDK build
« Reply #104 on: 06 / August / 2008, 10:35:22 »
yes, it is possible by the use of scripts (please search the forum or open another thread). please refrain from double or triple posting.

about the hotpixel issue: like Microfunguy already wrote, it isnt possible (yet), and maybe never will.

*

Offline obsidian

  • *
  • 31
  • A710IS
Re: the collaborative CHDK build
« Reply #105 on: 06 / August / 2008, 10:41:00 »
A710IS:  when pressed half shutter while starting the camera crashes. Why? Latest collaborative autobuild.
Does the edge overlay work in A710IS?
A710IS + 4GB SanDisk Ultra II

*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
Re: the collaborative CHDK build
« Reply #106 on: 06 / August / 2008, 11:04:32 »
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.)


Quote
Does the edge overlay work in A710IS?
From what I've tested, doesn't seem to.

*

Offline obsidian

  • *
  • 31
  • A710IS
Re: the collaborative CHDK build
« Reply #107 on: 06 / August / 2008, 13:52:12 »
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?
« Last Edit: 06 / August / 2008, 14:11:43 by obsidian »
A710IS + 4GB SanDisk Ultra II


*

Offline Jucifer

  • *****
  • 251
  • [A710IS]
Re: the collaborative CHDK build
« Reply #108 on: 07 / August / 2008, 08:33:32 »
(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 )
« Last Edit: 07 / August / 2008, 15:13:02 by Jucifer »

*

Offline reyalp

  • ******
  • 14110
Re: the collaborative CHDK build
« Reply #109 on: 09 / August / 2008, 06:08:46 »
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.
Don't forget what the H stands for.

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal