From: David P. <da...@de...> - 2018-12-01 04:05:33
|
Thanks, I hadn't seen that. I did have some mismatched image sized and I fixed them. It helped some but my CPU utilization still hovers around 200%. Maybe I'm just expecting too much out of this little Raspberry Pi. It seems to be handling the 5 cameras I have connected pretty well, but I plan to add a couple more and the utilization was only about 50% before I added the last two cameras (both rtsp - the other three are MJPEG). Maybe I will have to split the cameras between two RPis. David On 11/30/18 8:31 AM, leonardo wrote: > On 23/11/2018 21:57, Tom Kennelly wrote: >> I have various no name cameras all using rasp in motion. I have >> found that I need to have an exact match in the motion conf file and >> how the camera is set up. Any mismatches result in high cpu >> utilization. > > i had the same problem (mismatching resolution), infact in motion > guide (height/width parameters) you can find: > > In case of a rtsp/rtmp network camera, Motion will rescale the camera > image to the requested dimensions. This rescaling comes at a very high > CPU cost so it is recommended that the network camera send the image > in the same dimensions as included in the configuration file. > > > > _______________________________________________ > 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 |