Send Motion-user mailing list submissions to
        motion-user@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
        motion-user-requ...@lists.sourceforge.net

You can reach the person managing the list at
        motion-user-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."


Today's Topics:

   1. Re: Blurred and Low framerate (Steve Goldsmith)


----------------------------------------------------------------------

Message: 1
Date: Thu, 15 Jun 2017 10:12:13 -0400
From: Steve Goldsmith <sgj...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Blurred and Low framerate
Message-ID:
        <CAFYqzyn-CZz77vvhJt2rCBnMaYwW9QBTzDw3pY7Fnr2e=lp...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

It depends on the Pi version. I know the earlier versions shared the USB
bus with the network interface I believe and USB cams sucked with that
configuration. Even on quad core SBCs like the ODROID C1 I typically shoot
for 7 FPS at 720P, but I'm also doing pedestrian detection and encoding
video. I still like to leave about 20% headroom for normal OS stuff as
well. You can see over my 24h CPU usage that I do not exceed 80% often and
idle is around 20% for motion detection. Obviously if you are doing only
motion detection and encoding video you can go higher FPS and resolution.
Also, some SBCs have the ability to do hardware encoding, so there are
multiple things to consider. Also consider I'm using the default settings
of the camera a MS LIfecam 3000 HD.


?
Frankly, I'd start off with something like mjpg-streamer and get a base
line. If your USB camera is using MJPEG then it will use very little CPU
since the frames will not need encoding but you should also be looking at
network performance. As FPS and frame size increases you my end up
saturating your network using MJPEG. This is why I keep all the traffic
local on the camera and only send DIVX MP4 encoded videos over the network.
H264 is too slow without hardware acceleration, but DIVX is way better than
MJPEG.

One of my projects has a script to install mpg-streamer (which will work on
the Pi) https://github.com/sgjava/install-opencv#install-mjpg-streamer. I'd
install libjpeg-turbo first though
https://github.com/sgjava/install-opencv#install-libjpeg-turbo in case you
do need to encode JPEG for any reason. A nice side effect is that you will
have a MJPEG stream always available to view regardless of what other
software is reading the camera. Then just use
http://localhost:8080/?action=stream with motion as a network camera
instead of letting it access USB camera directly.

On Thu, Jun 15, 2017 at 3:57 AM, <m...@1337mail.net> wrote:

> Hmmm, I went from 17 to 8 and the frame rate went down AND I started
> getting "Video device is unavailable".  It seems like 2
> (V4L2_PIX_FMT_SBGGR8  : 2  'BA81') is giving me the best performance (on a
> Raspberry Pi3 with a USB cam)....
>
>
> What's the least CPU intensive setting?
>
>
>
>
> Hi
>> Thanks for replying.
>> It's the latest code from git, and takes 2% CPU (on a 24-core Xeon) so I
>> don't think it's the CPU ;-)
>>
>> I tried the brightness control in the conf file without success.
>> But thanks to your help I changed exposure_auto with v4l2-ctl and it
>> really helped!
>> (focus_auto was suggested but it doesn't have that option)
>>
>> I then discovered that the camera has both MJPEG and YUYV (4:2:2) and the
>> latter is limited to 5 fps
>> so I changed the v4l2_palette config from 17 to 8 and now I get 30 fps
>> (there's a lot of chroma noise now but at least it works)
>>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>



-- 
Steven P. Goldsmith
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2017-06-15 09-49-36.png
Type: image/png
Size: 274859 bytes
Desc: not available

------------------------------

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

------------------------------

Subject: Digest Footer

_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user


------------------------------

End of Motion-user Digest, Vol 132, Issue 10
********************************************

Reply via email to