|
From: David P. <da...@de...> - 2018-11-23 19:47:58
|
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...@de...> 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 <cl...@gm...> wrote: >> >> On Fri, 23 Nov 2018 at 16:43, David Powell <da...@de...> 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 >> Mot...@li... >> 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 >> Mot...@li... >> 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 >> Mot...@li... >> 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 > Mot...@li... > https://lists.sourceforge.net/lists/listinfo/motion-user > https://motion-project.github.io/ > > Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user |