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: RTSP stream and CPU utilization (prismb...@gmail.com)
   2. Re: RTSP stream and CPU utilization (David Powell)


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

Message: 1
Date: Fri, 23 Nov 2018 14:21:53 -0800
From: prismb...@gmail.com
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] RTSP stream and CPU utilization
Message-ID:
        <cagd+p+bknofcq2hlsws+p94hgcuvp_bd5_ocyp-g7x2_nde...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I have RTSP cameras from sony and they can do both HTTP and RTSP URL's. I
suspect the comment from the manufacturer is misinformed. I would at least
try the MJPEG url...

On Fri, Nov 23, 2018 at 2:15 PM David Powell <da...@depowell.com> wrote:

> Yea, I saw that. I don't know where he came up with those, but I contacted
> the manufacturer and they said RTSP was all it would do.
>
> David
> On 11/23/18 2:10 PM, prismb...@gmail.com wrote:
>
> A person on Amazon listed these URL's as usable for the camera:
>
> rtsp : / / admin:instar@IP-Address:RTSP-Port/11 - VLC Stream
>
> http : / / admin:instar@IP-Address:Port/iphone/11 - Quicktime Stream
>
> http :/ / IP-Address:Port/tmpfs/snap.jpg?usr=admin&pwd=instar - Snapshot
> (720p / 1280x720 Pixel)
>
> http : / / IP-Address:Port/tmpfs/auto.jpg?usr=admin&pwd=instar - Snapshot
> (352p or 176p)
>
> http : / /
> IP-Address:Port/cgi-bin/hi3510/mjpegstream.cgi?-chn=11&-usr=admin&-pwd=instar
> - MJPEG Stream
>
>
> On Fri, Nov 23, 2018 at 11:48 AM David Powell <da...@depowell.com> wrote:
>
>> Thanks for the insight.  And thanks to Harlan for the tip on *mediainfo*
>> - that's going to come in handy.
>>
>> I looked at the settings on the camera and the frame rate was set to 30
>> fps.  Also, the media profile was set to highprofile.  I changed the frame
>> rate to 15 and the profile to "baseline".  None of that lowered the CPU
>> utilization.
>>
>> That camera actually has two streams, a primary and a secondary. The
>> secondary has a 640x352 resolution.  I set it to 15 fps and switched to
>> that stream, and it did make a big difference; brought it down to about
>> 125%. The picture is not as good of course, but I think I can live with
>> that.
>>
>> Still, 125% is 2.5x the other three cameras combined, plus overhead.  It
>> seems to me that I should still be able to do *something* to bring it
>> down under 100%.  I can't believe that an RTSP stream takes that much more
>> computational power. I want to add 4 more similar cameras once I figure
>> this out.  This is the one that I'm playing with:
>>
>>
>> https://www.amazon.com/Security-Surveillance-Detection-Waterproof-4sdot/dp/B073TSN6YD/ref=sr_1_4
>>
>> If you know of any similarly-priced cameras that support MJPEG I'd like a
>> pointer to them!
>>
>> David
>>
>>
>>
>> On 11/23/18 11:26 AM, Colin Law wrote:
>>
>> On Fri, 23 Nov 2018 at 17:13, David Powell <da...@depowell.com> 
>> <da...@depowell.com> wrote:
>>
>> The resolution of the MJPEG ones are all 640x480.  The RTSP one is 720p.
>>
>> I have framerate set to 15 in motion.conf.  The individual camera config 
>> files do not have that setting.
>>
>> The MJPEG cameras are 307200 pixels, the RTSP is 921600 which is
>> equivalent to all the others put together.  Also the RTSP is probably
>> providing the data at 25 or 30 frames/sec and the processor has to
>> decode all of those even though you only want 15/sec in motion Mjpeg
>> is a sequence of individual pictures so unwanted ones can just be
>> thrown away.  So yes, there is a lot more processing to be done for
>> the RTSP camera before it even gets as far as motion.  You may be able
>> to slow down the frame rate in the camera, and also possibly the
>> resolution if you don't need it all.
>>
>>
>> David
>>
>> On 11/23/18 10:54 AM, Colin Law wrote:
>>
>> On Fri, 23 Nov 2018 at 16:53, Colin Law <clan...@gmail.com> 
>> <clan...@gmail.com> wrote:
>>
>> On Fri, 23 Nov 2018 at 16:43, David Powell <da...@depowell.com> 
>> <da...@depowell.com> wrote:
>>
>> I have 3 IP cameras configured in Motion running on a Raspberry Pi (Ubuntu). 
>>  These cameras all use MJPEG streams and the CPU utilization on the Pi 
>> hovers around 50%.
>>
>> I added another camera which doesn't support MJPEG, but does support RTSP.  
>> Adding this one RTSP camera ran the CPU utilization up to around 200% (I 
>> believe this Pi has a quad-core CPU).  Is this typical for RTSP?  Is there 
>> any way to reduce the load for this protocol?  I want to add several more 
>> cameras but cheap wireless outdoor IP cameras that support MJPEG seem to be 
>> hard to come by nowadays.
>>
>> What is the resolution of the mjpeg cameras and what is the rtsp one?
>>
>> Also what is frame rate of both?
>>
>> Colin
>>
>> David
>>
>> _______________________________________________
>> Motion-user mailing 
>> listMotion-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/motion-userhttps://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>> _______________________________________________
>> Motion-user mailing 
>> listMotion-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/motion-userhttps://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>> _______________________________________________
>> Motion-user mailing 
>> listMotion-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/motion-userhttps://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>> _______________________________________________
>> Motion-user mailing 
>> listMotion-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/motion-userhttps://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>> _______________________________________________
>> 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
>
>
>
> _______________________________________________
> Motion-user mailing 
> listMotion-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/motion-userhttps://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...

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

