Send Motion-user mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: Motion 4.2.2 vs 4.1.1 CPU usage (Colin Law)
----------------------------------------------------------------------
Message: 1
Date: Sat, 20 Jul 2019 15:35:04 +0100
From: Colin Law <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Motion 4.2.2 vs 4.1.1 CPU usage
Message-ID:
<CAL=0gLt0NUuiaLF3fTbffQNa6J=8kmxdnoxmoryddm1h6gf...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On Sat, 20 Jul 2019 at 15:24, John D. Gwinner <[email protected]> wrote:
> Ok, that helps me with my project ? we need to get 15fps or 30fps; (it?s a
> medical project).
>
>
>
> If you?re getting 2-5 and that high a CPU rate, clearly we?ll never get to
> 15.
>
It also depends dramatically on the format of the data. If it is mpjpeg
for example then motion need do very little to decode the image, if however
it is H264 then there is a vast amount of work required just extracting the
images from the stream. On my system running an H264 camera a lot more
processor time is spent decoding the stream than is spent in motion
detection.
Colin
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 17360 bytes
Desc: not available
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 157, Issue 33
********************************************
