Motion Detection too slow? - page 25 - Script Writing - CHDK Forum supplierdeeply
« previous next »
Pages: 1 ... 20 21 22 23 24 [25]   Go Down

Motion Detection too slow?

  • 247 Replies
  • 137755 Views
*

Offline KPOT

  • *
  • 10
Re: Motion Detection too slow?
« Reply #240 on: 22 / June / 2011, 15:22:16 »
Advertisements
hi!
help me please
on my A495 100d script work strange,
after decting motion i have black screen,
and after ~10sec, shoot
Logged
*

Offline waterwingz

  • ******
  • 11998
    • Waterwingz
Re: Motion Detection too slow?
« Reply #241 on: 22 / June / 2011, 21:40:12 »
Quote from: KPOT on 22 / June / 2011, 15:22:16
hi!
help me please
on my A495 100d script work strange,
after decting motion i have black screen,
and after ~10sec, shoot
This sounds camera specific - you probably want to post this in the A495 forum thead <link here> to see if other A495 owners can help.
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline KPOT

  • *
  • 10
Re: Motion Detection too slow?
« Reply #242 on: 23 / June / 2011, 05:32:08 »

Quote from: waterwingz on 22 / June / 2011, 21:40:12
This sounds camera specific - you probably want to post this in the A495 forum thead ....
probably(:, thank you
Logged
*

Offline Caefix

  • ***
  • 147
  • Sorry, busy deleting test shots...
Re: Motion Detection too slow?
« Reply #243 on: 28 / October / 2019, 11:56:18 »
   md_detect_motion a,b,1,d,e,f,g,  :-* ,i,j,k,j+(a%2=0)-(a=2),k+(b%2=0)-(b=2),  :) ;)  N :xmas ,o,p
   
   
    MD_DO_IMMEDIATE_SHOOT {[n=1,9]}, is triggered if one cell hit.

   Now two lines containing MD_AT_ONCE {(N=16,17,25 [&& 1,9])} break the for loops to save milliseconds between
   first hit in field "2x5" and calculating on until '10*10'.
   The return value is adjusted to idx ("2x5").

   [n=1,9] same new behavior to speed up the archive, returns 1.

   (I don´t expect collisions with md_get_cell_diff & md_get_cell_val in OutbackScriptFuncions utilizing [n=1,9].)

edit: Now the N=16+   values are seperated, because of unwanted continuos shooting.
to avoid that, a leading md dummy line could be used in script, like
Code: [Select]
md_detect_motion a,b+h,1,200,100,100,3,T,i,j,k,l,m,0,o,21
md_detect_motion a,b+h,1,  d,  e,  f,g,h,i,j,k,l,m,n,o,p
        N=25 uses kbd_key_press(KEY_SHOOT_FULL_ONLY);

   enjoy...
« Last Edit: 06 / November / 2019, 13:44:18 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline Caefix

  • ***
  • 147
  • Sorry, busy deleting test shots...
Re: Motion Detection too slow?
« Reply #244 on: 14 / November / 2019, 12:23:42 »
 8) Catched with Sx150
ASSERT!! VideoDrv.c Line 530
Task name: FaceFrame

How to utilize in md_det?
Logged
All lifetime is a loan from eternity.
*

Offline srsa_4c

  • ******
  • 4150
Re: Motion Detection too slow?
« Reply #245 on: 14 / November / 2019, 13:35:29 »
Quote from: Caefix on 14 / November / 2019, 12:23:42
How to utilize in md_det?
I guess you mean utilizing face detection. There was some research done here, but it has not become a CHDK feature.
Logged
*

Offline Caefix

  • ***
  • 147
  • Sorry, busy deleting test shots...
Re: Motion Detection too slow?
« Reply #246 on: 16 / November / 2019, 12:20:35 »
 :) nice research, could be continued sometimes.
Maybe uBasic needs a peek_statement first...
One identified indicator was enough to swich, so
I tried to get a hint when auto mode shifts to portrait, but no success so far.
Logged
All lifetime is a loan from eternity.
*

Offline Caefix

  • ***
  • 147
  • Sorry, busy deleting test shots...
Re: Motion Detection too slow?
« Reply #247 on: 23 / November / 2019, 13:51:08 »
 :D ... Found another BIT for
 md_detect_motion a,b,1,d,e,f, :xmas G,  :-* ,i,j,k,j+(a%2=0)-(a=2),k+(b%2=0)-(b=2),  N  ,o,p

G=5,6,7 : draw_grid & 4 -->> only triggered fields are drawn, mostly red.
Logged
All lifetime is a loan from eternity.
Pages: 1 ... 20 21 22 23 24 [25]   Go Up
« previous next »
 

Related Topics