Re: [Motion-user] latest git fails to open netcam

[S A. <san...@gm...>]

Hi Dave,

I've had some interesting results you might be interested in.
Booted up this morning, and watched it closely.

Very unusual double green screen in startup video as initial lag at 7 
seconds, becomes 1 second at end.
0550.47 startup-green, 7sec-lag-video 05:50.40
0550.50 motion-detect? jump, B-frames-over-green,
0550.51 video I-frame now 1 sec-lag

hhmm.ss  Recv-Q :port# Seconds (lag in snapshot every 60 sec.)
0556.04    7320 :45632   1
0606.21 2598501 :45632  7

  Edit capture_rate=16 in webcontrol in browser, without restarting program.

0607.23                port reset triggered motion recording with green 
screen,
  Have video if interested.
0608.37  843428 :45634
0611.42 2498757 :45634
0612.00 2616961 :45634 30
  Double check camera clock is within 1 second. yes. Yes it is.
0613.43 2603429 :45634

  Set capture rate to =17
0614.00                33  stream in snapshot says at 0613.27
0615.00 1678376 :45636 15
0616.00       0 :45638 29  resets with new port#
0617.00 2257776 :45638 18
0618.00  180472 :45640  4
0619.00  697768 :45640  7
0620.00  884408 :45640 10
0621.18 2520217 :45640 18
  See pattern, waiting packets grows until new port# kicks back to start 
of stream.
0622.17   null      rtsp connection gone from list $ ss -t
0622.23   null      still not reconnected
0622.41  204688 :45642
0623                    5 sec. Not starting at 1 or has drifted already.
0624.02  698140 :45642 15
0625.12  968200 :45642  5
0626.03 2278012 :45642 19
0626.45 2561981 :45642
0627.01 2522612 :45642 27
0627.26   null
0627.35   99348 :45644
0628.00  444672 :45644  5
0629.29  969940 :45644  8
0630.00 1501392 :45644 13
0631.00 2481737 :45644 29
0631.25   null
0631.43   null
0631.48   68916 :45646
0632.05  353264 :45646  3
--- repeats until something different happened ---
0645.50   null
0645.59   11156 :45652
0646.00                 3  motion triggered video, but see nothing 
except # of pixels indicates whole frame changed with port reconnection. 
No green screen this time.
0647.00                12
0647.40  827424 :45652

  Doubting capture_rate has any effect without restarting program. But 
it is resetting the port often. So... unsure?

$ vcgencmd get_mem gpu
gpu=512M

Edit config.txt and reboot

$ vcgencmd get_mem arm
arm=896M
0654.24  57916 :52654
0655.00   4392 :52654  1
0656.06      0 :52654  1
0657.00      0 :52654  1
0658.07   4392 :52654  1
0659.00      0 :52654  2
0700.23      0 :52654  2
0701.22      0 :52654  2
0729.10   4780 :52654  2
--- 1 hour later ---
0823.01      0 :52654  2
  Still good.

So either editing the arm/gpu memory did the trick, or rebooting so that 
capture_rate took effect.

I noticed log_level does not take effect without restarting.
Will have to test capture_rate further to see if it was or not. Set back 
to 16 tomorrow.

Stewart


MrDave wrote:
> On your problem lagging camera, I've have one of those too.  I don't 
> run on Pi's anymore so some of the solutions may not work on that 
> platform.  The items that helped me.
>
> 3.  With the latest version, you now have the option 'capture_rate' in 
> netcam_params which allows you to specify how fast pictures should be 
> captured from the camera.  The higher the number, the higher the CPU 
> load but also the more frequent the clearing of the pictures from the 
> decoder (and therefore lower latency)
>