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

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

This new pi is only running the one camera, so cpu load should not be a 
factor.
1. already 15 fps
2. 60 = 2 seconds
3. So that's why the default chosen was 16, instead of 15. ok. I'll go 
back to a testing stance.
Also, as per murphy's law, the Recv-Q is now 0. The only thing I can see 
that changed, is day turned to dusk. I'll see what tomorrow brings.

Thanks.

MrDave wrote:
> Yea, I'll probably add in some defaults back in for the ports.  I just 
> don't want my perpetual task to be to figure out every protocol that 
> exists in the world and track down its default port number.
>
> 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.
>
> 1.  Change the frame rate on the camera (not Motion) to a lower number
>
> 2.  Increase the frequency of the I-Frames.
>
> 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)
>