Message: 2
Date: Fri, 23 Nov 2018 16:33:22 -0600
From: David Powell <da...@depowell.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] RTSP stream and CPU utilization
Message-ID: <83e5e43e-2f11-e131-a6b3-1948bddec...@depowell.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Oh, believe me, I've tried it and every permutation of it I could think 
of.? I'm not sure if the manufacturers are all trying to get away from 
MJPEG or not, but it seems silly to me to have a network camera that you 
can't view live in a stock browser.

David

On 11/23/18 4:21 PM, prismb...@gmail.com wrote:
> I have RTSP cameras from sony and they can do both HTTP and RTSP 
> URL's. I suspect the comment from the manufacturer is misinformed. I 
> would at least try the MJPEG url...
>
> On Fri, Nov 23, 2018 at 2:15 PM David Powell <da...@depowell.com 
> <mailto:da...@depowell.com>> wrote:
>
>     Yea, I saw that. I don't know where he came up with those, but I
>     contacted the manufacturer and they said RTSP was all it would do.
>
>     David
>
>     On 11/23/18 2:10 PM, prismb...@gmail.com
>     <mailto:prismb...@gmail.com> wrote:
>>     A person on Amazon listed these URL's as usable for the camera:
>>
>>     rtsp : / / admin:instar@IP-Address:RTSP-Port/11 - VLC Stream
>>
>>     http : / / admin:instar@IP-Address:Port/iphone/11 - Quicktime Stream
>>
>>     http :/ / IP-Address:Port/tmpfs/snap.jpg?usr=admin&pwd=instar -
>>     Snapshot (720p / 1280x720 Pixel)
>>
>>     http : / / IP-Address:Port/tmpfs/auto.jpg?usr=admin&pwd=instar -
>>     Snapshot (352p or 176p)
>>
>>     http : / /
>>     
>> IP-Address:Port/cgi-bin/hi3510/mjpegstream.cgi?-chn=11&-usr=admin&-pwd=instar
>>     - MJPEG Stream
>>
>>
>>     On Fri, Nov 23, 2018 at 11:48 AM David Powell <da...@depowell.com
>>     <mailto:da...@depowell.com>> wrote:
>>
>>         Thanks for the insight.? And thanks to Harlan for the tip on
>>         /mediainfo/ - that's going to come in handy.
>>
>>         I looked at the settings on the camera and the frame rate was
>>         set to 30 fps.? Also, the media profile was set to
>>         highprofile.? I changed the frame rate to 15 and the profile
>>         to "baseline". None of that lowered the CPU utilization.
>>
>>         That camera actually has two streams, a primary and a
>>         secondary. The secondary has a 640x352 resolution.? I set it
>>         to 15 fps and switched to that stream, and it did make a big
>>         difference; brought it down to about 125%. The picture is not
>>         as good of course, but I think I can live with that.
>>
>>         Still, 125% is 2.5x the other three cameras combined, plus
>>         overhead.? It seems to me that I should still be able to do
>>         /something/ to bring it down under 100%.? I can't believe
>>         that an RTSP stream takes that much more computational power.
>>         I want to add 4 more similar cameras once I figure this out.?
>>         This is the one that I'm playing with:
>>
>>         
>> https://www.amazon.com/Security-Surveillance-Detection-Waterproof-4sdot/dp/B073TSN6YD/ref=sr_1_4
>>
>>         If you know of any similarly-priced cameras that support
>>         MJPEG I'd like a pointer to them!
>>
>>         David
>>
>>
>>
>>         On 11/23/18 11:26 AM, Colin Law wrote:
>>>         On Fri, 23 Nov 2018 at 17:13, David Powell<da...@depowell.com>  
>>> <mailto:da...@depowell.com>  wrote:
>>>>         The resolution of the MJPEG ones are all 640x480.  The RTSP one is 
>>>> 720p.
>>>>
>>>>         I have framerate set to 15 in motion.conf.  The individual camera 
>>>> config files do not have that setting.
>>>         The MJPEG cameras are 307200 pixels, the RTSP is 921600 which is
>>>         equivalent to all the others put together.  Also the RTSP is 
>>> probably
>>>         providing the data at 25 or 30 frames/sec and the processor has to
>>>         decode all of those even though you only want 15/sec in motion Mjpeg
>>>         is a sequence of individual pictures so unwanted ones can just be
>>>         thrown away.  So yes, there is a lot more processing to be done for
>>>         the RTSP camera before it even gets as far as motion.  You may be 
>>> able
>>>         to slow down the frame rate in the camera, and also possibly the
>>>         resolution if you don't need it all.
>>>
>>>>         David
>>>>
>>>>         On 11/23/18 10:54 AM, Colin Law wrote:
>>>>
>>>>         On Fri, 23 Nov 2018 at 16:53, Colin Law<clan...@gmail.com>  
>>>> <mailto:clan...@gmail.com>  wrote:
>>>>
>>>>         On Fri, 23 Nov 2018 at 16:43, David Powell<da...@depowell.com>  
>>>> <mailto:da...@depowell.com>  wrote:
>>>>
>>>>         I have 3 IP cameras configured in Motion running on a Raspberry Pi 
>>>> (Ubuntu).  These cameras all use MJPEG streams and the CPU utilization on 
>>>> the Pi hovers around 50%.
>>>>
>>>>         I added another camera which doesn't support MJPEG, but does 
>>>> support RTSP.  Adding this one RTSP camera ran the CPU utilization up to 
>>>> around 200% (I believe this Pi has a quad-core CPU).  Is this typical for 
>>>> RTSP?  Is there any way to reduce the load for this protocol?  I want to 
>>>> add several more cameras but cheap wireless outdoor IP cameras that 
>>>> support MJPEG seem to be hard to come by nowadays.
>>>>
>>>>         What is the resolution of the mjpeg cameras and what is the rtsp 
>>>> one?
>>>>
>>>>         Also what is frame rate of both?
>>>>
>>>>         Colin
>>>>
>>>>         David
>>>>
>>>>         _______________________________________________
>>>>         Motion-user mailing list
>>>>         Motion-user@lists.sourceforge.net  
>>>> <mailto: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
>>>>
>>>>         _______________________________________________
>>>>         Motion-user mailing list
>>>>         Motion-user@lists.sourceforge.net  
>>>> <mailto: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
>>>>
>>>>         _______________________________________________
>>>>         Motion-user mailing list
>>>>         Motion-user@lists.sourceforge.net  
>>>> <mailto: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
>>>         _______________________________________________
>>>         Motion-user mailing list
>>>         Motion-user@lists.sourceforge.net  
>>> <mailto: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
>>         _______________________________________________
>>         Motion-user mailing list
>>         Motion-user@lists.sourceforge.net
>>         <mailto: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
>>
>>
>>
>>     _______________________________________________
>>     Motion-user mailing list
>>     Motion-user@lists.sourceforge.net  
>> <mailto: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
>     _______________________________________________
>     Motion-user mailing list
>     Motion-user@lists.sourceforge.net
>     <mailto: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
>
>
>
> _______________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...

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



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

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 149, Issue 25
********************************************

Reply via email to