Motion Detection too slow? - page 13 - Script Writing - CHDK Forum  

Motion Detection too slow?

  • 253 Replies
  • 168741 Views
Re: Motion Detection too slow?
« Reply #120 on: 06 / February / 2008, 18:22:23 »
Advertisements
Deleted
« Last Edit: 22 / April / 2008, 10:29:45 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

Re: Motion Detection too slow?
« Reply #121 on: 07 / February / 2008, 14:09:38 »


45ms shutter-lag. :)



Drools, can't wait till that gets released for my camera.

Re: Motion Detection too slow?
« Reply #122 on: 07 / February / 2008, 14:39:07 »
Deleted
« Last Edit: 22 / April / 2008, 10:30:12 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

Re: Motion Detection too slow?
« Reply #123 on: 07 / February / 2008, 16:17:20 »
Solved the problems with `continuous shooting' in all circumstances, so no problems
for all ISO levels, if using RAW or not, it all works without trigger delay at all (one caveat:
on my camera). Just added the complementary test with propcase 205/206.
Here it is.
Code: [Select]
@title MD LightningB
@param a Columns
@default a 6
@param b Rows
@default b 4
@param c Threshold (0-255)
@default c 10
@param d Compare Interval (ms)
@default d 0
@param e Trigger Delay (0.1 s)
@default e 0
@param f Time-out Period (s)
@default f 3600
@param g Pix-Step(speed/accuracy adj)
@default g 6
@param h Measure Mode(1-Y 0-U 2-V)
@default h 1
@param i Direct Shoot (0=N 1=Y)
@default i 1
print " compare interval",d
print " trigger delay   ",e
print " direct shoot    ",i
e=e*100
f=f*1000
while 1
  press "shoot_half"
rem use 205 for DigiII
  do
    get_prop 206 p
  until p=1
  md_detect_motion a, b, h, f, d, c, 1, t, 0, 1, 1, a, b, i, g, e
  if i=0 then click "shoot_full"
rem the next loop is endless if AE lock is activated, use 205 for DigiII
  do
    get_prop 206 p
  until p<>1
wend
end
Also cleaned up some of the parameters and printed those that are of relevance
for time from detection to shot. The other parameters do not influence this time.
Now it only remains to be seen if this 3 buffer idea can be implemented in a way
that does improve timing, which is not the case at the moment.

Edit: corrected typo in script
« Last Edit: 08 / February / 2008, 06:04:22 by anonymous »


*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Motion Detection too slow?
« Reply #124 on: 07 / February / 2008, 16:21:45 »
wow, so much brainstorming for shooting pics when it's thunderstorming :D
will definitly try your scripts this weekend. with your scripts it should be possible to take pictures of licenseplates of speeding cars, we could be the small town police, especially since you can even calculate how fast (too fast? charge him $! :D) a car passes by. terrific job y'all did here :)

Re: Motion Detection too slow?
« Reply #125 on: 07 / February / 2008, 18:24:26 »
Deleted
« Last Edit: 22 / April / 2008, 10:30:35 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Motion Detection too slow?
« Reply #126 on: 07 / February / 2008, 18:38:24 »
Keep in mind that the spurious ones (both speedy and laggy ones) may be just the operating system / drivers acting up by lagging and then drawing stuff from buffers or skipping something entirely. I think I'll modify my LED blinker gadget a bit to suit MD benchmarking to have something I can trust 100% and something to compare the lightning test PC software to.

Re: Motion Detection too slow?
« Reply #127 on: 07 / February / 2008, 19:04:12 »
Deleted
« Last Edit: 22 / April / 2008, 10:30:58 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye


Re: Motion Detection too slow?
« Reply #128 on: 07 / February / 2008, 23:27:58 »


Well, don't lose too much saliva over the issue.  :D

Here's the odd thing, after I got some rest I thought I'd see if other settings got it to go even faster. Danged if I could get it to reproduce those 45ms speeds! Best I could do was 60ms, using both methods of triggering (Direct Shoot = 0 or 1). I must have changed something or used a different ISO or ... who knows.





I had the same thing happen with my 80ms shots. I changed to allbest and back and I cant get better then 120ms. I had all my settings written down so either theres something missing or I have gremlins.

Re: Motion Detection too slow?
« Reply #129 on: 08 / February / 2008, 01:20:11 »
Deleted
« Last Edit: 22 / April / 2008, 10:31:27 by Barney Fife »
[acseven/admin commented out: please refrain from more direct offensive language to any user. FW complaints to me] I felt it imperative to withdraw my TOTAL participation. Nobody has my permission, nor the right, to reinstate MY posts. Make-do with my quoted text in others' replies only. Bye

 

Related Topics